loc stringlengths 82 266 | api stringlengths 90 274 | lastmod stringdate 2024-02-23 00:00:00 2025-08-28 00:00:00 | changefreq stringclasses 1
value | priority float64 0.5 0.5 | sitemappart stringclasses 268
values | locale stringclasses 1
value | bundle stringclasses 231
values | page_id stringlengths 19 186 | release stringclasses 9
values | title stringlengths 1 283 | description stringlengths 0 410 | keywords listlengths 0 142 | breadcrumbs listlengths 0 12 | html_content stringlengths 392 1.6M | page_content dict | clean_text stringlengths 1 379k | rich_text stringlengths 70 379k |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
https://www.servicenow.com/docs/en-US/bundle/zurich-source-to-pay-operations/page/reuse/glossary/A/gloss-agent-workspace.html | https://servicenow-be-prod.servicenow.com/api/bundle/zurich-source-to-pay-operations/page/reuse/glossary/A/gloss-agent-workspace.html | 2025-08-05 | daily | 0.5 | 268.xml | en-US | zurich-source-to-pay-operations | reuse/glossary/A/gloss-agent-workspace.html | zurich | Agent Workspace | a suite of tools that provides agents, case managers, help desk professionals, and managers quick access to what they need to help answer customer questions and resolve customer problems. | [] | [
"Finance and Supply Chain",
"Accounts Payable Operations",
"Accounts Payable Operations reference",
"Approval Plan form",
"Accounts Payable Operations glossary",
"A"
] | <article class="hascomments" data-page="bundle:zurich-source-to-pay-operations/enus/reuse/glossary/A/gloss-agent-workspace.html" id="bundle:zurich-source-to-pay-operations/enus/reuse/glossary/A/gloss-agent-workspace.html"><body id="gloss-agent-workspace"><main role="main"><article role="article" class="dita" id="gloss-agent-workspace" aria-labelledby="title_gloss-agent-workspace">
<h1 class="title glossterm topictitle1" id="title_gloss-agent-workspace">Agent Workspace</h1>
<div class="abstract glossdef">a suite of tools that provides agents, case managers, help desk professionals, and managers quick access to what they need to help answer customer questions and resolve customer problems.</div>
<nav role="navigation"></nav><nav role="navigation" class="tasksNavigation"></nav><nav role="navigation" class="related-links"></nav></article></main></body></article> | {
"attachments": {
"all_attachments": null,
"topic_attachments": []
},
"available_languages": [
"enus"
],
"breadcrumbs": [
{
"title": "Finance and Supply Chain",
"topic_id": "product/source-to-pay-operations/concept/finance-supply-chain-landing.html"
},
{
"title": "Accounts Payable Operations",
"topic_id": "product/accounts-payable-operations/concept/acc-pay-mgmt-landing-page.html"
},
{
"title": "Accounts Payable Operations reference",
"topic_id": "product/accounts-payable-operations/reference/acc-pay-reference.html"
},
{
"title": "Approval Plan form",
"topic_id": "product/accounts-payable-operations/reference/approval-plan-form.html"
},
{
"title": "Accounts Payable Operations glossary",
"topic_id": "product/accounts-payable-operations/concept/apo-glossary.html"
},
{
"title": "A",
"topic_id": "product/accounts-payable-operations/concept/gloss-group-a-apo.html"
}
],
"breadcrumbs_html": "<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations\">Zurich Finance and Supply Chain</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/source-to-pay-operations/concept/finance-supply-chain-landing.html\">Finance and Supply Chain</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/concept/acc-pay-mgmt-landing-page.html\">Accounts Payable Operations</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/reference/acc-pay-reference.html\">Accounts Payable Operations reference</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/reference/approval-plan-form.html\">Approval Plan form</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/concept/apo-glossary.html\">Accounts Payable Operations glossary</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/concept/gloss-group-a-apo.html\">A</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<span class=\"active\">Agent Workspace</span>",
"bundle_id": "zurich-source-to-pay-operations",
"bundle_key": 2735,
"bundle_landing_page": "product/source-to-pay-operations/concept/finance-supply-chain-landing.html",
"bundle_subtitle": null,
"bundle_title": "Zurich Finance and Supply Chain",
"canonical_link": null,
"dates": {
"Added on": "2025-08-05T13:11:54.216332Z",
"Created on": null,
"Initial upload": "2025-07-30T22:25:52.095402Z",
"Updated on": null
},
"dislike_url": "https://servicenow-be-prod.servicenow.com/dislike/55688985",
"dislikes": 0,
"es_archived_content": false,
"is_in_fav": false,
"is_liked": null,
"is_watched": false,
"keywords": [
" zurich zurich"
],
"labels": [
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "zurich",
"navtitle": "Zurich",
"outputclasses": [],
"subjectHeadId": "versions",
"subjectheadNavtitle": "Versions",
"visibility": "show-facet"
},
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "apmgt",
"navtitle": "Accounts Payable Operations",
"outputclasses": [],
"subjectHeadId": "products",
"subjectheadNavtitle": "Products",
"visibility": "show-facet"
}
],
"labels_text": "Versions > Zurich; Products > Finance and Supply Chain > Accounts Payable Operations",
"like_url": "https://servicenow-be-prod.servicenow.com/like/55688985",
"likes": 0,
"metadata": {
"AI Search": null,
"AI Search Assist": null,
"Application Insights": null,
"Capabilities": null,
"Code Signing": null,
"Contextual Search": null,
"DC.contributor": null,
"DC.coverage": null,
"DC.creator": null,
"DC.date.created": "2023-11-14-06:00",
"DC.date.modified": null,
"DC.format": "HTML5",
"DC.identifier": "gloss-agent-workspace",
"DC.language": null,
"DC.relation": "../../../product/accounts-payable-operations/concept/gloss-group-a-apo.html",
"DC.rights.owner": "(C) Copyright 2025",
"DC.subject": null,
"DC.type": "glossentry",
"Data Discovery": null,
"Data Policy": null,
"Data Privacy": null,
"Discovery": null,
"External Content for AI Search": null,
"Field Administration": null,
"Field Normalization": null,
"Key Management Framework": null,
"Localization Framework": null,
"Now Platform": null,
"PlatSec": null,
"Platform": null,
"Platform Administration": null,
"Platform Performance": null,
"Platform Privacy": null,
"Proactive Triggers": null,
"Process Optimization": null,
"RN doc editing record number": null,
"Search Administration": null,
"Secrets Management": null,
"ServiceNow AI Platform": null,
"State Model": null,
"Subscription Management": null,
"Task Communications Management": null,
"Timeline Visualizations": null,
"User Administration": null,
"User Experience Analytics": null,
"Zing": null,
"ai-now-assist": null,
"app-name": null,
"app_route": null,
"azureapimanagemen": null,
"change-completed": null,
"change-item": null,
"change-request-id": null,
"change-request-reference": null,
"com.glide.embedded_help.category": null,
"component": null,
"copyright": "(C) Copyright 2025",
"crossroads": null,
"data": null,
"description": "a suite of tools that provides agents, case managers, help desk professionals, and managers quick access to what they need to help answer customer questions and resolve customer problems.",
"dominant_bundle": null,
"erp-canvas-video": null,
"fsm-mobile": null,
"fsm-route": null,
"fsm-sched-opt": null,
"fsm-wrk-order": null,
"genai-round-7": null,
"generator": "DITA-OT",
"glossPartOfSpeech": null,
"glossStatus": null,
"guided setup": null,
"guided tours": null,
"keywords": null,
"min-toc": null,
"mini": null,
"mini-to truec": null,
"mini-toc": null,
"mini_toc": null,
"minitoc": null,
"modification": null,
"now-assist-app-gen-video": null,
"order": null,
"page-type": null,
"page-type ": null,
"prodname": null,
"product": null,
"product_name": null,
"release": null,
"resourceID": null,
"roles": null,
"route_page": null,
"route_params_listId": null,
"route_params_table": null,
"route_params_type": null,
"route_type": null,
"setconfigurationproperties": null,
"topic": null,
"translation-type": "source",
"version": null,
"workflow": "Creator",
"workplace-srvc-delvry-ditamap": null
},
"page_id": "reuse/glossary/A/gloss-agent-workspace.html",
"page_key": 55688985,
"preprocessed_PDF": "https://downloads.docs.servicenow.com/pdf/enus/servicenow-yokohama-source-to-pay-operations-enus.pdf",
"rating": null,
"read_time_data": {
"char_count": 187,
"img_count": 0,
"read_time": 1,
"video_links": [
""
],
"word_count": 29
},
"related_links": [],
"search_title": null,
"title": "Agent Workspace",
"topic_cluster": {
"clustered_by": {
"enabled": true,
"primary_key": "versions",
"primary_sort": "top-down",
"type": "subjecthead"
},
"clustered_labels": [
"versions"
],
"clustered_topics": [],
"clustering_title": "Zurich"
},
"topic_html": "<article class=\"hascomments\" data-page=\"bundle:zurich-source-to-pay-operations/enus/reuse/glossary/A/gloss-agent-workspace.html\" id=\"bundle:zurich-source-to-pay-operations/enus/reuse/glossary/A/gloss-agent-workspace.html\"><body id=\"gloss-agent-workspace\"><main role=\"main\"><article role=\"article\" class=\"dita\" id=\"gloss-agent-workspace\" aria-labelledby=\"title_gloss-agent-workspace\">\n <h1 class=\"title glossterm topictitle1\" id=\"title_gloss-agent-workspace\">Agent Workspace</h1>\n <div class=\"abstract glossdef\">a suite of tools that provides agents, case managers, help desk professionals, and managers quick access to what they need to help answer customer questions and resolve customer problems.</div>\n \n<nav role=\"navigation\"></nav><nav role=\"navigation\" class=\"tasksNavigation\"></nav><nav role=\"navigation\" class=\"related-links\"></nav></article></main></body></article>",
"topic_language": "enus",
"views": 0,
"your_rating": null
} | # Agent Workspace
a suite of tools that provides agents, case managers, help desk professionals, and managers quick access to what they need to help answer customer questions and resolve customer problems.
| ---
title: Agent Workspace
description: a suite of tools that provides agents, case managers, help desk professionals,
and managers quick access to what they need to help answer customer questions and
resolve customer problems.
keywords: []
breadcrumbs:
- Finance and Supply Chain
- Accounts Payable Operations
- Accounts Payable Operations reference
- Approval Plan form
- Accounts Payable Operations glossary
- A
---
# Agent Workspace
a suite of tools that provides agents, case managers, help desk professionals, and managers quick access to what they need to help answer customer questions and resolve customer problems.
|
https://www.servicenow.com/docs/en-US/bundle/zurich-source-to-pay-operations/page/reuse/glossary/A/gloss-approval-workflow-apo.html | https://servicenow-be-prod.servicenow.com/api/bundle/zurich-source-to-pay-operations/page/reuse/glossary/A/gloss-approval-workflow-apo.html | 2025-08-05 | daily | 0.5 | 268.xml | en-US | zurich-source-to-pay-operations | reuse/glossary/A/gloss-approval-workflow-apo.html | zurich | Approval workflow | The sequence of steps required to approve an invoice. | [] | [
"Finance and Supply Chain",
"Accounts Payable Operations",
"Accounts Payable Operations reference",
"Approval Plan form",
"Accounts Payable Operations glossary",
"A"
] | <article class="hascomments" data-page="bundle:zurich-source-to-pay-operations/enus/reuse/glossary/A/gloss-approval-workflow-apo.html" id="bundle:zurich-source-to-pay-operations/enus/reuse/glossary/A/gloss-approval-workflow-apo.html"><body id="gloss-approval-workflow-apo"><main role="main"><article role="article" class="dita" id="gloss-approval-workflow-apo" aria-labelledby="title_gloss-approval-workflow-apo">
<h1 class="title glossterm topictitle1" id="title_gloss-approval-workflow-apo">Approval workflow</h1>
<div class="abstract glossdef">The sequence of steps required to approve an invoice.</div>
<nav role="navigation"></nav><nav role="navigation" class="tasksNavigation"></nav><nav role="navigation" class="related-links"></nav></article></main></body></article> | {
"attachments": {
"all_attachments": null,
"topic_attachments": []
},
"available_languages": [
"enus"
],
"breadcrumbs": [
{
"title": "Finance and Supply Chain",
"topic_id": "product/source-to-pay-operations/concept/finance-supply-chain-landing.html"
},
{
"title": "Accounts Payable Operations",
"topic_id": "product/accounts-payable-operations/concept/acc-pay-mgmt-landing-page.html"
},
{
"title": "Accounts Payable Operations reference",
"topic_id": "product/accounts-payable-operations/reference/acc-pay-reference.html"
},
{
"title": "Approval Plan form",
"topic_id": "product/accounts-payable-operations/reference/approval-plan-form.html"
},
{
"title": "Accounts Payable Operations glossary",
"topic_id": "product/accounts-payable-operations/concept/apo-glossary.html"
},
{
"title": "A",
"topic_id": "product/accounts-payable-operations/concept/gloss-group-a-apo.html"
}
],
"breadcrumbs_html": "<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations\">Zurich Finance and Supply Chain</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/source-to-pay-operations/concept/finance-supply-chain-landing.html\">Finance and Supply Chain</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/concept/acc-pay-mgmt-landing-page.html\">Accounts Payable Operations</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/reference/acc-pay-reference.html\">Accounts Payable Operations reference</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/reference/approval-plan-form.html\">Approval Plan form</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/concept/apo-glossary.html\">Accounts Payable Operations glossary</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/concept/gloss-group-a-apo.html\">A</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<span class=\"active\">Approval workflow</span>",
"bundle_id": "zurich-source-to-pay-operations",
"bundle_key": 2735,
"bundle_landing_page": "product/source-to-pay-operations/concept/finance-supply-chain-landing.html",
"bundle_subtitle": null,
"bundle_title": "Zurich Finance and Supply Chain",
"canonical_link": null,
"dates": {
"Added on": "2025-08-05T13:11:54.216332Z",
"Created on": "2024-11-04T00:00:00Z",
"Initial upload": "2025-07-30T22:25:52.095402Z",
"Updated on": "2025-07-31T00:00:00Z"
},
"dislike_url": "https://servicenow-be-prod.servicenow.com/dislike/55688986",
"dislikes": 0,
"es_archived_content": false,
"is_in_fav": false,
"is_liked": null,
"is_watched": false,
"keywords": [
" zurich zurich"
],
"labels": [
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "zurich",
"navtitle": "Zurich",
"outputclasses": [],
"subjectHeadId": "versions",
"subjectheadNavtitle": "Versions",
"visibility": "show-facet"
},
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "apmgt",
"navtitle": "Accounts Payable Operations",
"outputclasses": [],
"subjectHeadId": "products",
"subjectheadNavtitle": "Products",
"visibility": "show-facet"
}
],
"labels_text": "Versions > Zurich; Products > Finance and Supply Chain > Accounts Payable Operations",
"like_url": "https://servicenow-be-prod.servicenow.com/like/55688986",
"likes": 0,
"metadata": {
"AI Search": null,
"AI Search Assist": null,
"Application Insights": null,
"Capabilities": null,
"Code Signing": null,
"Contextual Search": null,
"DC.contributor": null,
"DC.coverage": null,
"DC.creator": "ServiceNow",
"DC.date.created": "2024-11-04T05:34:34+05:30",
"DC.date.modified": "2025-07-31",
"DC.format": "HTML5",
"DC.identifier": "gloss-approval-workflow-apo",
"DC.language": null,
"DC.relation": "../../../product/accounts-payable-operations/concept/gloss-group-a-apo.html",
"DC.rights.owner": "(C) Copyright 2025",
"DC.subject": null,
"DC.type": "glossentry",
"Data Discovery": null,
"Data Policy": null,
"Data Privacy": null,
"Discovery": null,
"External Content for AI Search": null,
"Field Administration": null,
"Field Normalization": null,
"Key Management Framework": null,
"Localization Framework": null,
"Now Platform": null,
"PlatSec": null,
"Platform": null,
"Platform Administration": null,
"Platform Performance": null,
"Platform Privacy": null,
"Proactive Triggers": null,
"Process Optimization": null,
"RN doc editing record number": null,
"Search Administration": null,
"Secrets Management": null,
"ServiceNow AI Platform": null,
"State Model": null,
"Subscription Management": null,
"Task Communications Management": null,
"Timeline Visualizations": null,
"User Administration": null,
"User Experience Analytics": null,
"Zing": null,
"ai-now-assist": null,
"app-name": null,
"app_route": null,
"azureapimanagemen": null,
"change-completed": null,
"change-item": null,
"change-request-id": null,
"change-request-reference": null,
"com.glide.embedded_help.category": null,
"component": null,
"copyright": "(C) Copyright 2025",
"crossroads": null,
"data": null,
"description": "The sequence of steps required to approve an invoice.",
"dominant_bundle": null,
"erp-canvas-video": null,
"fsm-mobile": null,
"fsm-route": null,
"fsm-sched-opt": null,
"fsm-wrk-order": null,
"genai-round-7": null,
"generator": "DITA-OT",
"glossPartOfSpeech": null,
"glossStatus": null,
"guided setup": null,
"guided tours": null,
"keywords": null,
"min-toc": null,
"mini": null,
"mini-to truec": null,
"mini-toc": null,
"mini_toc": null,
"minitoc": null,
"modification": null,
"now-assist-app-gen-video": null,
"order": null,
"page-type": null,
"page-type ": null,
"prodname": null,
"product": "product_name",
"product_name": null,
"release": null,
"resourceID": null,
"roles": null,
"route_page": null,
"route_params_listId": null,
"route_params_table": null,
"route_params_type": null,
"route_type": null,
"setconfigurationproperties": null,
"topic": null,
"translation-type": "source",
"version": null,
"workflow": "Creator, workflow_name",
"workplace-srvc-delvry-ditamap": null
},
"page_id": "reuse/glossary/A/gloss-approval-workflow-apo.html",
"page_key": 55688986,
"preprocessed_PDF": "https://downloads.docs.servicenow.com/pdf/enus/servicenow-yokohama-source-to-pay-operations-enus.pdf",
"rating": null,
"read_time_data": {
"char_count": 53,
"img_count": 0,
"read_time": 1,
"video_links": [
""
],
"word_count": 9
},
"related_links": [],
"search_title": null,
"title": "Approval workflow",
"topic_cluster": {
"clustered_by": {
"enabled": true,
"primary_key": "versions",
"primary_sort": "top-down",
"type": "subjecthead"
},
"clustered_labels": [
"versions"
],
"clustered_topics": [],
"clustering_title": "Zurich"
},
"topic_html": "<article class=\"hascomments\" data-page=\"bundle:zurich-source-to-pay-operations/enus/reuse/glossary/A/gloss-approval-workflow-apo.html\" id=\"bundle:zurich-source-to-pay-operations/enus/reuse/glossary/A/gloss-approval-workflow-apo.html\"><body id=\"gloss-approval-workflow-apo\"><main role=\"main\"><article role=\"article\" class=\"dita\" id=\"gloss-approval-workflow-apo\" aria-labelledby=\"title_gloss-approval-workflow-apo\">\n <h1 class=\"title glossterm topictitle1\" id=\"title_gloss-approval-workflow-apo\">Approval workflow</h1>\n <div class=\"abstract glossdef\">The sequence of steps required to approve an invoice.</div>\n \n<nav role=\"navigation\"></nav><nav role=\"navigation\" class=\"tasksNavigation\"></nav><nav role=\"navigation\" class=\"related-links\"></nav></article></main></body></article>",
"topic_language": "enus",
"views": 0,
"your_rating": null
} | # Approval workflow
The sequence of steps required to approve an invoice.
| ---
title: Approval workflow
description: The sequence of steps required to approve an invoice.
keywords: []
breadcrumbs:
- Finance and Supply Chain
- Accounts Payable Operations
- Accounts Payable Operations reference
- Approval Plan form
- Accounts Payable Operations glossary
- A
---
# Approval workflow
The sequence of steps required to approve an invoice.
|
https://www.servicenow.com/docs/en-US/bundle/zurich-source-to-pay-operations/page/reuse/glossary/A/gloss-assignment-rules-apo.html | https://servicenow-be-prod.servicenow.com/api/bundle/zurich-source-to-pay-operations/page/reuse/glossary/A/gloss-assignment-rules-apo.html | 2025-08-05 | daily | 0.5 | 268.xml | en-US | zurich-source-to-pay-operations | reuse/glossary/A/gloss-assignment-rules-apo.html | zurich | Assignment rules | Guidelines that determine how work items are assigned. | [] | [
"Finance and Supply Chain",
"Accounts Payable Operations",
"Accounts Payable Operations reference",
"Approval Plan form",
"Accounts Payable Operations glossary",
"A"
] | <article class="hascomments" data-page="bundle:zurich-source-to-pay-operations/enus/reuse/glossary/A/gloss-assignment-rules-apo.html" id="bundle:zurich-source-to-pay-operations/enus/reuse/glossary/A/gloss-assignment-rules-apo.html"><body id="gloss-assignment-rules-apo"><main role="main"><article role="article" class="dita" id="gloss-assignment-rules-apo" aria-labelledby="title_gloss-assignment-rules-apo">
<h1 class="title glossterm topictitle1" id="title_gloss-assignment-rules-apo">Assignment rules</h1>
<div class="abstract glossdef">Guidelines that determine how work items are assigned.</div>
<nav role="navigation"></nav><nav role="navigation" class="tasksNavigation"></nav><nav role="navigation" class="related-links"></nav></article></main></body></article> | {
"attachments": {
"all_attachments": null,
"topic_attachments": []
},
"available_languages": [
"enus"
],
"breadcrumbs": [
{
"title": "Finance and Supply Chain",
"topic_id": "product/source-to-pay-operations/concept/finance-supply-chain-landing.html"
},
{
"title": "Accounts Payable Operations",
"topic_id": "product/accounts-payable-operations/concept/acc-pay-mgmt-landing-page.html"
},
{
"title": "Accounts Payable Operations reference",
"topic_id": "product/accounts-payable-operations/reference/acc-pay-reference.html"
},
{
"title": "Approval Plan form",
"topic_id": "product/accounts-payable-operations/reference/approval-plan-form.html"
},
{
"title": "Accounts Payable Operations glossary",
"topic_id": "product/accounts-payable-operations/concept/apo-glossary.html"
},
{
"title": "A",
"topic_id": "product/accounts-payable-operations/concept/gloss-group-a-apo.html"
}
],
"breadcrumbs_html": "<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations\">Zurich Finance and Supply Chain</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/source-to-pay-operations/concept/finance-supply-chain-landing.html\">Finance and Supply Chain</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/concept/acc-pay-mgmt-landing-page.html\">Accounts Payable Operations</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/reference/acc-pay-reference.html\">Accounts Payable Operations reference</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/reference/approval-plan-form.html\">Approval Plan form</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/concept/apo-glossary.html\">Accounts Payable Operations glossary</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/concept/gloss-group-a-apo.html\">A</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<span class=\"active\">Assignment rules</span>",
"bundle_id": "zurich-source-to-pay-operations",
"bundle_key": 2735,
"bundle_landing_page": "product/source-to-pay-operations/concept/finance-supply-chain-landing.html",
"bundle_subtitle": null,
"bundle_title": "Zurich Finance and Supply Chain",
"canonical_link": null,
"dates": {
"Added on": "2025-08-05T13:11:54.216332Z",
"Created on": "2024-11-04T00:00:00Z",
"Initial upload": "2025-07-30T22:25:52.095402Z",
"Updated on": "2025-07-31T00:00:00Z"
},
"dislike_url": "https://servicenow-be-prod.servicenow.com/dislike/55688987",
"dislikes": 0,
"es_archived_content": false,
"is_in_fav": false,
"is_liked": null,
"is_watched": false,
"keywords": [
" zurich zurich"
],
"labels": [
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "zurich",
"navtitle": "Zurich",
"outputclasses": [],
"subjectHeadId": "versions",
"subjectheadNavtitle": "Versions",
"visibility": "show-facet"
},
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "apmgt",
"navtitle": "Accounts Payable Operations",
"outputclasses": [],
"subjectHeadId": "products",
"subjectheadNavtitle": "Products",
"visibility": "show-facet"
}
],
"labels_text": "Versions > Zurich; Products > Finance and Supply Chain > Accounts Payable Operations",
"like_url": "https://servicenow-be-prod.servicenow.com/like/55688987",
"likes": 0,
"metadata": {
"AI Search": null,
"AI Search Assist": null,
"Application Insights": null,
"Capabilities": null,
"Code Signing": null,
"Contextual Search": null,
"DC.contributor": null,
"DC.coverage": null,
"DC.creator": "ServiceNow",
"DC.date.created": "2024-11-04T05:50:30+05:30",
"DC.date.modified": "2025-07-31",
"DC.format": "HTML5",
"DC.identifier": "gloss-assignment-rules-apo",
"DC.language": null,
"DC.relation": "../../../product/accounts-payable-operations/concept/gloss-group-a-apo.html",
"DC.rights.owner": "(C) Copyright 2025",
"DC.subject": null,
"DC.type": "glossentry",
"Data Discovery": null,
"Data Policy": null,
"Data Privacy": null,
"Discovery": null,
"External Content for AI Search": null,
"Field Administration": null,
"Field Normalization": null,
"Key Management Framework": null,
"Localization Framework": null,
"Now Platform": null,
"PlatSec": null,
"Platform": null,
"Platform Administration": null,
"Platform Performance": null,
"Platform Privacy": null,
"Proactive Triggers": null,
"Process Optimization": null,
"RN doc editing record number": null,
"Search Administration": null,
"Secrets Management": null,
"ServiceNow AI Platform": null,
"State Model": null,
"Subscription Management": null,
"Task Communications Management": null,
"Timeline Visualizations": null,
"User Administration": null,
"User Experience Analytics": null,
"Zing": null,
"ai-now-assist": null,
"app-name": null,
"app_route": null,
"azureapimanagemen": null,
"change-completed": null,
"change-item": null,
"change-request-id": null,
"change-request-reference": null,
"com.glide.embedded_help.category": null,
"component": null,
"copyright": "(C) Copyright 2025",
"crossroads": null,
"data": null,
"description": "Guidelines that determine how work items are assigned.",
"dominant_bundle": null,
"erp-canvas-video": null,
"fsm-mobile": null,
"fsm-route": null,
"fsm-sched-opt": null,
"fsm-wrk-order": null,
"genai-round-7": null,
"generator": "DITA-OT",
"glossPartOfSpeech": null,
"glossStatus": null,
"guided setup": null,
"guided tours": null,
"keywords": null,
"min-toc": null,
"mini": null,
"mini-to truec": null,
"mini-toc": null,
"mini_toc": null,
"minitoc": null,
"modification": null,
"now-assist-app-gen-video": null,
"order": null,
"page-type": null,
"page-type ": null,
"prodname": null,
"product": "product_name",
"product_name": null,
"release": null,
"resourceID": null,
"roles": null,
"route_page": null,
"route_params_listId": null,
"route_params_table": null,
"route_params_type": null,
"route_type": null,
"setconfigurationproperties": null,
"topic": null,
"translation-type": "source",
"version": null,
"workflow": "Creator, workflow_name",
"workplace-srvc-delvry-ditamap": null
},
"page_id": "reuse/glossary/A/gloss-assignment-rules-apo.html",
"page_key": 55688987,
"preprocessed_PDF": "https://downloads.docs.servicenow.com/pdf/enus/servicenow-yokohama-source-to-pay-operations-enus.pdf",
"rating": null,
"read_time_data": {
"char_count": 54,
"img_count": 0,
"read_time": 1,
"video_links": [
""
],
"word_count": 8
},
"related_links": [],
"search_title": null,
"title": "Assignment rules",
"topic_cluster": {
"clustered_by": {
"enabled": true,
"primary_key": "versions",
"primary_sort": "top-down",
"type": "subjecthead"
},
"clustered_labels": [
"versions"
],
"clustered_topics": [],
"clustering_title": "Zurich"
},
"topic_html": "<article class=\"hascomments\" data-page=\"bundle:zurich-source-to-pay-operations/enus/reuse/glossary/A/gloss-assignment-rules-apo.html\" id=\"bundle:zurich-source-to-pay-operations/enus/reuse/glossary/A/gloss-assignment-rules-apo.html\"><body id=\"gloss-assignment-rules-apo\"><main role=\"main\"><article role=\"article\" class=\"dita\" id=\"gloss-assignment-rules-apo\" aria-labelledby=\"title_gloss-assignment-rules-apo\">\n <h1 class=\"title glossterm topictitle1\" id=\"title_gloss-assignment-rules-apo\">Assignment rules</h1>\n <div class=\"abstract glossdef\">Guidelines that determine how work items are assigned.</div>\n \n<nav role=\"navigation\"></nav><nav role=\"navigation\" class=\"tasksNavigation\"></nav><nav role=\"navigation\" class=\"related-links\"></nav></article></main></body></article>",
"topic_language": "enus",
"views": 0,
"your_rating": null
} | # Assignment rules
Guidelines that determine how work items are assigned.
| ---
title: Assignment rules
description: Guidelines that determine how work items are assigned.
keywords: []
breadcrumbs:
- Finance and Supply Chain
- Accounts Payable Operations
- Accounts Payable Operations reference
- Approval Plan form
- Accounts Payable Operations glossary
- A
---
# Assignment rules
Guidelines that determine how work items are assigned.
|
https://www.servicenow.com/docs/en-US/bundle/zurich-source-to-pay-operations/page/reuse/glossary/A/gloss-awa-apo.html | https://servicenow-be-prod.servicenow.com/api/bundle/zurich-source-to-pay-operations/page/reuse/glossary/A/gloss-awa-apo.html | 2025-08-05 | daily | 0.5 | 268.xml | en-US | zurich-source-to-pay-operations | reuse/glossary/A/gloss-awa-apo.html | zurich | Advanced work assignment for Accounts Payable Operations | An application that automatically assigns work items to agents based on their availability, capacity, and skills to resolve invoice cases within Accounts Payable Operations . | [] | [
"Finance and Supply Chain",
"Accounts Payable Operations",
"Accounts Payable Operations reference",
"Approval Plan form",
"Accounts Payable Operations glossary",
"A"
] | <article class="hascomments" data-page="bundle:zurich-source-to-pay-operations/enus/reuse/glossary/A/gloss-awa-apo.html" id="bundle:zurich-source-to-pay-operations/enus/reuse/glossary/A/gloss-awa-apo.html"><body id="gloss-awa-apo"><main role="main"><article role="article" class="dita" id="gloss-awa-apo" aria-labelledby="title_gloss-awa-apo">
<h1 class="title glossterm topictitle1" id="title_gloss-awa-apo">Advanced work assignment for <span class="ph">Accounts Payable Operations</span></h1>
<div class="abstract glossdef">An application that automatically assigns work items to agents based on their availability, capacity, and skills to resolve invoice cases within <span class="ph">Accounts Payable Operations</span>.</div>
<nav role="navigation"></nav><nav role="navigation" class="tasksNavigation"></nav><nav role="navigation" class="related-links"></nav></article></main></body></article> | {
"attachments": {
"all_attachments": null,
"topic_attachments": []
},
"available_languages": [
"enus"
],
"breadcrumbs": [
{
"title": "Finance and Supply Chain",
"topic_id": "product/source-to-pay-operations/concept/finance-supply-chain-landing.html"
},
{
"title": "Accounts Payable Operations",
"topic_id": "product/accounts-payable-operations/concept/acc-pay-mgmt-landing-page.html"
},
{
"title": "Accounts Payable Operations reference",
"topic_id": "product/accounts-payable-operations/reference/acc-pay-reference.html"
},
{
"title": "Approval Plan form",
"topic_id": "product/accounts-payable-operations/reference/approval-plan-form.html"
},
{
"title": "Accounts Payable Operations glossary",
"topic_id": "product/accounts-payable-operations/concept/apo-glossary.html"
},
{
"title": "A",
"topic_id": "product/accounts-payable-operations/concept/gloss-group-a-apo.html"
}
],
"breadcrumbs_html": "<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations\">Zurich Finance and Supply Chain</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/source-to-pay-operations/concept/finance-supply-chain-landing.html\">Finance and Supply Chain</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/concept/acc-pay-mgmt-landing-page.html\">Accounts Payable Operations</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/reference/acc-pay-reference.html\">Accounts Payable Operations reference</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/reference/approval-plan-form.html\">Approval Plan form</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/concept/apo-glossary.html\">Accounts Payable Operations glossary</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/concept/gloss-group-a-apo.html\">A</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<span class=\"active\">Advanced work assignment for Accounts Payable Operations</span>",
"bundle_id": "zurich-source-to-pay-operations",
"bundle_key": 2735,
"bundle_landing_page": "product/source-to-pay-operations/concept/finance-supply-chain-landing.html",
"bundle_subtitle": null,
"bundle_title": "Zurich Finance and Supply Chain",
"canonical_link": null,
"dates": {
"Added on": "2025-08-05T13:11:54.216332Z",
"Created on": "2024-11-04T00:00:00Z",
"Initial upload": "2025-07-30T22:25:52.095402Z",
"Updated on": "2025-07-31T00:00:00Z"
},
"dislike_url": "https://servicenow-be-prod.servicenow.com/dislike/55688988",
"dislikes": 0,
"es_archived_content": false,
"is_in_fav": false,
"is_liked": null,
"is_watched": false,
"keywords": [
" zurich zurich"
],
"labels": [
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "zurich",
"navtitle": "Zurich",
"outputclasses": [],
"subjectHeadId": "versions",
"subjectheadNavtitle": "Versions",
"visibility": "show-facet"
},
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "apmgt",
"navtitle": "Accounts Payable Operations",
"outputclasses": [],
"subjectHeadId": "products",
"subjectheadNavtitle": "Products",
"visibility": "show-facet"
}
],
"labels_text": "Versions > Zurich; Products > Finance and Supply Chain > Accounts Payable Operations",
"like_url": "https://servicenow-be-prod.servicenow.com/like/55688988",
"likes": 0,
"metadata": {
"AI Search": null,
"AI Search Assist": null,
"Application Insights": null,
"Capabilities": null,
"Code Signing": null,
"Contextual Search": null,
"DC.contributor": null,
"DC.coverage": null,
"DC.creator": "ServiceNow",
"DC.date.created": "2024-11-04T05:41:23+05:30",
"DC.date.modified": "2025-07-31",
"DC.format": "HTML5",
"DC.identifier": "gloss-awa-apo",
"DC.language": null,
"DC.relation": "../../../product/accounts-payable-operations/concept/gloss-group-a-apo.html",
"DC.rights.owner": "(C) Copyright 2025",
"DC.subject": null,
"DC.type": "glossentry",
"Data Discovery": null,
"Data Policy": null,
"Data Privacy": null,
"Discovery": null,
"External Content for AI Search": null,
"Field Administration": null,
"Field Normalization": null,
"Key Management Framework": null,
"Localization Framework": null,
"Now Platform": null,
"PlatSec": null,
"Platform": null,
"Platform Administration": null,
"Platform Performance": null,
"Platform Privacy": null,
"Proactive Triggers": null,
"Process Optimization": null,
"RN doc editing record number": null,
"Search Administration": null,
"Secrets Management": null,
"ServiceNow AI Platform": null,
"State Model": null,
"Subscription Management": null,
"Task Communications Management": null,
"Timeline Visualizations": null,
"User Administration": null,
"User Experience Analytics": null,
"Zing": null,
"ai-now-assist": null,
"app-name": null,
"app_route": null,
"azureapimanagemen": null,
"change-completed": null,
"change-item": null,
"change-request-id": null,
"change-request-reference": null,
"com.glide.embedded_help.category": null,
"component": null,
"copyright": "(C) Copyright 2025",
"crossroads": null,
"data": null,
"description": "An application that automatically assigns work items to agents based on their availability, capacity, and skills to resolve invoice cases within Accounts Payable Operations .",
"dominant_bundle": null,
"erp-canvas-video": null,
"fsm-mobile": null,
"fsm-route": null,
"fsm-sched-opt": null,
"fsm-wrk-order": null,
"genai-round-7": null,
"generator": "DITA-OT",
"glossPartOfSpeech": null,
"glossStatus": null,
"guided setup": null,
"guided tours": null,
"keywords": null,
"min-toc": null,
"mini": null,
"mini-to truec": null,
"mini-toc": null,
"mini_toc": null,
"minitoc": null,
"modification": null,
"now-assist-app-gen-video": null,
"order": null,
"page-type": null,
"page-type ": null,
"prodname": null,
"product": "product_name",
"product_name": null,
"release": null,
"resourceID": null,
"roles": null,
"route_page": null,
"route_params_listId": null,
"route_params_table": null,
"route_params_type": null,
"route_type": null,
"setconfigurationproperties": null,
"topic": null,
"translation-type": "source",
"version": null,
"workflow": "Creator, workflow_name",
"workplace-srvc-delvry-ditamap": null
},
"page_id": "reuse/glossary/A/gloss-awa-apo.html",
"page_key": 55688988,
"preprocessed_PDF": "https://downloads.docs.servicenow.com/pdf/enus/servicenow-yokohama-source-to-pay-operations-enus.pdf",
"rating": null,
"read_time_data": {
"char_count": 174,
"img_count": 0,
"read_time": 1,
"video_links": [
""
],
"word_count": 25
},
"related_links": [],
"search_title": null,
"title": "Advanced work assignment for Accounts Payable Operations",
"topic_cluster": {
"clustered_by": {
"enabled": true,
"primary_key": "versions",
"primary_sort": "top-down",
"type": "subjecthead"
},
"clustered_labels": [
"versions"
],
"clustered_topics": [],
"clustering_title": "Zurich"
},
"topic_html": "<article class=\"hascomments\" data-page=\"bundle:zurich-source-to-pay-operations/enus/reuse/glossary/A/gloss-awa-apo.html\" id=\"bundle:zurich-source-to-pay-operations/enus/reuse/glossary/A/gloss-awa-apo.html\"><body id=\"gloss-awa-apo\"><main role=\"main\"><article role=\"article\" class=\"dita\" id=\"gloss-awa-apo\" aria-labelledby=\"title_gloss-awa-apo\">\n <h1 class=\"title glossterm topictitle1\" id=\"title_gloss-awa-apo\">Advanced work assignment for <span class=\"ph\">Accounts Payable Operations</span></h1>\n <div class=\"abstract glossdef\">An application that automatically assigns work items to agents based on their availability, capacity, and skills to resolve invoice cases within <span class=\"ph\">Accounts Payable Operations</span>.</div>\n \n<nav role=\"navigation\"></nav><nav role=\"navigation\" class=\"tasksNavigation\"></nav><nav role=\"navigation\" class=\"related-links\"></nav></article></main></body></article>",
"topic_language": "enus",
"views": 0,
"your_rating": null
} | # Advanced work assignment for Accounts Payable Operations
An application that automatically assigns work items to agents based on their availability, capacity, and skills to resolve invoice cases within Accounts Payable Operations.
| ---
title: Advanced work assignment for Accounts Payable Operations
description: An application that automatically assigns work items to agents based
on their availability, capacity, and skills to resolve invoice cases within Accounts
Payable Operations .
keywords: []
breadcrumbs:
- Finance and Supply Chain
- Accounts Payable Operations
- Accounts Payable Operations reference
- Approval Plan form
- Accounts Payable Operations glossary
- A
---
# Advanced work assignment for Accounts Payable Operations
An application that automatically assigns work items to agents based on their availability, capacity, and skills to resolve invoice cases within Accounts Payable Operations.
|
https://www.servicenow.com/docs/en-US/bundle/zurich-source-to-pay-operations/page/reuse/glossary/D/gloss-data-capture-apo.html | https://servicenow-be-prod.servicenow.com/api/bundle/zurich-source-to-pay-operations/page/reuse/glossary/D/gloss-data-capture-apo.html | 2025-08-05 | daily | 0.5 | 268.xml | en-US | zurich-source-to-pay-operations | reuse/glossary/D/gloss-data-capture-apo.html | zurich | Data capture | The process of collecting and digitizing invoice data. | [] | [
"Finance and Supply Chain",
"Accounts Payable Operations",
"Accounts Payable Operations reference",
"Approval Plan form",
"Accounts Payable Operations glossary",
"D"
] | <article class="hascomments" data-page="bundle:zurich-source-to-pay-operations/enus/reuse/glossary/D/gloss-data-capture-apo.html" id="bundle:zurich-source-to-pay-operations/enus/reuse/glossary/D/gloss-data-capture-apo.html"><body id="gloss-data-capture-apo"><main role="main"><article role="article" class="dita" id="gloss-data-capture-apo" aria-labelledby="title_gloss-data-capture-apo">
<h1 class="title glossterm topictitle1" id="title_gloss-data-capture-apo">Data capture</h1>
<div class="abstract glossdef">The process of collecting and digitizing invoice data.</div>
<nav role="navigation"></nav><nav role="navigation" class="tasksNavigation"></nav><nav role="navigation" class="related-links"></nav></article></main></body></article> | {
"attachments": {
"all_attachments": null,
"topic_attachments": []
},
"available_languages": [
"enus"
],
"breadcrumbs": [
{
"title": "Finance and Supply Chain",
"topic_id": "product/source-to-pay-operations/concept/finance-supply-chain-landing.html"
},
{
"title": "Accounts Payable Operations",
"topic_id": "product/accounts-payable-operations/concept/acc-pay-mgmt-landing-page.html"
},
{
"title": "Accounts Payable Operations reference",
"topic_id": "product/accounts-payable-operations/reference/acc-pay-reference.html"
},
{
"title": "Approval Plan form",
"topic_id": "product/accounts-payable-operations/reference/approval-plan-form.html"
},
{
"title": "Accounts Payable Operations glossary",
"topic_id": "product/accounts-payable-operations/concept/apo-glossary.html"
},
{
"title": "D",
"topic_id": "product/accounts-payable-operations/concept/gloss-group-d-apo.html"
}
],
"breadcrumbs_html": "<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations\">Zurich Finance and Supply Chain</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/source-to-pay-operations/concept/finance-supply-chain-landing.html\">Finance and Supply Chain</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/concept/acc-pay-mgmt-landing-page.html\">Accounts Payable Operations</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/reference/acc-pay-reference.html\">Accounts Payable Operations reference</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/reference/approval-plan-form.html\">Approval Plan form</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/concept/apo-glossary.html\">Accounts Payable Operations glossary</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/concept/gloss-group-d-apo.html\">D</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<span class=\"active\">Data capture</span>",
"bundle_id": "zurich-source-to-pay-operations",
"bundle_key": 2735,
"bundle_landing_page": "product/source-to-pay-operations/concept/finance-supply-chain-landing.html",
"bundle_subtitle": null,
"bundle_title": "Zurich Finance and Supply Chain",
"canonical_link": null,
"dates": {
"Added on": "2025-08-05T13:11:54.216332Z",
"Created on": "2024-11-04T00:00:00Z",
"Initial upload": "2025-07-30T22:25:52.095402Z",
"Updated on": "2025-07-31T00:00:00Z"
},
"dislike_url": "https://servicenow-be-prod.servicenow.com/dislike/55688989",
"dislikes": 0,
"es_archived_content": false,
"is_in_fav": false,
"is_liked": null,
"is_watched": false,
"keywords": [
" zurich zurich"
],
"labels": [
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "zurich",
"navtitle": "Zurich",
"outputclasses": [],
"subjectHeadId": "versions",
"subjectheadNavtitle": "Versions",
"visibility": "show-facet"
},
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "apmgt",
"navtitle": "Accounts Payable Operations",
"outputclasses": [],
"subjectHeadId": "products",
"subjectheadNavtitle": "Products",
"visibility": "show-facet"
}
],
"labels_text": "Versions > Zurich; Products > Finance and Supply Chain > Accounts Payable Operations",
"like_url": "https://servicenow-be-prod.servicenow.com/like/55688989",
"likes": 0,
"metadata": {
"AI Search": null,
"AI Search Assist": null,
"Application Insights": null,
"Capabilities": null,
"Code Signing": null,
"Contextual Search": null,
"DC.contributor": null,
"DC.coverage": null,
"DC.creator": "ServiceNow",
"DC.date.created": "2024-11-04T05:39:07+05:30",
"DC.date.modified": "2025-07-31",
"DC.format": "HTML5",
"DC.identifier": "gloss-data-capture-apo",
"DC.language": null,
"DC.relation": "../../../product/accounts-payable-operations/concept/gloss-group-d-apo.html",
"DC.rights.owner": "(C) Copyright 2025",
"DC.subject": null,
"DC.type": "glossentry",
"Data Discovery": null,
"Data Policy": null,
"Data Privacy": null,
"Discovery": null,
"External Content for AI Search": null,
"Field Administration": null,
"Field Normalization": null,
"Key Management Framework": null,
"Localization Framework": null,
"Now Platform": null,
"PlatSec": null,
"Platform": null,
"Platform Administration": null,
"Platform Performance": null,
"Platform Privacy": null,
"Proactive Triggers": null,
"Process Optimization": null,
"RN doc editing record number": null,
"Search Administration": null,
"Secrets Management": null,
"ServiceNow AI Platform": null,
"State Model": null,
"Subscription Management": null,
"Task Communications Management": null,
"Timeline Visualizations": null,
"User Administration": null,
"User Experience Analytics": null,
"Zing": null,
"ai-now-assist": null,
"app-name": null,
"app_route": null,
"azureapimanagemen": null,
"change-completed": null,
"change-item": null,
"change-request-id": null,
"change-request-reference": null,
"com.glide.embedded_help.category": null,
"component": null,
"copyright": "(C) Copyright 2025",
"crossroads": null,
"data": null,
"description": "The process of collecting and digitizing invoice data.",
"dominant_bundle": null,
"erp-canvas-video": null,
"fsm-mobile": null,
"fsm-route": null,
"fsm-sched-opt": null,
"fsm-wrk-order": null,
"genai-round-7": null,
"generator": "DITA-OT",
"glossPartOfSpeech": null,
"glossStatus": null,
"guided setup": null,
"guided tours": null,
"keywords": null,
"min-toc": null,
"mini": null,
"mini-to truec": null,
"mini-toc": null,
"mini_toc": null,
"minitoc": null,
"modification": null,
"now-assist-app-gen-video": null,
"order": null,
"page-type": null,
"page-type ": null,
"prodname": null,
"product": "product_name",
"product_name": null,
"release": null,
"resourceID": null,
"roles": null,
"route_page": null,
"route_params_listId": null,
"route_params_table": null,
"route_params_type": null,
"route_type": null,
"setconfigurationproperties": null,
"topic": null,
"translation-type": "source",
"version": null,
"workflow": "Creator, workflow_name",
"workplace-srvc-delvry-ditamap": null
},
"page_id": "reuse/glossary/D/gloss-data-capture-apo.html",
"page_key": 55688989,
"preprocessed_PDF": "https://downloads.docs.servicenow.com/pdf/enus/servicenow-yokohama-source-to-pay-operations-enus.pdf",
"rating": null,
"read_time_data": {
"char_count": 54,
"img_count": 0,
"read_time": 1,
"video_links": [
""
],
"word_count": 8
},
"related_links": [],
"search_title": null,
"title": "Data capture",
"topic_cluster": {
"clustered_by": {
"enabled": true,
"primary_key": "versions",
"primary_sort": "top-down",
"type": "subjecthead"
},
"clustered_labels": [
"versions"
],
"clustered_topics": [],
"clustering_title": "Zurich"
},
"topic_html": "<article class=\"hascomments\" data-page=\"bundle:zurich-source-to-pay-operations/enus/reuse/glossary/D/gloss-data-capture-apo.html\" id=\"bundle:zurich-source-to-pay-operations/enus/reuse/glossary/D/gloss-data-capture-apo.html\"><body id=\"gloss-data-capture-apo\"><main role=\"main\"><article role=\"article\" class=\"dita\" id=\"gloss-data-capture-apo\" aria-labelledby=\"title_gloss-data-capture-apo\">\n <h1 class=\"title glossterm topictitle1\" id=\"title_gloss-data-capture-apo\">Data capture</h1>\n <div class=\"abstract glossdef\">The process of collecting and digitizing invoice data.</div>\n \n<nav role=\"navigation\"></nav><nav role=\"navigation\" class=\"tasksNavigation\"></nav><nav role=\"navigation\" class=\"related-links\"></nav></article></main></body></article>",
"topic_language": "enus",
"views": 0,
"your_rating": null
} | # Data capture
The process of collecting and digitizing invoice data.
| ---
title: Data capture
description: The process of collecting and digitizing invoice data.
keywords: []
breadcrumbs:
- Finance and Supply Chain
- Accounts Payable Operations
- Accounts Payable Operations reference
- Approval Plan form
- Accounts Payable Operations glossary
- D
---
# Data capture
The process of collecting and digitizing invoice data.
|
https://www.servicenow.com/docs/en-US/bundle/zurich-source-to-pay-operations/page/reuse/glossary/D/gloss-data-security-apo.html | https://servicenow-be-prod.servicenow.com/api/bundle/zurich-source-to-pay-operations/page/reuse/glossary/D/gloss-data-security-apo.html | 2025-08-05 | daily | 0.5 | 268.xml | en-US | zurich-source-to-pay-operations | reuse/glossary/D/gloss-data-security-apo.html | zurich | Data security | Measures to protect sensitive information within the system. | [] | [
"Finance and Supply Chain",
"Accounts Payable Operations",
"Accounts Payable Operations reference",
"Approval Plan form",
"Accounts Payable Operations glossary",
"D"
] | <article class="hascomments" data-page="bundle:zurich-source-to-pay-operations/enus/reuse/glossary/D/gloss-data-security-apo.html" id="bundle:zurich-source-to-pay-operations/enus/reuse/glossary/D/gloss-data-security-apo.html"><body id="gloss-data-security-apo"><main role="main"><article role="article" class="dita" id="gloss-data-security-apo" aria-labelledby="title_gloss-data-security-apo">
<h1 class="title glossterm topictitle1" id="title_gloss-data-security-apo">Data security</h1>
<div class="abstract glossdef">Measures to protect sensitive information within the system.</div>
<nav role="navigation"></nav><nav role="navigation" class="tasksNavigation"></nav><nav role="navigation" class="related-links"></nav></article></main></body></article> | {
"attachments": {
"all_attachments": null,
"topic_attachments": []
},
"available_languages": [
"enus"
],
"breadcrumbs": [
{
"title": "Finance and Supply Chain",
"topic_id": "product/source-to-pay-operations/concept/finance-supply-chain-landing.html"
},
{
"title": "Accounts Payable Operations",
"topic_id": "product/accounts-payable-operations/concept/acc-pay-mgmt-landing-page.html"
},
{
"title": "Accounts Payable Operations reference",
"topic_id": "product/accounts-payable-operations/reference/acc-pay-reference.html"
},
{
"title": "Approval Plan form",
"topic_id": "product/accounts-payable-operations/reference/approval-plan-form.html"
},
{
"title": "Accounts Payable Operations glossary",
"topic_id": "product/accounts-payable-operations/concept/apo-glossary.html"
},
{
"title": "D",
"topic_id": "product/accounts-payable-operations/concept/gloss-group-d-apo.html"
}
],
"breadcrumbs_html": "<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations\">Zurich Finance and Supply Chain</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/source-to-pay-operations/concept/finance-supply-chain-landing.html\">Finance and Supply Chain</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/concept/acc-pay-mgmt-landing-page.html\">Accounts Payable Operations</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/reference/acc-pay-reference.html\">Accounts Payable Operations reference</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/reference/approval-plan-form.html\">Approval Plan form</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/concept/apo-glossary.html\">Accounts Payable Operations glossary</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/concept/gloss-group-d-apo.html\">D</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<span class=\"active\">Data security</span>",
"bundle_id": "zurich-source-to-pay-operations",
"bundle_key": 2735,
"bundle_landing_page": "product/source-to-pay-operations/concept/finance-supply-chain-landing.html",
"bundle_subtitle": null,
"bundle_title": "Zurich Finance and Supply Chain",
"canonical_link": null,
"dates": {
"Added on": "2025-08-05T13:11:54.216332Z",
"Created on": "2024-11-04T00:00:00Z",
"Initial upload": "2025-07-30T22:25:52.095402Z",
"Updated on": "2025-07-31T00:00:00Z"
},
"dislike_url": "https://servicenow-be-prod.servicenow.com/dislike/55688990",
"dislikes": 0,
"es_archived_content": false,
"is_in_fav": false,
"is_liked": null,
"is_watched": false,
"keywords": [
" zurich zurich"
],
"labels": [
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "zurich",
"navtitle": "Zurich",
"outputclasses": [],
"subjectHeadId": "versions",
"subjectheadNavtitle": "Versions",
"visibility": "show-facet"
},
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "apmgt",
"navtitle": "Accounts Payable Operations",
"outputclasses": [],
"subjectHeadId": "products",
"subjectheadNavtitle": "Products",
"visibility": "show-facet"
}
],
"labels_text": "Versions > Zurich; Products > Finance and Supply Chain > Accounts Payable Operations",
"like_url": "https://servicenow-be-prod.servicenow.com/like/55688990",
"likes": 0,
"metadata": {
"AI Search": null,
"AI Search Assist": null,
"Application Insights": null,
"Capabilities": null,
"Code Signing": null,
"Contextual Search": null,
"DC.contributor": null,
"DC.coverage": null,
"DC.creator": "ServiceNow",
"DC.date.created": "2024-11-04T05:37:00+05:30",
"DC.date.modified": "2025-07-31",
"DC.format": "HTML5",
"DC.identifier": "gloss-data-security-apo",
"DC.language": null,
"DC.relation": "../../../product/accounts-payable-operations/concept/gloss-group-d-apo.html",
"DC.rights.owner": "(C) Copyright 2025",
"DC.subject": null,
"DC.type": "glossentry",
"Data Discovery": null,
"Data Policy": null,
"Data Privacy": null,
"Discovery": null,
"External Content for AI Search": null,
"Field Administration": null,
"Field Normalization": null,
"Key Management Framework": null,
"Localization Framework": null,
"Now Platform": null,
"PlatSec": null,
"Platform": null,
"Platform Administration": null,
"Platform Performance": null,
"Platform Privacy": null,
"Proactive Triggers": null,
"Process Optimization": null,
"RN doc editing record number": null,
"Search Administration": null,
"Secrets Management": null,
"ServiceNow AI Platform": null,
"State Model": null,
"Subscription Management": null,
"Task Communications Management": null,
"Timeline Visualizations": null,
"User Administration": null,
"User Experience Analytics": null,
"Zing": null,
"ai-now-assist": null,
"app-name": null,
"app_route": null,
"azureapimanagemen": null,
"change-completed": null,
"change-item": null,
"change-request-id": null,
"change-request-reference": null,
"com.glide.embedded_help.category": null,
"component": null,
"copyright": "(C) Copyright 2025",
"crossroads": null,
"data": null,
"description": "Measures to protect sensitive information within the system.",
"dominant_bundle": null,
"erp-canvas-video": null,
"fsm-mobile": null,
"fsm-route": null,
"fsm-sched-opt": null,
"fsm-wrk-order": null,
"genai-round-7": null,
"generator": "DITA-OT",
"glossPartOfSpeech": null,
"glossStatus": null,
"guided setup": null,
"guided tours": null,
"keywords": null,
"min-toc": null,
"mini": null,
"mini-to truec": null,
"mini-toc": null,
"mini_toc": null,
"minitoc": null,
"modification": null,
"now-assist-app-gen-video": null,
"order": null,
"page-type": null,
"page-type ": null,
"prodname": null,
"product": "product_name",
"product_name": null,
"release": null,
"resourceID": null,
"roles": null,
"route_page": null,
"route_params_listId": null,
"route_params_table": null,
"route_params_type": null,
"route_type": null,
"setconfigurationproperties": null,
"topic": null,
"translation-type": "source",
"version": null,
"workflow": "Creator, workflow_name",
"workplace-srvc-delvry-ditamap": null
},
"page_id": "reuse/glossary/D/gloss-data-security-apo.html",
"page_key": 55688990,
"preprocessed_PDF": "https://downloads.docs.servicenow.com/pdf/enus/servicenow-yokohama-source-to-pay-operations-enus.pdf",
"rating": null,
"read_time_data": {
"char_count": 60,
"img_count": 0,
"read_time": 1,
"video_links": [
""
],
"word_count": 8
},
"related_links": [],
"search_title": null,
"title": "Data security",
"topic_cluster": {
"clustered_by": {
"enabled": true,
"primary_key": "versions",
"primary_sort": "top-down",
"type": "subjecthead"
},
"clustered_labels": [
"versions"
],
"clustered_topics": [],
"clustering_title": "Zurich"
},
"topic_html": "<article class=\"hascomments\" data-page=\"bundle:zurich-source-to-pay-operations/enus/reuse/glossary/D/gloss-data-security-apo.html\" id=\"bundle:zurich-source-to-pay-operations/enus/reuse/glossary/D/gloss-data-security-apo.html\"><body id=\"gloss-data-security-apo\"><main role=\"main\"><article role=\"article\" class=\"dita\" id=\"gloss-data-security-apo\" aria-labelledby=\"title_gloss-data-security-apo\">\n <h1 class=\"title glossterm topictitle1\" id=\"title_gloss-data-security-apo\">Data security</h1>\n <div class=\"abstract glossdef\">Measures to protect sensitive information within the system.</div>\n \n<nav role=\"navigation\"></nav><nav role=\"navigation\" class=\"tasksNavigation\"></nav><nav role=\"navigation\" class=\"related-links\"></nav></article></main></body></article>",
"topic_language": "enus",
"views": 0,
"your_rating": null
} | # Data security
Measures to protect sensitive information within the system.
| ---
title: Data security
description: Measures to protect sensitive information within the system.
keywords: []
breadcrumbs:
- Finance and Supply Chain
- Accounts Payable Operations
- Accounts Payable Operations reference
- Approval Plan form
- Accounts Payable Operations glossary
- D
---
# Data security
Measures to protect sensitive information within the system.
|
https://www.servicenow.com/docs/en-US/bundle/zurich-source-to-pay-operations/page/reuse/glossary/D/gloss-doc-intel-apo.html | https://servicenow-be-prod.servicenow.com/api/bundle/zurich-source-to-pay-operations/page/reuse/glossary/D/gloss-doc-intel-apo.html | 2025-08-05 | daily | 0.5 | 268.xml | en-US | zurich-source-to-pay-operations | reuse/glossary/D/gloss-doc-intel-apo.html | zurich | Document intelligence | ServiceNow® AI-powered tool for extracting data from invoices. | [] | [
"Finance and Supply Chain",
"Accounts Payable Operations",
"Accounts Payable Operations reference",
"Approval Plan form",
"Accounts Payable Operations glossary",
"D"
] | <article class="hascomments" data-page="bundle:zurich-source-to-pay-operations/enus/reuse/glossary/D/gloss-doc-intel-apo.html" id="bundle:zurich-source-to-pay-operations/enus/reuse/glossary/D/gloss-doc-intel-apo.html"><body id="gloss-doc-intel-apo"><main role="main"><article role="article" class="dita" id="gloss-doc-intel-apo" aria-labelledby="title_gloss-doc-intel-apo">
<h1 class="title topictitle1" id="title_gloss-doc-intel-apo">Document intelligence</h1>
<div class="body conbody"><p class="shortdesc"><span class="ph">ServiceNow®</span> AI-powered tool for extracting data from invoices.</p></div>
<nav role="navigation"></nav><nav role="navigation" class="tasksNavigation"></nav><nav role="navigation" class="related-links"></nav></article></main></body></article> | {
"attachments": {
"all_attachments": null,
"topic_attachments": []
},
"available_languages": [
"enus"
],
"breadcrumbs": [
{
"title": "Finance and Supply Chain",
"topic_id": "product/source-to-pay-operations/concept/finance-supply-chain-landing.html"
},
{
"title": "Accounts Payable Operations",
"topic_id": "product/accounts-payable-operations/concept/acc-pay-mgmt-landing-page.html"
},
{
"title": "Accounts Payable Operations reference",
"topic_id": "product/accounts-payable-operations/reference/acc-pay-reference.html"
},
{
"title": "Approval Plan form",
"topic_id": "product/accounts-payable-operations/reference/approval-plan-form.html"
},
{
"title": "Accounts Payable Operations glossary",
"topic_id": "product/accounts-payable-operations/concept/apo-glossary.html"
},
{
"title": "D",
"topic_id": "product/accounts-payable-operations/concept/gloss-group-d-apo.html"
}
],
"breadcrumbs_html": "<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations\">Zurich Finance and Supply Chain</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/source-to-pay-operations/concept/finance-supply-chain-landing.html\">Finance and Supply Chain</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/concept/acc-pay-mgmt-landing-page.html\">Accounts Payable Operations</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/reference/acc-pay-reference.html\">Accounts Payable Operations reference</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/reference/approval-plan-form.html\">Approval Plan form</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/concept/apo-glossary.html\">Accounts Payable Operations glossary</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/concept/gloss-group-d-apo.html\">D</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<span class=\"active\">Document intelligence</span>",
"bundle_id": "zurich-source-to-pay-operations",
"bundle_key": 2735,
"bundle_landing_page": "product/source-to-pay-operations/concept/finance-supply-chain-landing.html",
"bundle_subtitle": null,
"bundle_title": "Zurich Finance and Supply Chain",
"canonical_link": null,
"dates": {
"Added on": "2025-08-05T13:11:54.216332Z",
"Created on": "2024-11-04T00:00:00Z",
"Initial upload": "2025-07-30T22:25:52.095402Z",
"Updated on": "2025-07-31T00:00:00Z"
},
"dislike_url": "https://servicenow-be-prod.servicenow.com/dislike/55688991",
"dislikes": 0,
"es_archived_content": false,
"is_in_fav": false,
"is_liked": null,
"is_watched": false,
"keywords": [
" zurich zurich"
],
"labels": [
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "zurich",
"navtitle": "Zurich",
"outputclasses": [],
"subjectHeadId": "versions",
"subjectheadNavtitle": "Versions",
"visibility": "show-facet"
},
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "apmgt",
"navtitle": "Accounts Payable Operations",
"outputclasses": [],
"subjectHeadId": "products",
"subjectheadNavtitle": "Products",
"visibility": "show-facet"
}
],
"labels_text": "Versions > Zurich; Products > Finance and Supply Chain > Accounts Payable Operations",
"like_url": "https://servicenow-be-prod.servicenow.com/like/55688991",
"likes": 0,
"metadata": {
"AI Search": null,
"AI Search Assist": null,
"Application Insights": null,
"Capabilities": null,
"Code Signing": null,
"Contextual Search": null,
"DC.contributor": null,
"DC.coverage": null,
"DC.creator": "ServiceNow",
"DC.date.created": "2024-11-04T05:14:00+05:30",
"DC.date.modified": "2025-07-31",
"DC.format": "HTML5",
"DC.identifier": "gloss-doc-intel-apo",
"DC.language": null,
"DC.relation": "../../../product/accounts-payable-operations/concept/gloss-group-d-apo.html",
"DC.rights.owner": "(C) Copyright 2025",
"DC.subject": null,
"DC.type": "concept",
"Data Discovery": null,
"Data Policy": null,
"Data Privacy": null,
"Discovery": null,
"External Content for AI Search": null,
"Field Administration": null,
"Field Normalization": null,
"Key Management Framework": null,
"Localization Framework": null,
"Now Platform": null,
"PlatSec": null,
"Platform": null,
"Platform Administration": null,
"Platform Performance": null,
"Platform Privacy": null,
"Proactive Triggers": null,
"Process Optimization": null,
"RN doc editing record number": null,
"Search Administration": null,
"Secrets Management": null,
"ServiceNow AI Platform": null,
"State Model": null,
"Subscription Management": null,
"Task Communications Management": null,
"Timeline Visualizations": null,
"User Administration": null,
"User Experience Analytics": null,
"Zing": null,
"ai-now-assist": null,
"app-name": null,
"app_route": null,
"azureapimanagemen": null,
"change-completed": null,
"change-item": null,
"change-request-id": null,
"change-request-reference": null,
"com.glide.embedded_help.category": null,
"component": null,
"copyright": "(C) Copyright 2025",
"crossroads": null,
"data": null,
"description": "ServiceNow® AI-powered tool for extracting data from invoices.",
"dominant_bundle": null,
"erp-canvas-video": null,
"fsm-mobile": null,
"fsm-route": null,
"fsm-sched-opt": null,
"fsm-wrk-order": null,
"genai-round-7": null,
"generator": "DITA-OT",
"glossPartOfSpeech": null,
"glossStatus": null,
"guided setup": null,
"guided tours": null,
"keywords": null,
"min-toc": null,
"mini": null,
"mini-to truec": null,
"mini-toc": null,
"mini_toc": null,
"minitoc": null,
"modification": null,
"now-assist-app-gen-video": null,
"order": null,
"page-type": null,
"page-type ": null,
"prodname": null,
"product": null,
"product_name": null,
"release": null,
"resourceID": null,
"roles": null,
"route_page": null,
"route_params_listId": null,
"route_params_table": null,
"route_params_type": null,
"route_type": null,
"setconfigurationproperties": null,
"topic": null,
"translation-type": "source",
"version": null,
"workflow": "Creator",
"workplace-srvc-delvry-ditamap": null
},
"page_id": "reuse/glossary/D/gloss-doc-intel-apo.html",
"page_key": 55688991,
"preprocessed_PDF": "https://downloads.docs.servicenow.com/pdf/enus/servicenow-yokohama-source-to-pay-operations-enus.pdf",
"rating": null,
"read_time_data": {
"char_count": 62,
"img_count": 0,
"read_time": 1,
"video_links": [
""
],
"word_count": 8
},
"related_links": [],
"search_title": null,
"title": "Document intelligence",
"topic_cluster": {
"clustered_by": {
"enabled": true,
"primary_key": "versions",
"primary_sort": "top-down",
"type": "subjecthead"
},
"clustered_labels": [
"versions"
],
"clustered_topics": [],
"clustering_title": "Zurich"
},
"topic_html": "<article class=\"hascomments\" data-page=\"bundle:zurich-source-to-pay-operations/enus/reuse/glossary/D/gloss-doc-intel-apo.html\" id=\"bundle:zurich-source-to-pay-operations/enus/reuse/glossary/D/gloss-doc-intel-apo.html\"><body id=\"gloss-doc-intel-apo\"><main role=\"main\"><article role=\"article\" class=\"dita\" id=\"gloss-doc-intel-apo\" aria-labelledby=\"title_gloss-doc-intel-apo\">\n <h1 class=\"title topictitle1\" id=\"title_gloss-doc-intel-apo\">Document intelligence</h1>\n \n \n <div class=\"body conbody\"><p class=\"shortdesc\"><span class=\"ph\">ServiceNow®</span> AI-powered tool for extracting data from invoices.</p></div>\n<nav role=\"navigation\"></nav><nav role=\"navigation\" class=\"tasksNavigation\"></nav><nav role=\"navigation\" class=\"related-links\"></nav></article></main></body></article>",
"topic_language": "enus",
"views": 0,
"your_rating": null
} | # Document intelligence
ServiceNow® AI-powered tool for extracting data from invoices.
| ---
title: Document intelligence
description: "ServiceNow\xAE AI-powered tool for extracting data from invoices."
keywords: []
breadcrumbs:
- Finance and Supply Chain
- Accounts Payable Operations
- Accounts Payable Operations reference
- Approval Plan form
- Accounts Payable Operations glossary
- D
---
# Document intelligence
ServiceNow® AI-powered tool for extracting data from invoices.
|
https://www.servicenow.com/docs/en-US/bundle/zurich-source-to-pay-operations/page/reuse/glossary/E/gloss-erp-system-apo.html | https://servicenow-be-prod.servicenow.com/api/bundle/zurich-source-to-pay-operations/page/reuse/glossary/E/gloss-erp-system-apo.html | 2025-08-05 | daily | 0.5 | 268.xml | en-US | zurich-source-to-pay-operations | reuse/glossary/E/gloss-erp-system-apo.html | zurich | Enterprise resource planning systems | Enterprise resource planning (ERP) systems used for managing business processes. | [] | [
"Finance and Supply Chain",
"Accounts Payable Operations",
"Accounts Payable Operations reference",
"Approval Plan form",
"Accounts Payable Operations glossary",
"E"
] | <article class="hascomments" data-page="bundle:zurich-source-to-pay-operations/enus/reuse/glossary/E/gloss-erp-system-apo.html" id="bundle:zurich-source-to-pay-operations/enus/reuse/glossary/E/gloss-erp-system-apo.html"><body id="gloss-erp-system-apo"><main role="main"><article role="article" class="dita" id="gloss-erp-system-apo" aria-labelledby="title_gloss-erp-system-apo">
<h1 class="title glossterm topictitle1" id="title_gloss-erp-system-apo">Enterprise resource planning systems</h1>
<div class="abstract glossdef">Enterprise resource planning (ERP) systems used for managing business processes.</div>
<nav role="navigation"></nav><nav role="navigation" class="tasksNavigation"></nav><nav role="navigation" class="related-links"></nav></article></main></body></article> | {
"attachments": {
"all_attachments": null,
"topic_attachments": []
},
"available_languages": [
"enus"
],
"breadcrumbs": [
{
"title": "Finance and Supply Chain",
"topic_id": "product/source-to-pay-operations/concept/finance-supply-chain-landing.html"
},
{
"title": "Accounts Payable Operations",
"topic_id": "product/accounts-payable-operations/concept/acc-pay-mgmt-landing-page.html"
},
{
"title": "Accounts Payable Operations reference",
"topic_id": "product/accounts-payable-operations/reference/acc-pay-reference.html"
},
{
"title": "Approval Plan form",
"topic_id": "product/accounts-payable-operations/reference/approval-plan-form.html"
},
{
"title": "Accounts Payable Operations glossary",
"topic_id": "product/accounts-payable-operations/concept/apo-glossary.html"
},
{
"title": "E",
"topic_id": "product/accounts-payable-operations/concept/gloss-group-e-apo.html"
}
],
"breadcrumbs_html": "<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations\">Zurich Finance and Supply Chain</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/source-to-pay-operations/concept/finance-supply-chain-landing.html\">Finance and Supply Chain</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/concept/acc-pay-mgmt-landing-page.html\">Accounts Payable Operations</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/reference/acc-pay-reference.html\">Accounts Payable Operations reference</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/reference/approval-plan-form.html\">Approval Plan form</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/concept/apo-glossary.html\">Accounts Payable Operations glossary</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/concept/gloss-group-e-apo.html\">E</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<span class=\"active\">Enterprise resource planning systems</span>",
"bundle_id": "zurich-source-to-pay-operations",
"bundle_key": 2735,
"bundle_landing_page": "product/source-to-pay-operations/concept/finance-supply-chain-landing.html",
"bundle_subtitle": null,
"bundle_title": "Zurich Finance and Supply Chain",
"canonical_link": null,
"dates": {
"Added on": "2025-08-05T13:11:54.216332Z",
"Created on": "2024-11-04T00:00:00Z",
"Initial upload": "2025-07-30T22:25:52.095402Z",
"Updated on": "2025-07-31T00:00:00Z"
},
"dislike_url": "https://servicenow-be-prod.servicenow.com/dislike/55688992",
"dislikes": 0,
"es_archived_content": false,
"is_in_fav": false,
"is_liked": null,
"is_watched": false,
"keywords": [
" zurich zurich"
],
"labels": [
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "zurich",
"navtitle": "Zurich",
"outputclasses": [],
"subjectHeadId": "versions",
"subjectheadNavtitle": "Versions",
"visibility": "show-facet"
},
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "apmgt",
"navtitle": "Accounts Payable Operations",
"outputclasses": [],
"subjectHeadId": "products",
"subjectheadNavtitle": "Products",
"visibility": "show-facet"
}
],
"labels_text": "Versions > Zurich; Products > Finance and Supply Chain > Accounts Payable Operations",
"like_url": "https://servicenow-be-prod.servicenow.com/like/55688992",
"likes": 0,
"metadata": {
"AI Search": null,
"AI Search Assist": null,
"Application Insights": null,
"Capabilities": null,
"Code Signing": null,
"Contextual Search": null,
"DC.contributor": null,
"DC.coverage": null,
"DC.creator": "ServiceNow",
"DC.date.created": "2024-11-04T05:19:08+05:30",
"DC.date.modified": "2025-07-31",
"DC.format": "HTML5",
"DC.identifier": "gloss-erp-system-apo",
"DC.language": null,
"DC.relation": "../../../product/accounts-payable-operations/concept/gloss-group-e-apo.html",
"DC.rights.owner": "(C) Copyright 2025",
"DC.subject": null,
"DC.type": "glossentry",
"Data Discovery": null,
"Data Policy": null,
"Data Privacy": null,
"Discovery": null,
"External Content for AI Search": null,
"Field Administration": null,
"Field Normalization": null,
"Key Management Framework": null,
"Localization Framework": null,
"Now Platform": null,
"PlatSec": null,
"Platform": null,
"Platform Administration": null,
"Platform Performance": null,
"Platform Privacy": null,
"Proactive Triggers": null,
"Process Optimization": null,
"RN doc editing record number": null,
"Search Administration": null,
"Secrets Management": null,
"ServiceNow AI Platform": null,
"State Model": null,
"Subscription Management": null,
"Task Communications Management": null,
"Timeline Visualizations": null,
"User Administration": null,
"User Experience Analytics": null,
"Zing": null,
"ai-now-assist": null,
"app-name": null,
"app_route": null,
"azureapimanagemen": null,
"change-completed": null,
"change-item": null,
"change-request-id": null,
"change-request-reference": null,
"com.glide.embedded_help.category": null,
"component": null,
"copyright": "(C) Copyright 2025",
"crossroads": null,
"data": null,
"description": "Enterprise resource planning (ERP) systems used for managing business processes.",
"dominant_bundle": null,
"erp-canvas-video": null,
"fsm-mobile": null,
"fsm-route": null,
"fsm-sched-opt": null,
"fsm-wrk-order": null,
"genai-round-7": null,
"generator": "DITA-OT",
"glossPartOfSpeech": null,
"glossStatus": null,
"guided setup": null,
"guided tours": null,
"keywords": null,
"min-toc": null,
"mini": null,
"mini-to truec": null,
"mini-toc": null,
"mini_toc": null,
"minitoc": null,
"modification": null,
"now-assist-app-gen-video": null,
"order": null,
"page-type": null,
"page-type ": null,
"prodname": null,
"product": "product_name",
"product_name": null,
"release": null,
"resourceID": null,
"roles": null,
"route_page": null,
"route_params_listId": null,
"route_params_table": null,
"route_params_type": null,
"route_type": null,
"setconfigurationproperties": null,
"topic": null,
"translation-type": "source",
"version": null,
"workflow": "Creator, workflow_name",
"workplace-srvc-delvry-ditamap": null
},
"page_id": "reuse/glossary/E/gloss-erp-system-apo.html",
"page_key": 55688992,
"preprocessed_PDF": "https://downloads.docs.servicenow.com/pdf/enus/servicenow-yokohama-source-to-pay-operations-enus.pdf",
"rating": null,
"read_time_data": {
"char_count": 80,
"img_count": 0,
"read_time": 1,
"video_links": [
""
],
"word_count": 10
},
"related_links": [],
"search_title": null,
"title": "Enterprise resource planning systems",
"topic_cluster": {
"clustered_by": {
"enabled": true,
"primary_key": "versions",
"primary_sort": "top-down",
"type": "subjecthead"
},
"clustered_labels": [
"versions"
],
"clustered_topics": [],
"clustering_title": "Zurich"
},
"topic_html": "<article class=\"hascomments\" data-page=\"bundle:zurich-source-to-pay-operations/enus/reuse/glossary/E/gloss-erp-system-apo.html\" id=\"bundle:zurich-source-to-pay-operations/enus/reuse/glossary/E/gloss-erp-system-apo.html\"><body id=\"gloss-erp-system-apo\"><main role=\"main\"><article role=\"article\" class=\"dita\" id=\"gloss-erp-system-apo\" aria-labelledby=\"title_gloss-erp-system-apo\">\n <h1 class=\"title glossterm topictitle1\" id=\"title_gloss-erp-system-apo\">Enterprise resource planning systems</h1>\n <div class=\"abstract glossdef\">Enterprise resource planning (ERP) systems used for managing business processes.</div>\n \n<nav role=\"navigation\"></nav><nav role=\"navigation\" class=\"tasksNavigation\"></nav><nav role=\"navigation\" class=\"related-links\"></nav></article></main></body></article>",
"topic_language": "enus",
"views": 0,
"your_rating": null
} | # Enterprise resource planning systems
Enterprise resource planning (ERP) systems used for managing business processes.
| ---
title: Enterprise resource planning systems
description: Enterprise resource planning (ERP) systems used for managing business
processes.
keywords: []
breadcrumbs:
- Finance and Supply Chain
- Accounts Payable Operations
- Accounts Payable Operations reference
- Approval Plan form
- Accounts Payable Operations glossary
- E
---
# Enterprise resource planning systems
Enterprise resource planning (ERP) systems used for managing business processes.
|
https://www.servicenow.com/docs/en-US/bundle/zurich-source-to-pay-operations/page/reuse/glossary/E/gloss-exception-manage-apo.html | https://servicenow-be-prod.servicenow.com/api/bundle/zurich-source-to-pay-operations/page/reuse/glossary/E/gloss-exception-manage-apo.html | 2025-08-05 | daily | 0.5 | 268.xml | en-US | zurich-source-to-pay-operations | reuse/glossary/E/gloss-exception-manage-apo.html | zurich | Exception management | Handling and resolving issues that arise during Accounts Payable Operations invoice processing. | [] | [
"Finance and Supply Chain",
"Accounts Payable Operations",
"Accounts Payable Operations reference",
"Approval Plan form",
"Accounts Payable Operations glossary",
"E"
] | <article class="hascomments" data-page="bundle:zurich-source-to-pay-operations/enus/reuse/glossary/E/gloss-exception-manage-apo.html" id="bundle:zurich-source-to-pay-operations/enus/reuse/glossary/E/gloss-exception-manage-apo.html"><body id="gloss-exception-manage-apo"><main role="main"><article role="article" class="dita" id="gloss-exception-manage-apo" aria-labelledby="title_gloss-exception-manage-apo">
<h1 class="title glossterm topictitle1" id="title_gloss-exception-manage-apo">Exception management</h1>
<div class="abstract glossdef">Handling and resolving issues that arise during <span class="ph">Accounts Payable Operations</span> invoice processing.</div>
<nav role="navigation"></nav><nav role="navigation" class="tasksNavigation"></nav><nav role="navigation" class="related-links"></nav></article></main></body></article> | {
"attachments": {
"all_attachments": null,
"topic_attachments": []
},
"available_languages": [
"enus"
],
"breadcrumbs": [
{
"title": "Finance and Supply Chain",
"topic_id": "product/source-to-pay-operations/concept/finance-supply-chain-landing.html"
},
{
"title": "Accounts Payable Operations",
"topic_id": "product/accounts-payable-operations/concept/acc-pay-mgmt-landing-page.html"
},
{
"title": "Accounts Payable Operations reference",
"topic_id": "product/accounts-payable-operations/reference/acc-pay-reference.html"
},
{
"title": "Approval Plan form",
"topic_id": "product/accounts-payable-operations/reference/approval-plan-form.html"
},
{
"title": "Accounts Payable Operations glossary",
"topic_id": "product/accounts-payable-operations/concept/apo-glossary.html"
},
{
"title": "E",
"topic_id": "product/accounts-payable-operations/concept/gloss-group-e-apo.html"
}
],
"breadcrumbs_html": "<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations\">Zurich Finance and Supply Chain</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/source-to-pay-operations/concept/finance-supply-chain-landing.html\">Finance and Supply Chain</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/concept/acc-pay-mgmt-landing-page.html\">Accounts Payable Operations</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/reference/acc-pay-reference.html\">Accounts Payable Operations reference</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/reference/approval-plan-form.html\">Approval Plan form</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/concept/apo-glossary.html\">Accounts Payable Operations glossary</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/concept/gloss-group-e-apo.html\">E</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<span class=\"active\">Exception management</span>",
"bundle_id": "zurich-source-to-pay-operations",
"bundle_key": 2735,
"bundle_landing_page": "product/source-to-pay-operations/concept/finance-supply-chain-landing.html",
"bundle_subtitle": null,
"bundle_title": "Zurich Finance and Supply Chain",
"canonical_link": null,
"dates": {
"Added on": "2025-08-05T13:11:54.216332Z",
"Created on": "2024-11-04T00:00:00Z",
"Initial upload": "2025-07-30T22:25:52.095402Z",
"Updated on": "2025-07-31T00:00:00Z"
},
"dislike_url": "https://servicenow-be-prod.servicenow.com/dislike/55688993",
"dislikes": 0,
"es_archived_content": false,
"is_in_fav": false,
"is_liked": null,
"is_watched": false,
"keywords": [
" zurich zurich"
],
"labels": [
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "zurich",
"navtitle": "Zurich",
"outputclasses": [],
"subjectHeadId": "versions",
"subjectheadNavtitle": "Versions",
"visibility": "show-facet"
},
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "apmgt",
"navtitle": "Accounts Payable Operations",
"outputclasses": [],
"subjectHeadId": "products",
"subjectheadNavtitle": "Products",
"visibility": "show-facet"
}
],
"labels_text": "Versions > Zurich; Products > Finance and Supply Chain > Accounts Payable Operations",
"like_url": "https://servicenow-be-prod.servicenow.com/like/55688993",
"likes": 0,
"metadata": {
"AI Search": null,
"AI Search Assist": null,
"Application Insights": null,
"Capabilities": null,
"Code Signing": null,
"Contextual Search": null,
"DC.contributor": null,
"DC.coverage": null,
"DC.creator": "ServiceNow",
"DC.date.created": "2024-11-04T05:22:56+05:30",
"DC.date.modified": "2025-07-31",
"DC.format": "HTML5",
"DC.identifier": "gloss-exception-manage-apo",
"DC.language": null,
"DC.relation": "../../../product/accounts-payable-operations/concept/gloss-group-e-apo.html",
"DC.rights.owner": "(C) Copyright 2025",
"DC.subject": null,
"DC.type": "glossentry",
"Data Discovery": null,
"Data Policy": null,
"Data Privacy": null,
"Discovery": null,
"External Content for AI Search": null,
"Field Administration": null,
"Field Normalization": null,
"Key Management Framework": null,
"Localization Framework": null,
"Now Platform": null,
"PlatSec": null,
"Platform": null,
"Platform Administration": null,
"Platform Performance": null,
"Platform Privacy": null,
"Proactive Triggers": null,
"Process Optimization": null,
"RN doc editing record number": null,
"Search Administration": null,
"Secrets Management": null,
"ServiceNow AI Platform": null,
"State Model": null,
"Subscription Management": null,
"Task Communications Management": null,
"Timeline Visualizations": null,
"User Administration": null,
"User Experience Analytics": null,
"Zing": null,
"ai-now-assist": null,
"app-name": null,
"app_route": null,
"azureapimanagemen": null,
"change-completed": null,
"change-item": null,
"change-request-id": null,
"change-request-reference": null,
"com.glide.embedded_help.category": null,
"component": null,
"copyright": "(C) Copyright 2025",
"crossroads": null,
"data": null,
"description": "Handling and resolving issues that arise during Accounts Payable Operations invoice processing.",
"dominant_bundle": null,
"erp-canvas-video": null,
"fsm-mobile": null,
"fsm-route": null,
"fsm-sched-opt": null,
"fsm-wrk-order": null,
"genai-round-7": null,
"generator": "DITA-OT",
"glossPartOfSpeech": null,
"glossStatus": null,
"guided setup": null,
"guided tours": null,
"keywords": null,
"min-toc": null,
"mini": null,
"mini-to truec": null,
"mini-toc": null,
"mini_toc": null,
"minitoc": null,
"modification": null,
"now-assist-app-gen-video": null,
"order": null,
"page-type": null,
"page-type ": null,
"prodname": null,
"product": "product_name",
"product_name": null,
"release": null,
"resourceID": null,
"roles": null,
"route_page": null,
"route_params_listId": null,
"route_params_table": null,
"route_params_type": null,
"route_type": null,
"setconfigurationproperties": null,
"topic": null,
"translation-type": "source",
"version": null,
"workflow": "Creator, workflow_name",
"workplace-srvc-delvry-ditamap": null
},
"page_id": "reuse/glossary/E/gloss-exception-manage-apo.html",
"page_key": 55688993,
"preprocessed_PDF": "https://downloads.docs.servicenow.com/pdf/enus/servicenow-yokohama-source-to-pay-operations-enus.pdf",
"rating": null,
"read_time_data": {
"char_count": 95,
"img_count": 0,
"read_time": 1,
"video_links": [
""
],
"word_count": 12
},
"related_links": [],
"search_title": null,
"title": "Exception management",
"topic_cluster": {
"clustered_by": {
"enabled": true,
"primary_key": "versions",
"primary_sort": "top-down",
"type": "subjecthead"
},
"clustered_labels": [
"versions"
],
"clustered_topics": [],
"clustering_title": "Zurich"
},
"topic_html": "<article class=\"hascomments\" data-page=\"bundle:zurich-source-to-pay-operations/enus/reuse/glossary/E/gloss-exception-manage-apo.html\" id=\"bundle:zurich-source-to-pay-operations/enus/reuse/glossary/E/gloss-exception-manage-apo.html\"><body id=\"gloss-exception-manage-apo\"><main role=\"main\"><article role=\"article\" class=\"dita\" id=\"gloss-exception-manage-apo\" aria-labelledby=\"title_gloss-exception-manage-apo\">\n <h1 class=\"title glossterm topictitle1\" id=\"title_gloss-exception-manage-apo\">Exception management</h1>\n <div class=\"abstract glossdef\">Handling and resolving issues that arise during <span class=\"ph\">Accounts Payable Operations</span> invoice processing.</div>\n \n<nav role=\"navigation\"></nav><nav role=\"navigation\" class=\"tasksNavigation\"></nav><nav role=\"navigation\" class=\"related-links\"></nav></article></main></body></article>",
"topic_language": "enus",
"views": 0,
"your_rating": null
} | # Exception management
Handling and resolving issues that arise during Accounts Payable Operations invoice processing.
| ---
title: Exception management
description: Handling and resolving issues that arise during Accounts Payable Operations
invoice processing.
keywords: []
breadcrumbs:
- Finance and Supply Chain
- Accounts Payable Operations
- Accounts Payable Operations reference
- Approval Plan form
- Accounts Payable Operations glossary
- E
---
# Exception management
Handling and resolving issues that arise during Accounts Payable Operations invoice processing.
|
https://www.servicenow.com/docs/en-US/bundle/zurich-source-to-pay-operations/page/reuse/glossary/I/gloss-invoice-approval-apo.html | https://servicenow-be-prod.servicenow.com/api/bundle/zurich-source-to-pay-operations/page/reuse/glossary/I/gloss-invoice-approval-apo.html | 2025-08-05 | daily | 0.5 | 268.xml | en-US | zurich-source-to-pay-operations | reuse/glossary/I/gloss-invoice-approval-apo.html | zurich | Invoice approval | The process of verifying and authorizing an invoice for payment. | [] | [
"Finance and Supply Chain",
"Accounts Payable Operations",
"Accounts Payable Operations reference",
"Approval Plan form",
"Accounts Payable Operations glossary",
"I"
] | <article class="hascomments" data-page="bundle:zurich-source-to-pay-operations/enus/reuse/glossary/I/gloss-invoice-approval-apo.html" id="bundle:zurich-source-to-pay-operations/enus/reuse/glossary/I/gloss-invoice-approval-apo.html"><body id="gloss-invoice-approval-apo"><main role="main"><article role="article" class="dita" id="gloss-invoice-approval-apo" aria-labelledby="title_gloss-invoice-approval-apo">
<h1 class="title glossterm topictitle1" id="title_gloss-invoice-approval-apo">Invoice approval</h1>
<div class="abstract glossdef">The process of verifying and authorizing an invoice for payment.</div>
<nav role="navigation"></nav><nav role="navigation" class="tasksNavigation"></nav><nav role="navigation" class="related-links"></nav></article></main></body></article> | {
"attachments": {
"all_attachments": null,
"topic_attachments": []
},
"available_languages": [
"enus"
],
"breadcrumbs": [
{
"title": "Finance and Supply Chain",
"topic_id": "product/source-to-pay-operations/concept/finance-supply-chain-landing.html"
},
{
"title": "Accounts Payable Operations",
"topic_id": "product/accounts-payable-operations/concept/acc-pay-mgmt-landing-page.html"
},
{
"title": "Accounts Payable Operations reference",
"topic_id": "product/accounts-payable-operations/reference/acc-pay-reference.html"
},
{
"title": "Approval Plan form",
"topic_id": "product/accounts-payable-operations/reference/approval-plan-form.html"
},
{
"title": "Accounts Payable Operations glossary",
"topic_id": "product/accounts-payable-operations/concept/apo-glossary.html"
},
{
"title": "I",
"topic_id": "product/accounts-payable-operations/concept/gloss-group-i-apo.html"
}
],
"breadcrumbs_html": "<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations\">Zurich Finance and Supply Chain</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/source-to-pay-operations/concept/finance-supply-chain-landing.html\">Finance and Supply Chain</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/concept/acc-pay-mgmt-landing-page.html\">Accounts Payable Operations</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/reference/acc-pay-reference.html\">Accounts Payable Operations reference</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/reference/approval-plan-form.html\">Approval Plan form</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/concept/apo-glossary.html\">Accounts Payable Operations glossary</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/concept/gloss-group-i-apo.html\">I</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<span class=\"active\">Invoice approval</span>",
"bundle_id": "zurich-source-to-pay-operations",
"bundle_key": 2735,
"bundle_landing_page": "product/source-to-pay-operations/concept/finance-supply-chain-landing.html",
"bundle_subtitle": null,
"bundle_title": "Zurich Finance and Supply Chain",
"canonical_link": null,
"dates": {
"Added on": "2025-08-05T13:11:54.216332Z",
"Created on": "2024-11-04T00:00:00Z",
"Initial upload": "2025-07-30T22:25:52.095402Z",
"Updated on": "2025-07-31T00:00:00Z"
},
"dislike_url": "https://servicenow-be-prod.servicenow.com/dislike/55688994",
"dislikes": 0,
"es_archived_content": false,
"is_in_fav": false,
"is_liked": null,
"is_watched": false,
"keywords": [
" zurich zurich"
],
"labels": [
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "zurich",
"navtitle": "Zurich",
"outputclasses": [],
"subjectHeadId": "versions",
"subjectheadNavtitle": "Versions",
"visibility": "show-facet"
},
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "apmgt",
"navtitle": "Accounts Payable Operations",
"outputclasses": [],
"subjectHeadId": "products",
"subjectheadNavtitle": "Products",
"visibility": "show-facet"
}
],
"labels_text": "Versions > Zurich; Products > Finance and Supply Chain > Accounts Payable Operations",
"like_url": "https://servicenow-be-prod.servicenow.com/like/55688994",
"likes": 0,
"metadata": {
"AI Search": null,
"AI Search Assist": null,
"Application Insights": null,
"Capabilities": null,
"Code Signing": null,
"Contextual Search": null,
"DC.contributor": null,
"DC.coverage": null,
"DC.creator": "ServiceNow",
"DC.date.created": "2024-11-04T05:31:42+05:30",
"DC.date.modified": "2025-07-31",
"DC.format": "HTML5",
"DC.identifier": "gloss-invoice-approval-apo",
"DC.language": null,
"DC.relation": "../../../product/accounts-payable-operations/concept/gloss-group-i-apo.html",
"DC.rights.owner": "(C) Copyright 2025",
"DC.subject": null,
"DC.type": "glossentry",
"Data Discovery": null,
"Data Policy": null,
"Data Privacy": null,
"Discovery": null,
"External Content for AI Search": null,
"Field Administration": null,
"Field Normalization": null,
"Key Management Framework": null,
"Localization Framework": null,
"Now Platform": null,
"PlatSec": null,
"Platform": null,
"Platform Administration": null,
"Platform Performance": null,
"Platform Privacy": null,
"Proactive Triggers": null,
"Process Optimization": null,
"RN doc editing record number": null,
"Search Administration": null,
"Secrets Management": null,
"ServiceNow AI Platform": null,
"State Model": null,
"Subscription Management": null,
"Task Communications Management": null,
"Timeline Visualizations": null,
"User Administration": null,
"User Experience Analytics": null,
"Zing": null,
"ai-now-assist": null,
"app-name": null,
"app_route": null,
"azureapimanagemen": null,
"change-completed": null,
"change-item": null,
"change-request-id": null,
"change-request-reference": null,
"com.glide.embedded_help.category": null,
"component": null,
"copyright": "(C) Copyright 2025",
"crossroads": null,
"data": null,
"description": "The process of verifying and authorizing an invoice for payment.",
"dominant_bundle": null,
"erp-canvas-video": null,
"fsm-mobile": null,
"fsm-route": null,
"fsm-sched-opt": null,
"fsm-wrk-order": null,
"genai-round-7": null,
"generator": "DITA-OT",
"glossPartOfSpeech": null,
"glossStatus": null,
"guided setup": null,
"guided tours": null,
"keywords": null,
"min-toc": null,
"mini": null,
"mini-to truec": null,
"mini-toc": null,
"mini_toc": null,
"minitoc": null,
"modification": null,
"now-assist-app-gen-video": null,
"order": null,
"page-type": null,
"page-type ": null,
"prodname": null,
"product": "product_name",
"product_name": null,
"release": null,
"resourceID": null,
"roles": null,
"route_page": null,
"route_params_listId": null,
"route_params_table": null,
"route_params_type": null,
"route_type": null,
"setconfigurationproperties": null,
"topic": null,
"translation-type": "source",
"version": null,
"workflow": "Creator, workflow_name",
"workplace-srvc-delvry-ditamap": null
},
"page_id": "reuse/glossary/I/gloss-invoice-approval-apo.html",
"page_key": 55688994,
"preprocessed_PDF": "https://downloads.docs.servicenow.com/pdf/enus/servicenow-yokohama-source-to-pay-operations-enus.pdf",
"rating": null,
"read_time_data": {
"char_count": 64,
"img_count": 0,
"read_time": 1,
"video_links": [
""
],
"word_count": 10
},
"related_links": [],
"search_title": null,
"title": "Invoice approval",
"topic_cluster": {
"clustered_by": {
"enabled": true,
"primary_key": "versions",
"primary_sort": "top-down",
"type": "subjecthead"
},
"clustered_labels": [
"versions"
],
"clustered_topics": [],
"clustering_title": "Zurich"
},
"topic_html": "<article class=\"hascomments\" data-page=\"bundle:zurich-source-to-pay-operations/enus/reuse/glossary/I/gloss-invoice-approval-apo.html\" id=\"bundle:zurich-source-to-pay-operations/enus/reuse/glossary/I/gloss-invoice-approval-apo.html\"><body id=\"gloss-invoice-approval-apo\"><main role=\"main\"><article role=\"article\" class=\"dita\" id=\"gloss-invoice-approval-apo\" aria-labelledby=\"title_gloss-invoice-approval-apo\">\n <h1 class=\"title glossterm topictitle1\" id=\"title_gloss-invoice-approval-apo\">Invoice approval</h1>\n <div class=\"abstract glossdef\">The process of verifying and authorizing an invoice for payment.</div>\n \n<nav role=\"navigation\"></nav><nav role=\"navigation\" class=\"tasksNavigation\"></nav><nav role=\"navigation\" class=\"related-links\"></nav></article></main></body></article>",
"topic_language": "enus",
"views": 0,
"your_rating": null
} | # Invoice approval
The process of verifying and authorizing an invoice for payment.
| ---
title: Invoice approval
description: The process of verifying and authorizing an invoice for payment.
keywords: []
breadcrumbs:
- Finance and Supply Chain
- Accounts Payable Operations
- Accounts Payable Operations reference
- Approval Plan form
- Accounts Payable Operations glossary
- I
---
# Invoice approval
The process of verifying and authorizing an invoice for payment.
|
https://www.servicenow.com/docs/en-US/bundle/zurich-source-to-pay-operations/page/reuse/glossary/I/gloss-invoice-exception-apo.html | https://servicenow-be-prod.servicenow.com/api/bundle/zurich-source-to-pay-operations/page/reuse/glossary/I/gloss-invoice-exception-apo.html | 2025-08-05 | daily | 0.5 | 268.xml | en-US | zurich-source-to-pay-operations | reuse/glossary/I/gloss-invoice-exception-apo.html | zurich | Invoice exception | Issues identified during invoice processing that require resolution. | [] | [
"Finance and Supply Chain",
"Accounts Payable Operations",
"Accounts Payable Operations reference",
"Approval Plan form",
"Accounts Payable Operations glossary",
"I"
] | <article class="hascomments" data-page="bundle:zurich-source-to-pay-operations/enus/reuse/glossary/I/gloss-invoice-exception-apo.html" id="bundle:zurich-source-to-pay-operations/enus/reuse/glossary/I/gloss-invoice-exception-apo.html"><body id="gloss-invoice-exception-apo"><main role="main"><article role="article" class="dita" id="gloss-invoice-exception-apo" aria-labelledby="title_gloss-invoice-exception-apo">
<h1 class="title glossterm topictitle1" id="title_gloss-invoice-exception-apo">Invoice exception</h1>
<div class="abstract glossdef">Issues identified during invoice processing that require resolution.</div>
<nav role="navigation"></nav><nav role="navigation" class="tasksNavigation"></nav><nav role="navigation" class="related-links"></nav></article></main></body></article> | {
"attachments": {
"all_attachments": null,
"topic_attachments": []
},
"available_languages": [
"enus"
],
"breadcrumbs": [
{
"title": "Finance and Supply Chain",
"topic_id": "product/source-to-pay-operations/concept/finance-supply-chain-landing.html"
},
{
"title": "Accounts Payable Operations",
"topic_id": "product/accounts-payable-operations/concept/acc-pay-mgmt-landing-page.html"
},
{
"title": "Accounts Payable Operations reference",
"topic_id": "product/accounts-payable-operations/reference/acc-pay-reference.html"
},
{
"title": "Approval Plan form",
"topic_id": "product/accounts-payable-operations/reference/approval-plan-form.html"
},
{
"title": "Accounts Payable Operations glossary",
"topic_id": "product/accounts-payable-operations/concept/apo-glossary.html"
},
{
"title": "I",
"topic_id": "product/accounts-payable-operations/concept/gloss-group-i-apo.html"
}
],
"breadcrumbs_html": "<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations\">Zurich Finance and Supply Chain</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/source-to-pay-operations/concept/finance-supply-chain-landing.html\">Finance and Supply Chain</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/concept/acc-pay-mgmt-landing-page.html\">Accounts Payable Operations</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/reference/acc-pay-reference.html\">Accounts Payable Operations reference</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/reference/approval-plan-form.html\">Approval Plan form</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/concept/apo-glossary.html\">Accounts Payable Operations glossary</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/concept/gloss-group-i-apo.html\">I</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<span class=\"active\">Invoice exception</span>",
"bundle_id": "zurich-source-to-pay-operations",
"bundle_key": 2735,
"bundle_landing_page": "product/source-to-pay-operations/concept/finance-supply-chain-landing.html",
"bundle_subtitle": null,
"bundle_title": "Zurich Finance and Supply Chain",
"canonical_link": null,
"dates": {
"Added on": "2025-08-05T13:11:54.216332Z",
"Created on": "2024-11-04T00:00:00Z",
"Initial upload": "2025-07-30T22:25:52.095402Z",
"Updated on": "2025-07-31T00:00:00Z"
},
"dislike_url": "https://servicenow-be-prod.servicenow.com/dislike/55688995",
"dislikes": 0,
"es_archived_content": false,
"is_in_fav": false,
"is_liked": null,
"is_watched": false,
"keywords": [
" zurich zurich"
],
"labels": [
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "zurich",
"navtitle": "Zurich",
"outputclasses": [],
"subjectHeadId": "versions",
"subjectheadNavtitle": "Versions",
"visibility": "show-facet"
},
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "apmgt",
"navtitle": "Accounts Payable Operations",
"outputclasses": [],
"subjectHeadId": "products",
"subjectheadNavtitle": "Products",
"visibility": "show-facet"
}
],
"labels_text": "Versions > Zurich; Products > Finance and Supply Chain > Accounts Payable Operations",
"like_url": "https://servicenow-be-prod.servicenow.com/like/55688995",
"likes": 0,
"metadata": {
"AI Search": null,
"AI Search Assist": null,
"Application Insights": null,
"Capabilities": null,
"Code Signing": null,
"Contextual Search": null,
"DC.contributor": null,
"DC.coverage": null,
"DC.creator": "ServiceNow",
"DC.date.created": "2024-11-04T05:21:31+05:30",
"DC.date.modified": "2025-07-31",
"DC.format": "HTML5",
"DC.identifier": "gloss-invoice-exception-apo",
"DC.language": null,
"DC.relation": "../../../product/accounts-payable-operations/concept/gloss-group-i-apo.html",
"DC.rights.owner": "(C) Copyright 2025",
"DC.subject": null,
"DC.type": "glossentry",
"Data Discovery": null,
"Data Policy": null,
"Data Privacy": null,
"Discovery": null,
"External Content for AI Search": null,
"Field Administration": null,
"Field Normalization": null,
"Key Management Framework": null,
"Localization Framework": null,
"Now Platform": null,
"PlatSec": null,
"Platform": null,
"Platform Administration": null,
"Platform Performance": null,
"Platform Privacy": null,
"Proactive Triggers": null,
"Process Optimization": null,
"RN doc editing record number": null,
"Search Administration": null,
"Secrets Management": null,
"ServiceNow AI Platform": null,
"State Model": null,
"Subscription Management": null,
"Task Communications Management": null,
"Timeline Visualizations": null,
"User Administration": null,
"User Experience Analytics": null,
"Zing": null,
"ai-now-assist": null,
"app-name": null,
"app_route": null,
"azureapimanagemen": null,
"change-completed": null,
"change-item": null,
"change-request-id": null,
"change-request-reference": null,
"com.glide.embedded_help.category": null,
"component": null,
"copyright": "(C) Copyright 2025",
"crossroads": null,
"data": null,
"description": "Issues identified during invoice processing that require resolution.",
"dominant_bundle": null,
"erp-canvas-video": null,
"fsm-mobile": null,
"fsm-route": null,
"fsm-sched-opt": null,
"fsm-wrk-order": null,
"genai-round-7": null,
"generator": "DITA-OT",
"glossPartOfSpeech": null,
"glossStatus": null,
"guided setup": null,
"guided tours": null,
"keywords": null,
"min-toc": null,
"mini": null,
"mini-to truec": null,
"mini-toc": null,
"mini_toc": null,
"minitoc": null,
"modification": null,
"now-assist-app-gen-video": null,
"order": null,
"page-type": null,
"page-type ": null,
"prodname": null,
"product": "product_name",
"product_name": null,
"release": null,
"resourceID": null,
"roles": null,
"route_page": null,
"route_params_listId": null,
"route_params_table": null,
"route_params_type": null,
"route_type": null,
"setconfigurationproperties": null,
"topic": null,
"translation-type": "source",
"version": null,
"workflow": "Creator, workflow_name",
"workplace-srvc-delvry-ditamap": null
},
"page_id": "reuse/glossary/I/gloss-invoice-exception-apo.html",
"page_key": 55688995,
"preprocessed_PDF": "https://downloads.docs.servicenow.com/pdf/enus/servicenow-yokohama-source-to-pay-operations-enus.pdf",
"rating": null,
"read_time_data": {
"char_count": 68,
"img_count": 0,
"read_time": 1,
"video_links": [
""
],
"word_count": 8
},
"related_links": [],
"search_title": null,
"title": "Invoice exception",
"topic_cluster": {
"clustered_by": {
"enabled": true,
"primary_key": "versions",
"primary_sort": "top-down",
"type": "subjecthead"
},
"clustered_labels": [
"versions"
],
"clustered_topics": [],
"clustering_title": "Zurich"
},
"topic_html": "<article class=\"hascomments\" data-page=\"bundle:zurich-source-to-pay-operations/enus/reuse/glossary/I/gloss-invoice-exception-apo.html\" id=\"bundle:zurich-source-to-pay-operations/enus/reuse/glossary/I/gloss-invoice-exception-apo.html\"><body id=\"gloss-invoice-exception-apo\"><main role=\"main\"><article role=\"article\" class=\"dita\" id=\"gloss-invoice-exception-apo\" aria-labelledby=\"title_gloss-invoice-exception-apo\">\n <h1 class=\"title glossterm topictitle1\" id=\"title_gloss-invoice-exception-apo\">Invoice exception</h1>\n <div class=\"abstract glossdef\">Issues identified during invoice processing that require resolution.</div>\n \n<nav role=\"navigation\"></nav><nav role=\"navigation\" class=\"tasksNavigation\"></nav><nav role=\"navigation\" class=\"related-links\"></nav></article></main></body></article>",
"topic_language": "enus",
"views": 0,
"your_rating": null
} | # Invoice exception
Issues identified during invoice processing that require resolution.
| ---
title: Invoice exception
description: Issues identified during invoice processing that require resolution.
keywords: []
breadcrumbs:
- Finance and Supply Chain
- Accounts Payable Operations
- Accounts Payable Operations reference
- Approval Plan form
- Accounts Payable Operations glossary
- I
---
# Invoice exception
Issues identified during invoice processing that require resolution.
|
https://www.servicenow.com/docs/en-US/bundle/zurich-source-to-pay-operations/page/reuse/glossary/I/gloss-invoice-ingestion.html | https://servicenow-be-prod.servicenow.com/api/bundle/zurich-source-to-pay-operations/page/reuse/glossary/I/gloss-invoice-ingestion.html | 2025-08-05 | daily | 0.5 | 268.xml | en-US | zurich-source-to-pay-operations | reuse/glossary/I/gloss-invoice-ingestion.html | zurich | Invoice ingestion | The process of receiving and entering invoices into the system. | [] | [
"Finance and Supply Chain",
"Accounts Payable Operations",
"Accounts Payable Operations reference",
"Approval Plan form",
"Accounts Payable Operations glossary",
"I"
] | <article class="hascomments" data-page="bundle:zurich-source-to-pay-operations/enus/reuse/glossary/I/gloss-invoice-ingestion.html" id="bundle:zurich-source-to-pay-operations/enus/reuse/glossary/I/gloss-invoice-ingestion.html"><body id="gloss-invoice-ingestion"><main role="main"><article role="article" class="dita" id="gloss-invoice-ingestion" aria-labelledby="title_gloss-invoice-ingestion">
<h1 class="title glossterm topictitle1" id="title_gloss-invoice-ingestion">Invoice ingestion</h1>
<div class="abstract glossdef">The process of receiving and entering invoices into the system.</div>
<nav role="navigation"></nav><nav role="navigation" class="tasksNavigation"></nav><nav role="navigation" class="related-links"></nav></article></main></body></article> | {
"attachments": {
"all_attachments": null,
"topic_attachments": []
},
"available_languages": [
"enus"
],
"breadcrumbs": [
{
"title": "Finance and Supply Chain",
"topic_id": "product/source-to-pay-operations/concept/finance-supply-chain-landing.html"
},
{
"title": "Accounts Payable Operations",
"topic_id": "product/accounts-payable-operations/concept/acc-pay-mgmt-landing-page.html"
},
{
"title": "Accounts Payable Operations reference",
"topic_id": "product/accounts-payable-operations/reference/acc-pay-reference.html"
},
{
"title": "Approval Plan form",
"topic_id": "product/accounts-payable-operations/reference/approval-plan-form.html"
},
{
"title": "Accounts Payable Operations glossary",
"topic_id": "product/accounts-payable-operations/concept/apo-glossary.html"
},
{
"title": "I",
"topic_id": "product/accounts-payable-operations/concept/gloss-group-i-apo.html"
}
],
"breadcrumbs_html": "<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations\">Zurich Finance and Supply Chain</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/source-to-pay-operations/concept/finance-supply-chain-landing.html\">Finance and Supply Chain</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/concept/acc-pay-mgmt-landing-page.html\">Accounts Payable Operations</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/reference/acc-pay-reference.html\">Accounts Payable Operations reference</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/reference/approval-plan-form.html\">Approval Plan form</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/concept/apo-glossary.html\">Accounts Payable Operations glossary</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/concept/gloss-group-i-apo.html\">I</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<span class=\"active\">Invoice ingestion</span>",
"bundle_id": "zurich-source-to-pay-operations",
"bundle_key": 2735,
"bundle_landing_page": "product/source-to-pay-operations/concept/finance-supply-chain-landing.html",
"bundle_subtitle": null,
"bundle_title": "Zurich Finance and Supply Chain",
"canonical_link": null,
"dates": {
"Added on": "2025-08-05T13:11:54.216332Z",
"Created on": "2024-11-04T00:00:00Z",
"Initial upload": "2025-07-30T22:25:52.095402Z",
"Updated on": "2025-07-31T00:00:00Z"
},
"dislike_url": "https://servicenow-be-prod.servicenow.com/dislike/55688996",
"dislikes": 0,
"es_archived_content": false,
"is_in_fav": false,
"is_liked": null,
"is_watched": false,
"keywords": [
" zurich zurich"
],
"labels": [
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "zurich",
"navtitle": "Zurich",
"outputclasses": [],
"subjectHeadId": "versions",
"subjectheadNavtitle": "Versions",
"visibility": "show-facet"
},
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "apmgt",
"navtitle": "Accounts Payable Operations",
"outputclasses": [],
"subjectHeadId": "products",
"subjectheadNavtitle": "Products",
"visibility": "show-facet"
}
],
"labels_text": "Versions > Zurich; Products > Finance and Supply Chain > Accounts Payable Operations",
"like_url": "https://servicenow-be-prod.servicenow.com/like/55688996",
"likes": 0,
"metadata": {
"AI Search": null,
"AI Search Assist": null,
"Application Insights": null,
"Capabilities": null,
"Code Signing": null,
"Contextual Search": null,
"DC.contributor": null,
"DC.coverage": null,
"DC.creator": "ServiceNow",
"DC.date.created": "2024-11-04T05:32:38+05:30",
"DC.date.modified": "2025-07-31",
"DC.format": "HTML5",
"DC.identifier": "gloss-invoice-ingestion",
"DC.language": null,
"DC.relation": "../../../product/accounts-payable-operations/concept/gloss-group-i-apo.html",
"DC.rights.owner": "(C) Copyright 2025",
"DC.subject": null,
"DC.type": "glossentry",
"Data Discovery": null,
"Data Policy": null,
"Data Privacy": null,
"Discovery": null,
"External Content for AI Search": null,
"Field Administration": null,
"Field Normalization": null,
"Key Management Framework": null,
"Localization Framework": null,
"Now Platform": null,
"PlatSec": null,
"Platform": null,
"Platform Administration": null,
"Platform Performance": null,
"Platform Privacy": null,
"Proactive Triggers": null,
"Process Optimization": null,
"RN doc editing record number": null,
"Search Administration": null,
"Secrets Management": null,
"ServiceNow AI Platform": null,
"State Model": null,
"Subscription Management": null,
"Task Communications Management": null,
"Timeline Visualizations": null,
"User Administration": null,
"User Experience Analytics": null,
"Zing": null,
"ai-now-assist": null,
"app-name": null,
"app_route": null,
"azureapimanagemen": null,
"change-completed": null,
"change-item": null,
"change-request-id": null,
"change-request-reference": null,
"com.glide.embedded_help.category": null,
"component": null,
"copyright": "(C) Copyright 2025",
"crossroads": null,
"data": null,
"description": "The process of receiving and entering invoices into the system.",
"dominant_bundle": null,
"erp-canvas-video": null,
"fsm-mobile": null,
"fsm-route": null,
"fsm-sched-opt": null,
"fsm-wrk-order": null,
"genai-round-7": null,
"generator": "DITA-OT",
"glossPartOfSpeech": null,
"glossStatus": null,
"guided setup": null,
"guided tours": null,
"keywords": null,
"min-toc": null,
"mini": null,
"mini-to truec": null,
"mini-toc": null,
"mini_toc": null,
"minitoc": null,
"modification": null,
"now-assist-app-gen-video": null,
"order": null,
"page-type": null,
"page-type ": null,
"prodname": null,
"product": "product_name",
"product_name": null,
"release": null,
"resourceID": null,
"roles": null,
"route_page": null,
"route_params_listId": null,
"route_params_table": null,
"route_params_type": null,
"route_type": null,
"setconfigurationproperties": null,
"topic": null,
"translation-type": "source",
"version": null,
"workflow": "Creator, workflow_name",
"workplace-srvc-delvry-ditamap": null
},
"page_id": "reuse/glossary/I/gloss-invoice-ingestion.html",
"page_key": 55688996,
"preprocessed_PDF": "https://downloads.docs.servicenow.com/pdf/enus/servicenow-yokohama-source-to-pay-operations-enus.pdf",
"rating": null,
"read_time_data": {
"char_count": 63,
"img_count": 0,
"read_time": 1,
"video_links": [
""
],
"word_count": 10
},
"related_links": [],
"search_title": null,
"title": "Invoice ingestion",
"topic_cluster": {
"clustered_by": {
"enabled": true,
"primary_key": "versions",
"primary_sort": "top-down",
"type": "subjecthead"
},
"clustered_labels": [
"versions"
],
"clustered_topics": [],
"clustering_title": "Zurich"
},
"topic_html": "<article class=\"hascomments\" data-page=\"bundle:zurich-source-to-pay-operations/enus/reuse/glossary/I/gloss-invoice-ingestion.html\" id=\"bundle:zurich-source-to-pay-operations/enus/reuse/glossary/I/gloss-invoice-ingestion.html\"><body id=\"gloss-invoice-ingestion\"><main role=\"main\"><article role=\"article\" class=\"dita\" id=\"gloss-invoice-ingestion\" aria-labelledby=\"title_gloss-invoice-ingestion\">\n <h1 class=\"title glossterm topictitle1\" id=\"title_gloss-invoice-ingestion\">Invoice ingestion</h1>\n <div class=\"abstract glossdef\">The process of receiving and entering invoices into the system.</div>\n \n<nav role=\"navigation\"></nav><nav role=\"navigation\" class=\"tasksNavigation\"></nav><nav role=\"navigation\" class=\"related-links\"></nav></article></main></body></article>",
"topic_language": "enus",
"views": 0,
"your_rating": null
} | # Invoice ingestion
The process of receiving and entering invoices into the system.
| ---
title: Invoice ingestion
description: The process of receiving and entering invoices into the system.
keywords: []
breadcrumbs:
- Finance and Supply Chain
- Accounts Payable Operations
- Accounts Payable Operations reference
- Approval Plan form
- Accounts Payable Operations glossary
- I
---
# Invoice ingestion
The process of receiving and entering invoices into the system.
|
https://www.servicenow.com/docs/en-US/bundle/zurich-source-to-pay-operations/page/reuse/glossary/I/gloss-invoice-process-apo.html | https://servicenow-be-prod.servicenow.com/api/bundle/zurich-source-to-pay-operations/page/reuse/glossary/I/gloss-invoice-process-apo.html | 2025-08-05 | daily | 0.5 | 268.xml | en-US | zurich-source-to-pay-operations | reuse/glossary/I/gloss-invoice-process-apo.html | zurich | Invoice processing | The end-to-end handling of invoices from receipt to payment. | [] | [
"Finance and Supply Chain",
"Accounts Payable Operations",
"Accounts Payable Operations reference",
"Approval Plan form",
"Accounts Payable Operations glossary",
"I"
] | <article class="hascomments" data-page="bundle:zurich-source-to-pay-operations/enus/reuse/glossary/I/gloss-invoice-process-apo.html" id="bundle:zurich-source-to-pay-operations/enus/reuse/glossary/I/gloss-invoice-process-apo.html"><body id="gloss-invoice-process-apo"><main role="main"><article role="article" class="dita" id="gloss-invoice-process-apo" aria-labelledby="title_gloss-invoice-process-apo">
<h1 class="title glossterm topictitle1" id="title_gloss-invoice-process-apo">Invoice processing</h1>
<div class="abstract glossdef">The end-to-end handling of invoices from receipt to payment.</div>
<nav role="navigation"></nav><nav role="navigation" class="tasksNavigation"></nav><nav role="navigation" class="related-links"></nav></article></main></body></article> | {
"attachments": {
"all_attachments": null,
"topic_attachments": []
},
"available_languages": [
"enus"
],
"breadcrumbs": [
{
"title": "Finance and Supply Chain",
"topic_id": "product/source-to-pay-operations/concept/finance-supply-chain-landing.html"
},
{
"title": "Accounts Payable Operations",
"topic_id": "product/accounts-payable-operations/concept/acc-pay-mgmt-landing-page.html"
},
{
"title": "Accounts Payable Operations reference",
"topic_id": "product/accounts-payable-operations/reference/acc-pay-reference.html"
},
{
"title": "Approval Plan form",
"topic_id": "product/accounts-payable-operations/reference/approval-plan-form.html"
},
{
"title": "Accounts Payable Operations glossary",
"topic_id": "product/accounts-payable-operations/concept/apo-glossary.html"
},
{
"title": "I",
"topic_id": "product/accounts-payable-operations/concept/gloss-group-i-apo.html"
}
],
"breadcrumbs_html": "<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations\">Zurich Finance and Supply Chain</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/source-to-pay-operations/concept/finance-supply-chain-landing.html\">Finance and Supply Chain</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/concept/acc-pay-mgmt-landing-page.html\">Accounts Payable Operations</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/reference/acc-pay-reference.html\">Accounts Payable Operations reference</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/reference/approval-plan-form.html\">Approval Plan form</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/concept/apo-glossary.html\">Accounts Payable Operations glossary</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/concept/gloss-group-i-apo.html\">I</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<span class=\"active\">Invoice processing</span>",
"bundle_id": "zurich-source-to-pay-operations",
"bundle_key": 2735,
"bundle_landing_page": "product/source-to-pay-operations/concept/finance-supply-chain-landing.html",
"bundle_subtitle": null,
"bundle_title": "Zurich Finance and Supply Chain",
"canonical_link": null,
"dates": {
"Added on": "2025-08-05T13:11:54.216332Z",
"Created on": "2024-11-04T00:00:00Z",
"Initial upload": "2025-07-30T22:25:52.095402Z",
"Updated on": "2025-07-31T00:00:00Z"
},
"dislike_url": "https://servicenow-be-prod.servicenow.com/dislike/55688997",
"dislikes": 0,
"es_archived_content": false,
"is_in_fav": false,
"is_liked": null,
"is_watched": false,
"keywords": [
" zurich zurich"
],
"labels": [
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "zurich",
"navtitle": "Zurich",
"outputclasses": [],
"subjectHeadId": "versions",
"subjectheadNavtitle": "Versions",
"visibility": "show-facet"
},
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "apmgt",
"navtitle": "Accounts Payable Operations",
"outputclasses": [],
"subjectHeadId": "products",
"subjectheadNavtitle": "Products",
"visibility": "show-facet"
}
],
"labels_text": "Versions > Zurich; Products > Finance and Supply Chain > Accounts Payable Operations",
"like_url": "https://servicenow-be-prod.servicenow.com/like/55688997",
"likes": 0,
"metadata": {
"AI Search": null,
"AI Search Assist": null,
"Application Insights": null,
"Capabilities": null,
"Code Signing": null,
"Contextual Search": null,
"DC.contributor": null,
"DC.coverage": null,
"DC.creator": "ServiceNow",
"DC.date.created": "2024-11-04T04:59:39+05:30",
"DC.date.modified": "2025-07-31",
"DC.format": "HTML5",
"DC.identifier": "gloss-invoice-process-apo",
"DC.language": null,
"DC.relation": "../../../product/accounts-payable-operations/concept/gloss-group-i-apo.html",
"DC.rights.owner": "(C) Copyright 2025",
"DC.subject": null,
"DC.type": "glossentry",
"Data Discovery": null,
"Data Policy": null,
"Data Privacy": null,
"Discovery": null,
"External Content for AI Search": null,
"Field Administration": null,
"Field Normalization": null,
"Key Management Framework": null,
"Localization Framework": null,
"Now Platform": null,
"PlatSec": null,
"Platform": null,
"Platform Administration": null,
"Platform Performance": null,
"Platform Privacy": null,
"Proactive Triggers": null,
"Process Optimization": null,
"RN doc editing record number": null,
"Search Administration": null,
"Secrets Management": null,
"ServiceNow AI Platform": null,
"State Model": null,
"Subscription Management": null,
"Task Communications Management": null,
"Timeline Visualizations": null,
"User Administration": null,
"User Experience Analytics": null,
"Zing": null,
"ai-now-assist": null,
"app-name": null,
"app_route": null,
"azureapimanagemen": null,
"change-completed": null,
"change-item": null,
"change-request-id": null,
"change-request-reference": null,
"com.glide.embedded_help.category": null,
"component": null,
"copyright": "(C) Copyright 2025",
"crossroads": null,
"data": null,
"description": "The end-to-end handling of invoices from receipt to payment.",
"dominant_bundle": null,
"erp-canvas-video": null,
"fsm-mobile": null,
"fsm-route": null,
"fsm-sched-opt": null,
"fsm-wrk-order": null,
"genai-round-7": null,
"generator": "DITA-OT",
"glossPartOfSpeech": null,
"glossStatus": null,
"guided setup": null,
"guided tours": null,
"keywords": null,
"min-toc": null,
"mini": null,
"mini-to truec": null,
"mini-toc": null,
"mini_toc": null,
"minitoc": null,
"modification": null,
"now-assist-app-gen-video": null,
"order": null,
"page-type": null,
"page-type ": null,
"prodname": null,
"product": "product_name",
"product_name": null,
"release": null,
"resourceID": null,
"roles": null,
"route_page": null,
"route_params_listId": null,
"route_params_table": null,
"route_params_type": null,
"route_type": null,
"setconfigurationproperties": null,
"topic": null,
"translation-type": "source",
"version": null,
"workflow": "Creator, workflow_name",
"workplace-srvc-delvry-ditamap": null
},
"page_id": "reuse/glossary/I/gloss-invoice-process-apo.html",
"page_key": 55688997,
"preprocessed_PDF": "https://downloads.docs.servicenow.com/pdf/enus/servicenow-yokohama-source-to-pay-operations-enus.pdf",
"rating": null,
"read_time_data": {
"char_count": 60,
"img_count": 0,
"read_time": 1,
"video_links": [
""
],
"word_count": 9
},
"related_links": [],
"search_title": null,
"title": "Invoice processing",
"topic_cluster": {
"clustered_by": {
"enabled": true,
"primary_key": "versions",
"primary_sort": "top-down",
"type": "subjecthead"
},
"clustered_labels": [
"versions"
],
"clustered_topics": [],
"clustering_title": "Zurich"
},
"topic_html": "<article class=\"hascomments\" data-page=\"bundle:zurich-source-to-pay-operations/enus/reuse/glossary/I/gloss-invoice-process-apo.html\" id=\"bundle:zurich-source-to-pay-operations/enus/reuse/glossary/I/gloss-invoice-process-apo.html\"><body id=\"gloss-invoice-process-apo\"><main role=\"main\"><article role=\"article\" class=\"dita\" id=\"gloss-invoice-process-apo\" aria-labelledby=\"title_gloss-invoice-process-apo\">\n <h1 class=\"title glossterm topictitle1\" id=\"title_gloss-invoice-process-apo\">Invoice processing</h1>\n <div class=\"abstract glossdef\">The end-to-end handling of invoices from receipt to payment.</div>\n \n<nav role=\"navigation\"></nav><nav role=\"navigation\" class=\"tasksNavigation\"></nav><nav role=\"navigation\" class=\"related-links\"></nav></article></main></body></article>",
"topic_language": "enus",
"views": 0,
"your_rating": null
} | # Invoice processing
The end-to-end handling of invoices from receipt to payment.
| ---
title: Invoice processing
description: The end-to-end handling of invoices from receipt to payment.
keywords: []
breadcrumbs:
- Finance and Supply Chain
- Accounts Payable Operations
- Accounts Payable Operations reference
- Approval Plan form
- Accounts Payable Operations glossary
- I
---
# Invoice processing
The end-to-end handling of invoices from receipt to payment.
|
https://www.servicenow.com/docs/en-US/bundle/zurich-source-to-pay-operations/page/reuse/glossary/P/gloss-purchase-order-apo.html | https://servicenow-be-prod.servicenow.com/api/bundle/zurich-source-to-pay-operations/page/reuse/glossary/P/gloss-purchase-order-apo.html | 2025-08-05 | daily | 0.5 | 268.xml | en-US | zurich-source-to-pay-operations | reuse/glossary/P/gloss-purchase-order-apo.html | zurich | Purchase order | A document issued by a buyer to a seller, detailing the items or services to be purchased. | [] | [
"Finance and Supply Chain",
"Accounts Payable Operations",
"Accounts Payable Operations reference",
"Approval Plan form",
"Accounts Payable Operations glossary",
"P"
] | <article class="hascomments" data-page="bundle:zurich-source-to-pay-operations/enus/reuse/glossary/P/gloss-purchase-order-apo.html" id="bundle:zurich-source-to-pay-operations/enus/reuse/glossary/P/gloss-purchase-order-apo.html"><body id="gloss-purchase-order-apo"><main role="main"><article role="article" class="dita" id="gloss-purchase-order-apo" aria-labelledby="title_gloss-purchase-order-apo">
<h1 class="title topictitle1" id="title_gloss-purchase-order-apo">Purchase order</h1>
<div class="body conbody"><p class="shortdesc">A document issued by a buyer to a seller, detailing the items or services to be purchased.</p></div>
<nav role="navigation"></nav><nav role="navigation" class="tasksNavigation"></nav><nav role="navigation" class="related-links"></nav></article></main></body></article> | {
"attachments": {
"all_attachments": null,
"topic_attachments": []
},
"available_languages": [
"enus"
],
"breadcrumbs": [
{
"title": "Finance and Supply Chain",
"topic_id": "product/source-to-pay-operations/concept/finance-supply-chain-landing.html"
},
{
"title": "Accounts Payable Operations",
"topic_id": "product/accounts-payable-operations/concept/acc-pay-mgmt-landing-page.html"
},
{
"title": "Accounts Payable Operations reference",
"topic_id": "product/accounts-payable-operations/reference/acc-pay-reference.html"
},
{
"title": "Approval Plan form",
"topic_id": "product/accounts-payable-operations/reference/approval-plan-form.html"
},
{
"title": "Accounts Payable Operations glossary",
"topic_id": "product/accounts-payable-operations/concept/apo-glossary.html"
},
{
"title": "P",
"topic_id": "product/accounts-payable-operations/concept/gloss-group-p-apo.html"
}
],
"breadcrumbs_html": "<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations\">Zurich Finance and Supply Chain</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/source-to-pay-operations/concept/finance-supply-chain-landing.html\">Finance and Supply Chain</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/concept/acc-pay-mgmt-landing-page.html\">Accounts Payable Operations</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/reference/acc-pay-reference.html\">Accounts Payable Operations reference</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/reference/approval-plan-form.html\">Approval Plan form</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/concept/apo-glossary.html\">Accounts Payable Operations glossary</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/concept/gloss-group-p-apo.html\">P</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<span class=\"active\">Purchase order</span>",
"bundle_id": "zurich-source-to-pay-operations",
"bundle_key": 2735,
"bundle_landing_page": "product/source-to-pay-operations/concept/finance-supply-chain-landing.html",
"bundle_subtitle": null,
"bundle_title": "Zurich Finance and Supply Chain",
"canonical_link": null,
"dates": {
"Added on": "2025-08-05T13:11:54.216332Z",
"Created on": "2024-11-04T00:00:00Z",
"Initial upload": "2025-07-30T22:25:52.095402Z",
"Updated on": "2025-07-31T00:00:00Z"
},
"dislike_url": "https://servicenow-be-prod.servicenow.com/dislike/55688998",
"dislikes": 0,
"es_archived_content": false,
"is_in_fav": false,
"is_liked": null,
"is_watched": false,
"keywords": [
" zurich zurich"
],
"labels": [
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "zurich",
"navtitle": "Zurich",
"outputclasses": [],
"subjectHeadId": "versions",
"subjectheadNavtitle": "Versions",
"visibility": "show-facet"
},
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "apmgt",
"navtitle": "Accounts Payable Operations",
"outputclasses": [],
"subjectHeadId": "products",
"subjectheadNavtitle": "Products",
"visibility": "show-facet"
}
],
"labels_text": "Versions > Zurich; Products > Finance and Supply Chain > Accounts Payable Operations",
"like_url": "https://servicenow-be-prod.servicenow.com/like/55688998",
"likes": 0,
"metadata": {
"AI Search": null,
"AI Search Assist": null,
"Application Insights": null,
"Capabilities": null,
"Code Signing": null,
"Contextual Search": null,
"DC.contributor": null,
"DC.coverage": null,
"DC.creator": "ServiceNow",
"DC.date.created": "2024-11-04T05:11:51+05:30",
"DC.date.modified": "2025-07-31",
"DC.format": "HTML5",
"DC.identifier": "gloss-purchase-order-apo",
"DC.language": null,
"DC.relation": "../../../product/accounts-payable-operations/concept/gloss-group-p-apo.html",
"DC.rights.owner": "(C) Copyright 2025",
"DC.subject": null,
"DC.type": "concept",
"Data Discovery": null,
"Data Policy": null,
"Data Privacy": null,
"Discovery": null,
"External Content for AI Search": null,
"Field Administration": null,
"Field Normalization": null,
"Key Management Framework": null,
"Localization Framework": null,
"Now Platform": null,
"PlatSec": null,
"Platform": null,
"Platform Administration": null,
"Platform Performance": null,
"Platform Privacy": null,
"Proactive Triggers": null,
"Process Optimization": null,
"RN doc editing record number": null,
"Search Administration": null,
"Secrets Management": null,
"ServiceNow AI Platform": null,
"State Model": null,
"Subscription Management": null,
"Task Communications Management": null,
"Timeline Visualizations": null,
"User Administration": null,
"User Experience Analytics": null,
"Zing": null,
"ai-now-assist": null,
"app-name": null,
"app_route": null,
"azureapimanagemen": null,
"change-completed": null,
"change-item": null,
"change-request-id": null,
"change-request-reference": null,
"com.glide.embedded_help.category": null,
"component": null,
"copyright": "(C) Copyright 2025",
"crossroads": null,
"data": null,
"description": "A document issued by a buyer to a seller, detailing the items or services to be purchased.",
"dominant_bundle": null,
"erp-canvas-video": null,
"fsm-mobile": null,
"fsm-route": null,
"fsm-sched-opt": null,
"fsm-wrk-order": null,
"genai-round-7": null,
"generator": "DITA-OT",
"glossPartOfSpeech": null,
"glossStatus": null,
"guided setup": null,
"guided tours": null,
"keywords": null,
"min-toc": null,
"mini": null,
"mini-to truec": null,
"mini-toc": null,
"mini_toc": null,
"minitoc": null,
"modification": null,
"now-assist-app-gen-video": null,
"order": null,
"page-type": null,
"page-type ": null,
"prodname": null,
"product": null,
"product_name": null,
"release": null,
"resourceID": null,
"roles": null,
"route_page": null,
"route_params_listId": null,
"route_params_table": null,
"route_params_type": null,
"route_type": null,
"setconfigurationproperties": null,
"topic": null,
"translation-type": "source",
"version": null,
"workflow": "Creator",
"workplace-srvc-delvry-ditamap": null
},
"page_id": "reuse/glossary/P/gloss-purchase-order-apo.html",
"page_key": 55688998,
"preprocessed_PDF": "https://downloads.docs.servicenow.com/pdf/enus/servicenow-yokohama-source-to-pay-operations-enus.pdf",
"rating": null,
"read_time_data": {
"char_count": 90,
"img_count": 0,
"read_time": 1,
"video_links": [
""
],
"word_count": 17
},
"related_links": [],
"search_title": null,
"title": "Purchase order",
"topic_cluster": {
"clustered_by": {
"enabled": true,
"primary_key": "versions",
"primary_sort": "top-down",
"type": "subjecthead"
},
"clustered_labels": [
"versions"
],
"clustered_topics": [],
"clustering_title": "Zurich"
},
"topic_html": "<article class=\"hascomments\" data-page=\"bundle:zurich-source-to-pay-operations/enus/reuse/glossary/P/gloss-purchase-order-apo.html\" id=\"bundle:zurich-source-to-pay-operations/enus/reuse/glossary/P/gloss-purchase-order-apo.html\"><body id=\"gloss-purchase-order-apo\"><main role=\"main\"><article role=\"article\" class=\"dita\" id=\"gloss-purchase-order-apo\" aria-labelledby=\"title_gloss-purchase-order-apo\">\n <h1 class=\"title topictitle1\" id=\"title_gloss-purchase-order-apo\">Purchase order</h1>\n \n \n <div class=\"body conbody\"><p class=\"shortdesc\">A document issued by a buyer to a seller, detailing the items or services to be purchased.</p></div>\n<nav role=\"navigation\"></nav><nav role=\"navigation\" class=\"tasksNavigation\"></nav><nav role=\"navigation\" class=\"related-links\"></nav></article></main></body></article>",
"topic_language": "enus",
"views": 0,
"your_rating": null
} | # Purchase order
A document issued by a buyer to a seller, detailing the items or services to be purchased.
| ---
title: Purchase order
description: A document issued by a buyer to a seller, detailing the items or services
to be purchased.
keywords: []
breadcrumbs:
- Finance and Supply Chain
- Accounts Payable Operations
- Accounts Payable Operations reference
- Approval Plan form
- Accounts Payable Operations glossary
- P
---
# Purchase order
A document issued by a buyer to a seller, detailing the items or services to be purchased.
|
https://www.servicenow.com/docs/en-US/bundle/zurich-source-to-pay-operations/page/reuse/glossary/S/gloss-supplier-management-apo.html | https://servicenow-be-prod.servicenow.com/api/bundle/zurich-source-to-pay-operations/page/reuse/glossary/S/gloss-supplier-management-apo.html | 2025-08-05 | daily | 0.5 | 268.xml | en-US | zurich-source-to-pay-operations | reuse/glossary/S/gloss-supplier-management-apo.html | zurich | supplier management | The process of managing relationships and transactions with suppliers. | [] | [
"Finance and Supply Chain",
"Accounts Payable Operations",
"Accounts Payable Operations reference",
"Approval Plan form",
"Accounts Payable Operations glossary",
"S"
] | <article class="hascomments" data-page="bundle:zurich-source-to-pay-operations/enus/reuse/glossary/S/gloss-supplier-management-apo.html" id="bundle:zurich-source-to-pay-operations/enus/reuse/glossary/S/gloss-supplier-management-apo.html"><body id="gloss-supplier-management-apo"><main role="main"><article role="article" class="dita" id="gloss-supplier-management-apo" aria-labelledby="title_gloss-supplier-management-apo">
<h1 class="title glossterm topictitle1" id="title_gloss-supplier-management-apo">supplier management</h1>
<div class="abstract glossdef">The process of managing relationships and transactions with suppliers.</div>
<nav role="navigation"></nav><nav role="navigation" class="tasksNavigation"></nav><nav role="navigation" class="related-links"></nav></article></main></body></article> | {
"attachments": {
"all_attachments": null,
"topic_attachments": []
},
"available_languages": [
"enus"
],
"breadcrumbs": [
{
"title": "Finance and Supply Chain",
"topic_id": "product/source-to-pay-operations/concept/finance-supply-chain-landing.html"
},
{
"title": "Accounts Payable Operations",
"topic_id": "product/accounts-payable-operations/concept/acc-pay-mgmt-landing-page.html"
},
{
"title": "Accounts Payable Operations reference",
"topic_id": "product/accounts-payable-operations/reference/acc-pay-reference.html"
},
{
"title": "Approval Plan form",
"topic_id": "product/accounts-payable-operations/reference/approval-plan-form.html"
},
{
"title": "Accounts Payable Operations glossary",
"topic_id": "product/accounts-payable-operations/concept/apo-glossary.html"
},
{
"title": "S",
"topic_id": "product/accounts-payable-operations/concept/gloss-group-s-apo.html"
}
],
"breadcrumbs_html": "<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations\">Zurich Finance and Supply Chain</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/source-to-pay-operations/concept/finance-supply-chain-landing.html\">Finance and Supply Chain</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/concept/acc-pay-mgmt-landing-page.html\">Accounts Payable Operations</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/reference/acc-pay-reference.html\">Accounts Payable Operations reference</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/reference/approval-plan-form.html\">Approval Plan form</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/concept/apo-glossary.html\">Accounts Payable Operations glossary</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/concept/gloss-group-s-apo.html\">S</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<span class=\"active\">supplier management</span>",
"bundle_id": "zurich-source-to-pay-operations",
"bundle_key": 2735,
"bundle_landing_page": "product/source-to-pay-operations/concept/finance-supply-chain-landing.html",
"bundle_subtitle": null,
"bundle_title": "Zurich Finance and Supply Chain",
"canonical_link": null,
"dates": {
"Added on": "2025-08-05T13:11:54.216332Z",
"Created on": "2024-11-04T00:00:00Z",
"Initial upload": "2025-07-30T22:25:52.095402Z",
"Updated on": "2025-07-31T00:00:00Z"
},
"dislike_url": "https://servicenow-be-prod.servicenow.com/dislike/55688999",
"dislikes": 0,
"es_archived_content": false,
"is_in_fav": false,
"is_liked": null,
"is_watched": false,
"keywords": [
" zurich zurich"
],
"labels": [
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "zurich",
"navtitle": "Zurich",
"outputclasses": [],
"subjectHeadId": "versions",
"subjectheadNavtitle": "Versions",
"visibility": "show-facet"
},
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "apmgt",
"navtitle": "Accounts Payable Operations",
"outputclasses": [],
"subjectHeadId": "products",
"subjectheadNavtitle": "Products",
"visibility": "show-facet"
}
],
"labels_text": "Versions > Zurich; Products > Finance and Supply Chain > Accounts Payable Operations",
"like_url": "https://servicenow-be-prod.servicenow.com/like/55688999",
"likes": 0,
"metadata": {
"AI Search": null,
"AI Search Assist": null,
"Application Insights": null,
"Capabilities": null,
"Code Signing": null,
"Contextual Search": null,
"DC.contributor": null,
"DC.coverage": null,
"DC.creator": "ServiceNow",
"DC.date.created": "2024-11-04T05:24:46+05:30",
"DC.date.modified": "2025-07-31",
"DC.format": "HTML5",
"DC.identifier": "gloss-supplier-management-apo",
"DC.language": null,
"DC.relation": "../../../product/accounts-payable-operations/concept/gloss-group-s-apo.html",
"DC.rights.owner": "(C) Copyright 2025",
"DC.subject": null,
"DC.type": "glossentry",
"Data Discovery": null,
"Data Policy": null,
"Data Privacy": null,
"Discovery": null,
"External Content for AI Search": null,
"Field Administration": null,
"Field Normalization": null,
"Key Management Framework": null,
"Localization Framework": null,
"Now Platform": null,
"PlatSec": null,
"Platform": null,
"Platform Administration": null,
"Platform Performance": null,
"Platform Privacy": null,
"Proactive Triggers": null,
"Process Optimization": null,
"RN doc editing record number": null,
"Search Administration": null,
"Secrets Management": null,
"ServiceNow AI Platform": null,
"State Model": null,
"Subscription Management": null,
"Task Communications Management": null,
"Timeline Visualizations": null,
"User Administration": null,
"User Experience Analytics": null,
"Zing": null,
"ai-now-assist": null,
"app-name": null,
"app_route": null,
"azureapimanagemen": null,
"change-completed": null,
"change-item": null,
"change-request-id": null,
"change-request-reference": null,
"com.glide.embedded_help.category": null,
"component": null,
"copyright": "(C) Copyright 2025",
"crossroads": null,
"data": null,
"description": "The process of managing relationships and transactions with suppliers.",
"dominant_bundle": null,
"erp-canvas-video": null,
"fsm-mobile": null,
"fsm-route": null,
"fsm-sched-opt": null,
"fsm-wrk-order": null,
"genai-round-7": null,
"generator": "DITA-OT",
"glossPartOfSpeech": null,
"glossStatus": null,
"guided setup": null,
"guided tours": null,
"keywords": null,
"min-toc": null,
"mini": null,
"mini-to truec": null,
"mini-toc": null,
"mini_toc": null,
"minitoc": null,
"modification": null,
"now-assist-app-gen-video": null,
"order": null,
"page-type": null,
"page-type ": null,
"prodname": null,
"product": "product_name",
"product_name": null,
"release": null,
"resourceID": null,
"roles": null,
"route_page": null,
"route_params_listId": null,
"route_params_table": null,
"route_params_type": null,
"route_type": null,
"setconfigurationproperties": null,
"topic": null,
"translation-type": "source",
"version": null,
"workflow": "Creator, workflow_name",
"workplace-srvc-delvry-ditamap": null
},
"page_id": "reuse/glossary/S/gloss-supplier-management-apo.html",
"page_key": 55688999,
"preprocessed_PDF": "https://downloads.docs.servicenow.com/pdf/enus/servicenow-yokohama-source-to-pay-operations-enus.pdf",
"rating": null,
"read_time_data": {
"char_count": 70,
"img_count": 0,
"read_time": 1,
"video_links": [
""
],
"word_count": 9
},
"related_links": [],
"search_title": null,
"title": "supplier management",
"topic_cluster": {
"clustered_by": {
"enabled": true,
"primary_key": "versions",
"primary_sort": "top-down",
"type": "subjecthead"
},
"clustered_labels": [
"versions"
],
"clustered_topics": [],
"clustering_title": "Zurich"
},
"topic_html": "<article class=\"hascomments\" data-page=\"bundle:zurich-source-to-pay-operations/enus/reuse/glossary/S/gloss-supplier-management-apo.html\" id=\"bundle:zurich-source-to-pay-operations/enus/reuse/glossary/S/gloss-supplier-management-apo.html\"><body id=\"gloss-supplier-management-apo\"><main role=\"main\"><article role=\"article\" class=\"dita\" id=\"gloss-supplier-management-apo\" aria-labelledby=\"title_gloss-supplier-management-apo\">\n <h1 class=\"title glossterm topictitle1\" id=\"title_gloss-supplier-management-apo\">supplier management</h1>\n <div class=\"abstract glossdef\">The process of managing relationships and transactions with suppliers.</div>\n \n<nav role=\"navigation\"></nav><nav role=\"navigation\" class=\"tasksNavigation\"></nav><nav role=\"navigation\" class=\"related-links\"></nav></article></main></body></article>",
"topic_language": "enus",
"views": 0,
"your_rating": null
} | # supplier management
The process of managing relationships and transactions with suppliers.
| ---
title: supplier management
description: The process of managing relationships and transactions with suppliers.
keywords: []
breadcrumbs:
- Finance and Supply Chain
- Accounts Payable Operations
- Accounts Payable Operations reference
- Approval Plan form
- Accounts Payable Operations glossary
- S
---
# supplier management
The process of managing relationships and transactions with suppliers.
|
https://www.servicenow.com/docs/en-US/bundle/zurich-source-to-pay-operations/page/reuse/glossary/T/gloss-tolerance-rules-apo.html | https://servicenow-be-prod.servicenow.com/api/bundle/zurich-source-to-pay-operations/page/reuse/glossary/T/gloss-tolerance-rules-apo.html | 2025-08-05 | daily | 0.5 | 268.xml | en-US | zurich-source-to-pay-operations | reuse/glossary/T/gloss-tolerance-rules-apo.html | zurich | tolerance rules | A limit that is set on invoices to determine acceptable variances before they require further review. | [] | [
"Finance and Supply Chain",
"Accounts Payable Operations",
"Accounts Payable Operations reference",
"Approval Plan form",
"Accounts Payable Operations glossary",
"T"
] | <article class="hascomments" data-page="bundle:zurich-source-to-pay-operations/enus/reuse/glossary/T/gloss-tolerance-rules-apo.html" id="bundle:zurich-source-to-pay-operations/enus/reuse/glossary/T/gloss-tolerance-rules-apo.html"><body id="gloss-tolerance-rules-apo"><main role="main"><article role="article" class="dita" id="gloss-tolerance-rules-apo" aria-labelledby="title_gloss-tolerance-rules-apo">
<h1 class="title glossterm topictitle1" id="title_gloss-tolerance-rules-apo">tolerance rules</h1>
<div class="abstract glossdef">A limit that is set on invoices to determine acceptable variances before they require further review.</div>
<nav role="navigation"></nav><nav role="navigation" class="tasksNavigation"></nav><nav role="navigation" class="related-links"></nav></article></main></body></article> | {
"attachments": {
"all_attachments": null,
"topic_attachments": []
},
"available_languages": [
"enus"
],
"breadcrumbs": [
{
"title": "Finance and Supply Chain",
"topic_id": "product/source-to-pay-operations/concept/finance-supply-chain-landing.html"
},
{
"title": "Accounts Payable Operations",
"topic_id": "product/accounts-payable-operations/concept/acc-pay-mgmt-landing-page.html"
},
{
"title": "Accounts Payable Operations reference",
"topic_id": "product/accounts-payable-operations/reference/acc-pay-reference.html"
},
{
"title": "Approval Plan form",
"topic_id": "product/accounts-payable-operations/reference/approval-plan-form.html"
},
{
"title": "Accounts Payable Operations glossary",
"topic_id": "product/accounts-payable-operations/concept/apo-glossary.html"
},
{
"title": "T",
"topic_id": "product/accounts-payable-operations/concept/gloss-group-t-apo.html"
}
],
"breadcrumbs_html": "<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations\">Zurich Finance and Supply Chain</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/source-to-pay-operations/concept/finance-supply-chain-landing.html\">Finance and Supply Chain</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/concept/acc-pay-mgmt-landing-page.html\">Accounts Payable Operations</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/reference/acc-pay-reference.html\">Accounts Payable Operations reference</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/reference/approval-plan-form.html\">Approval Plan form</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/concept/apo-glossary.html\">Accounts Payable Operations glossary</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/concept/gloss-group-t-apo.html\">T</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<span class=\"active\">tolerance rules</span>",
"bundle_id": "zurich-source-to-pay-operations",
"bundle_key": 2735,
"bundle_landing_page": "product/source-to-pay-operations/concept/finance-supply-chain-landing.html",
"bundle_subtitle": null,
"bundle_title": "Zurich Finance and Supply Chain",
"canonical_link": null,
"dates": {
"Added on": "2025-08-05T13:11:54.216332Z",
"Created on": "2024-11-04T00:00:00Z",
"Initial upload": "2025-07-30T22:25:52.095402Z",
"Updated on": "2025-07-31T00:00:00Z"
},
"dislike_url": "https://servicenow-be-prod.servicenow.com/dislike/55689000",
"dislikes": 0,
"es_archived_content": false,
"is_in_fav": false,
"is_liked": null,
"is_watched": false,
"keywords": [
" zurich zurich"
],
"labels": [
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "zurich",
"navtitle": "Zurich",
"outputclasses": [],
"subjectHeadId": "versions",
"subjectheadNavtitle": "Versions",
"visibility": "show-facet"
},
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "apmgt",
"navtitle": "Accounts Payable Operations",
"outputclasses": [],
"subjectHeadId": "products",
"subjectheadNavtitle": "Products",
"visibility": "show-facet"
}
],
"labels_text": "Versions > Zurich; Products > Finance and Supply Chain > Accounts Payable Operations",
"like_url": "https://servicenow-be-prod.servicenow.com/like/55689000",
"likes": 0,
"metadata": {
"AI Search": null,
"AI Search Assist": null,
"Application Insights": null,
"Capabilities": null,
"Code Signing": null,
"Contextual Search": null,
"DC.contributor": null,
"DC.coverage": null,
"DC.creator": "ServiceNow",
"DC.date.created": "2024-11-04T05:29:43+05:30",
"DC.date.modified": "2025-07-31",
"DC.format": "HTML5",
"DC.identifier": "gloss-tolerance-rules-apo",
"DC.language": null,
"DC.relation": "../../../product/accounts-payable-operations/concept/gloss-group-t-apo.html",
"DC.rights.owner": "(C) Copyright 2025",
"DC.subject": null,
"DC.type": "glossentry",
"Data Discovery": null,
"Data Policy": null,
"Data Privacy": null,
"Discovery": null,
"External Content for AI Search": null,
"Field Administration": null,
"Field Normalization": null,
"Key Management Framework": null,
"Localization Framework": null,
"Now Platform": null,
"PlatSec": null,
"Platform": null,
"Platform Administration": null,
"Platform Performance": null,
"Platform Privacy": null,
"Proactive Triggers": null,
"Process Optimization": null,
"RN doc editing record number": null,
"Search Administration": null,
"Secrets Management": null,
"ServiceNow AI Platform": null,
"State Model": null,
"Subscription Management": null,
"Task Communications Management": null,
"Timeline Visualizations": null,
"User Administration": null,
"User Experience Analytics": null,
"Zing": null,
"ai-now-assist": null,
"app-name": null,
"app_route": null,
"azureapimanagemen": null,
"change-completed": null,
"change-item": null,
"change-request-id": null,
"change-request-reference": null,
"com.glide.embedded_help.category": null,
"component": null,
"copyright": "(C) Copyright 2025",
"crossroads": null,
"data": null,
"description": "A limit that is set on invoices to determine acceptable variances before they require further review.",
"dominant_bundle": null,
"erp-canvas-video": null,
"fsm-mobile": null,
"fsm-route": null,
"fsm-sched-opt": null,
"fsm-wrk-order": null,
"genai-round-7": null,
"generator": "DITA-OT",
"glossPartOfSpeech": null,
"glossStatus": null,
"guided setup": null,
"guided tours": null,
"keywords": null,
"min-toc": null,
"mini": null,
"mini-to truec": null,
"mini-toc": null,
"mini_toc": null,
"minitoc": null,
"modification": null,
"now-assist-app-gen-video": null,
"order": null,
"page-type": null,
"page-type ": null,
"prodname": null,
"product": "product_name",
"product_name": null,
"release": null,
"resourceID": null,
"roles": null,
"route_page": null,
"route_params_listId": null,
"route_params_table": null,
"route_params_type": null,
"route_type": null,
"setconfigurationproperties": null,
"topic": null,
"translation-type": "source",
"version": null,
"workflow": "Creator, workflow_name",
"workplace-srvc-delvry-ditamap": null
},
"page_id": "reuse/glossary/T/gloss-tolerance-rules-apo.html",
"page_key": 55689000,
"preprocessed_PDF": "https://downloads.docs.servicenow.com/pdf/enus/servicenow-yokohama-source-to-pay-operations-enus.pdf",
"rating": null,
"read_time_data": {
"char_count": 101,
"img_count": 0,
"read_time": 1,
"video_links": [
""
],
"word_count": 16
},
"related_links": [],
"search_title": null,
"title": "tolerance rules",
"topic_cluster": {
"clustered_by": {
"enabled": true,
"primary_key": "versions",
"primary_sort": "top-down",
"type": "subjecthead"
},
"clustered_labels": [
"versions"
],
"clustered_topics": [],
"clustering_title": "Zurich"
},
"topic_html": "<article class=\"hascomments\" data-page=\"bundle:zurich-source-to-pay-operations/enus/reuse/glossary/T/gloss-tolerance-rules-apo.html\" id=\"bundle:zurich-source-to-pay-operations/enus/reuse/glossary/T/gloss-tolerance-rules-apo.html\"><body id=\"gloss-tolerance-rules-apo\"><main role=\"main\"><article role=\"article\" class=\"dita\" id=\"gloss-tolerance-rules-apo\" aria-labelledby=\"title_gloss-tolerance-rules-apo\">\n <h1 class=\"title glossterm topictitle1\" id=\"title_gloss-tolerance-rules-apo\">tolerance rules</h1>\n <div class=\"abstract glossdef\">A limit that is set on invoices to determine acceptable variances before they require further review.</div>\n \n<nav role=\"navigation\"></nav><nav role=\"navigation\" class=\"tasksNavigation\"></nav><nav role=\"navigation\" class=\"related-links\"></nav></article></main></body></article>",
"topic_language": "enus",
"views": 0,
"your_rating": null
} | # tolerance rules
A limit that is set on invoices to determine acceptable variances before they require further review.
| ---
title: tolerance rules
description: A limit that is set on invoices to determine acceptable variances before
they require further review.
keywords: []
breadcrumbs:
- Finance and Supply Chain
- Accounts Payable Operations
- Accounts Payable Operations reference
- Approval Plan form
- Accounts Payable Operations glossary
- T
---
# tolerance rules
A limit that is set on invoices to determine acceptable variances before they require further review.
|
https://www.servicenow.com/docs/en-US/bundle/zurich-source-to-pay-operations/page/reuse/glossary/V/gloss-virtual-agent-apo.html | https://servicenow-be-prod.servicenow.com/api/bundle/zurich-source-to-pay-operations/page/reuse/glossary/V/gloss-virtual-agent-apo.html | 2025-08-05 | daily | 0.5 | 268.xml | en-US | zurich-source-to-pay-operations | reuse/glossary/V/gloss-virtual-agent-apo.html | zurich | virtual agent | An AI-driven assistant for handling common requests and inquiries. | [] | [
"Finance and Supply Chain",
"Accounts Payable Operations",
"Accounts Payable Operations reference",
"Approval Plan form",
"Accounts Payable Operations glossary",
"V"
] | <article class="hascomments" data-page="bundle:zurich-source-to-pay-operations/enus/reuse/glossary/V/gloss-virtual-agent-apo.html" id="bundle:zurich-source-to-pay-operations/enus/reuse/glossary/V/gloss-virtual-agent-apo.html"><body id="gloss-virtual-agent-apo"><main role="main"><article role="article" class="dita" id="gloss-virtual-agent-apo" aria-labelledby="title_gloss-virtual-agent-apo">
<h1 class="title glossterm topictitle1" id="title_gloss-virtual-agent-apo">virtual agent</h1>
<div class="abstract glossdef">An AI-driven assistant for handling common requests and inquiries.</div>
<nav role="navigation"></nav><nav role="navigation" class="tasksNavigation"></nav><nav role="navigation" class="related-links"></nav></article></main></body></article> | {
"attachments": {
"all_attachments": null,
"topic_attachments": []
},
"available_languages": [
"enus"
],
"breadcrumbs": [
{
"title": "Finance and Supply Chain",
"topic_id": "product/source-to-pay-operations/concept/finance-supply-chain-landing.html"
},
{
"title": "Accounts Payable Operations",
"topic_id": "product/accounts-payable-operations/concept/acc-pay-mgmt-landing-page.html"
},
{
"title": "Accounts Payable Operations reference",
"topic_id": "product/accounts-payable-operations/reference/acc-pay-reference.html"
},
{
"title": "Approval Plan form",
"topic_id": "product/accounts-payable-operations/reference/approval-plan-form.html"
},
{
"title": "Accounts Payable Operations glossary",
"topic_id": "product/accounts-payable-operations/concept/apo-glossary.html"
},
{
"title": "V",
"topic_id": "product/accounts-payable-operations/concept/gloss-group-v-apo.html"
}
],
"breadcrumbs_html": "<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations\">Zurich Finance and Supply Chain</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/source-to-pay-operations/concept/finance-supply-chain-landing.html\">Finance and Supply Chain</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/concept/acc-pay-mgmt-landing-page.html\">Accounts Payable Operations</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/reference/acc-pay-reference.html\">Accounts Payable Operations reference</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/reference/approval-plan-form.html\">Approval Plan form</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/concept/apo-glossary.html\">Accounts Payable Operations glossary</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/concept/gloss-group-v-apo.html\">V</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<span class=\"active\">virtual agent</span>",
"bundle_id": "zurich-source-to-pay-operations",
"bundle_key": 2735,
"bundle_landing_page": "product/source-to-pay-operations/concept/finance-supply-chain-landing.html",
"bundle_subtitle": null,
"bundle_title": "Zurich Finance and Supply Chain",
"canonical_link": null,
"dates": {
"Added on": "2025-08-05T13:11:54.216332Z",
"Created on": "2024-11-04T00:00:00Z",
"Initial upload": "2025-07-30T22:25:52.095402Z",
"Updated on": "2025-07-31T00:00:00Z"
},
"dislike_url": "https://servicenow-be-prod.servicenow.com/dislike/55689001",
"dislikes": 0,
"es_archived_content": false,
"is_in_fav": false,
"is_liked": null,
"is_watched": false,
"keywords": [
" zurich zurich"
],
"labels": [
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "zurich",
"navtitle": "Zurich",
"outputclasses": [],
"subjectHeadId": "versions",
"subjectheadNavtitle": "Versions",
"visibility": "show-facet"
},
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "apmgt",
"navtitle": "Accounts Payable Operations",
"outputclasses": [],
"subjectHeadId": "products",
"subjectheadNavtitle": "Products",
"visibility": "show-facet"
}
],
"labels_text": "Versions > Zurich; Products > Finance and Supply Chain > Accounts Payable Operations",
"like_url": "https://servicenow-be-prod.servicenow.com/like/55689001",
"likes": 0,
"metadata": {
"AI Search": null,
"AI Search Assist": null,
"Application Insights": null,
"Capabilities": null,
"Code Signing": null,
"Contextual Search": null,
"DC.contributor": null,
"DC.coverage": null,
"DC.creator": "ServiceNow",
"DC.date.created": "2024-11-04T05:26:15+05:30",
"DC.date.modified": "2025-07-31",
"DC.format": "HTML5",
"DC.identifier": "gloss-virtual-agent-apo",
"DC.language": null,
"DC.relation": "../../../product/accounts-payable-operations/concept/gloss-group-v-apo.html",
"DC.rights.owner": "(C) Copyright 2025",
"DC.subject": null,
"DC.type": "glossentry",
"Data Discovery": null,
"Data Policy": null,
"Data Privacy": null,
"Discovery": null,
"External Content for AI Search": null,
"Field Administration": null,
"Field Normalization": null,
"Key Management Framework": null,
"Localization Framework": null,
"Now Platform": null,
"PlatSec": null,
"Platform": null,
"Platform Administration": null,
"Platform Performance": null,
"Platform Privacy": null,
"Proactive Triggers": null,
"Process Optimization": null,
"RN doc editing record number": null,
"Search Administration": null,
"Secrets Management": null,
"ServiceNow AI Platform": null,
"State Model": null,
"Subscription Management": null,
"Task Communications Management": null,
"Timeline Visualizations": null,
"User Administration": null,
"User Experience Analytics": null,
"Zing": null,
"ai-now-assist": null,
"app-name": null,
"app_route": null,
"azureapimanagemen": null,
"change-completed": null,
"change-item": null,
"change-request-id": null,
"change-request-reference": null,
"com.glide.embedded_help.category": null,
"component": null,
"copyright": "(C) Copyright 2025",
"crossroads": null,
"data": null,
"description": "An AI-driven assistant for handling common requests and inquiries.",
"dominant_bundle": null,
"erp-canvas-video": null,
"fsm-mobile": null,
"fsm-route": null,
"fsm-sched-opt": null,
"fsm-wrk-order": null,
"genai-round-7": null,
"generator": "DITA-OT",
"glossPartOfSpeech": null,
"glossStatus": null,
"guided setup": null,
"guided tours": null,
"keywords": null,
"min-toc": null,
"mini": null,
"mini-to truec": null,
"mini-toc": null,
"mini_toc": null,
"minitoc": null,
"modification": null,
"now-assist-app-gen-video": null,
"order": null,
"page-type": null,
"page-type ": null,
"prodname": null,
"product": "product_name",
"product_name": null,
"release": null,
"resourceID": null,
"roles": null,
"route_page": null,
"route_params_listId": null,
"route_params_table": null,
"route_params_type": null,
"route_type": null,
"setconfigurationproperties": null,
"topic": null,
"translation-type": "source",
"version": null,
"workflow": "Creator, workflow_name",
"workplace-srvc-delvry-ditamap": null
},
"page_id": "reuse/glossary/V/gloss-virtual-agent-apo.html",
"page_key": 55689001,
"preprocessed_PDF": "https://downloads.docs.servicenow.com/pdf/enus/servicenow-yokohama-source-to-pay-operations-enus.pdf",
"rating": null,
"read_time_data": {
"char_count": 66,
"img_count": 0,
"read_time": 1,
"video_links": [
""
],
"word_count": 9
},
"related_links": [],
"search_title": null,
"title": "virtual agent",
"topic_cluster": {
"clustered_by": {
"enabled": true,
"primary_key": "versions",
"primary_sort": "top-down",
"type": "subjecthead"
},
"clustered_labels": [
"versions"
],
"clustered_topics": [],
"clustering_title": "Zurich"
},
"topic_html": "<article class=\"hascomments\" data-page=\"bundle:zurich-source-to-pay-operations/enus/reuse/glossary/V/gloss-virtual-agent-apo.html\" id=\"bundle:zurich-source-to-pay-operations/enus/reuse/glossary/V/gloss-virtual-agent-apo.html\"><body id=\"gloss-virtual-agent-apo\"><main role=\"main\"><article role=\"article\" class=\"dita\" id=\"gloss-virtual-agent-apo\" aria-labelledby=\"title_gloss-virtual-agent-apo\">\n <h1 class=\"title glossterm topictitle1\" id=\"title_gloss-virtual-agent-apo\">virtual agent</h1>\n <div class=\"abstract glossdef\">An AI-driven assistant for handling common requests and inquiries.</div>\n \n<nav role=\"navigation\"></nav><nav role=\"navigation\" class=\"tasksNavigation\"></nav><nav role=\"navigation\" class=\"related-links\"></nav></article></main></body></article>",
"topic_language": "enus",
"views": 0,
"your_rating": null
} | # virtual agent
An AI-driven assistant for handling common requests and inquiries.
| ---
title: virtual agent
description: An AI-driven assistant for handling common requests and inquiries.
keywords: []
breadcrumbs:
- Finance and Supply Chain
- Accounts Payable Operations
- Accounts Payable Operations reference
- Approval Plan form
- Accounts Payable Operations glossary
- V
---
# virtual agent
An AI-driven assistant for handling common requests and inquiries.
|
https://www.servicenow.com/docs/en-US/bundle/zurich-source-to-pay-operations/page/reuse/glossary/W/gloss-work-item-queue-apo.html | https://servicenow-be-prod.servicenow.com/api/bundle/zurich-source-to-pay-operations/page/reuse/glossary/W/gloss-work-item-queue-apo.html | 2025-08-05 | daily | 0.5 | 268.xml | en-US | zurich-source-to-pay-operations | reuse/glossary/W/gloss-work-item-queue-apo.html | zurich | Work item queue | A storage area for work items waiting to be assigned to agents. | [] | [
"Finance and Supply Chain",
"Accounts Payable Operations",
"Accounts Payable Operations reference",
"Approval Plan form",
"Accounts Payable Operations glossary",
"W"
] | <article class="hascomments" data-page="bundle:zurich-source-to-pay-operations/enus/reuse/glossary/W/gloss-work-item-queue-apo.html" id="bundle:zurich-source-to-pay-operations/enus/reuse/glossary/W/gloss-work-item-queue-apo.html"><body id="gloss-work-item-queue-apo"><main role="main"><article role="article" class="dita" id="gloss-work-item-queue-apo" aria-labelledby="title_gloss-work-item-queue-apo">
<h1 class="title glossterm topictitle1" id="title_gloss-work-item-queue-apo">Work item queue</h1>
<div class="abstract glossdef">A storage area for work items waiting to be assigned to agents.</div>
<nav role="navigation"></nav><nav role="navigation" class="tasksNavigation"></nav><nav role="navigation" class="related-links"></nav></article></main></body></article> | {
"attachments": {
"all_attachments": null,
"topic_attachments": []
},
"available_languages": [
"enus"
],
"breadcrumbs": [
{
"title": "Finance and Supply Chain",
"topic_id": "product/source-to-pay-operations/concept/finance-supply-chain-landing.html"
},
{
"title": "Accounts Payable Operations",
"topic_id": "product/accounts-payable-operations/concept/acc-pay-mgmt-landing-page.html"
},
{
"title": "Accounts Payable Operations reference",
"topic_id": "product/accounts-payable-operations/reference/acc-pay-reference.html"
},
{
"title": "Approval Plan form",
"topic_id": "product/accounts-payable-operations/reference/approval-plan-form.html"
},
{
"title": "Accounts Payable Operations glossary",
"topic_id": "product/accounts-payable-operations/concept/apo-glossary.html"
},
{
"title": "W",
"topic_id": "product/accounts-payable-operations/concept/gloss-group-w-apo.html"
}
],
"breadcrumbs_html": "<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations\">Zurich Finance and Supply Chain</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/source-to-pay-operations/concept/finance-supply-chain-landing.html\">Finance and Supply Chain</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/concept/acc-pay-mgmt-landing-page.html\">Accounts Payable Operations</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/reference/acc-pay-reference.html\">Accounts Payable Operations reference</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/reference/approval-plan-form.html\">Approval Plan form</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/concept/apo-glossary.html\">Accounts Payable Operations glossary</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-source-to-pay-operations/page/product/accounts-payable-operations/concept/gloss-group-w-apo.html\">W</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<span class=\"active\">Work item queue</span>",
"bundle_id": "zurich-source-to-pay-operations",
"bundle_key": 2735,
"bundle_landing_page": "product/source-to-pay-operations/concept/finance-supply-chain-landing.html",
"bundle_subtitle": null,
"bundle_title": "Zurich Finance and Supply Chain",
"canonical_link": null,
"dates": {
"Added on": "2025-08-05T13:11:54.216332Z",
"Created on": "2024-11-04T00:00:00Z",
"Initial upload": "2025-07-30T22:25:52.095402Z",
"Updated on": "2025-07-31T00:00:00Z"
},
"dislike_url": "https://servicenow-be-prod.servicenow.com/dislike/55689002",
"dislikes": 0,
"es_archived_content": false,
"is_in_fav": false,
"is_liked": null,
"is_watched": false,
"keywords": [
" zurich zurich"
],
"labels": [
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "zurich",
"navtitle": "Zurich",
"outputclasses": [],
"subjectHeadId": "versions",
"subjectheadNavtitle": "Versions",
"visibility": "show-facet"
},
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "apmgt",
"navtitle": "Accounts Payable Operations",
"outputclasses": [],
"subjectHeadId": "products",
"subjectheadNavtitle": "Products",
"visibility": "show-facet"
}
],
"labels_text": "Versions > Zurich; Products > Finance and Supply Chain > Accounts Payable Operations",
"like_url": "https://servicenow-be-prod.servicenow.com/like/55689002",
"likes": 0,
"metadata": {
"AI Search": null,
"AI Search Assist": null,
"Application Insights": null,
"Capabilities": null,
"Code Signing": null,
"Contextual Search": null,
"DC.contributor": null,
"DC.coverage": null,
"DC.creator": "ServiceNow",
"DC.date.created": "2024-11-04T05:53:20+05:30",
"DC.date.modified": "2025-07-31",
"DC.format": "HTML5",
"DC.identifier": "gloss-work-item-queue-apo",
"DC.language": null,
"DC.relation": "../../../product/accounts-payable-operations/concept/gloss-group-w-apo.html",
"DC.rights.owner": "(C) Copyright 2025",
"DC.subject": null,
"DC.type": "glossentry",
"Data Discovery": null,
"Data Policy": null,
"Data Privacy": null,
"Discovery": null,
"External Content for AI Search": null,
"Field Administration": null,
"Field Normalization": null,
"Key Management Framework": null,
"Localization Framework": null,
"Now Platform": null,
"PlatSec": null,
"Platform": null,
"Platform Administration": null,
"Platform Performance": null,
"Platform Privacy": null,
"Proactive Triggers": null,
"Process Optimization": null,
"RN doc editing record number": null,
"Search Administration": null,
"Secrets Management": null,
"ServiceNow AI Platform": null,
"State Model": null,
"Subscription Management": null,
"Task Communications Management": null,
"Timeline Visualizations": null,
"User Administration": null,
"User Experience Analytics": null,
"Zing": null,
"ai-now-assist": null,
"app-name": null,
"app_route": null,
"azureapimanagemen": null,
"change-completed": null,
"change-item": null,
"change-request-id": null,
"change-request-reference": null,
"com.glide.embedded_help.category": null,
"component": null,
"copyright": "(C) Copyright 2025",
"crossroads": null,
"data": null,
"description": "A storage area for work items waiting to be assigned to agents.",
"dominant_bundle": null,
"erp-canvas-video": null,
"fsm-mobile": null,
"fsm-route": null,
"fsm-sched-opt": null,
"fsm-wrk-order": null,
"genai-round-7": null,
"generator": "DITA-OT",
"glossPartOfSpeech": null,
"glossStatus": null,
"guided setup": null,
"guided tours": null,
"keywords": null,
"min-toc": null,
"mini": null,
"mini-to truec": null,
"mini-toc": null,
"mini_toc": null,
"minitoc": null,
"modification": null,
"now-assist-app-gen-video": null,
"order": null,
"page-type": null,
"page-type ": null,
"prodname": null,
"product": "product_name",
"product_name": null,
"release": null,
"resourceID": null,
"roles": null,
"route_page": null,
"route_params_listId": null,
"route_params_table": null,
"route_params_type": null,
"route_type": null,
"setconfigurationproperties": null,
"topic": null,
"translation-type": "source",
"version": null,
"workflow": "Creator, workflow_name",
"workplace-srvc-delvry-ditamap": null
},
"page_id": "reuse/glossary/W/gloss-work-item-queue-apo.html",
"page_key": 55689002,
"preprocessed_PDF": "https://downloads.docs.servicenow.com/pdf/enus/servicenow-yokohama-source-to-pay-operations-enus.pdf",
"rating": null,
"read_time_data": {
"char_count": 63,
"img_count": 0,
"read_time": 1,
"video_links": [
""
],
"word_count": 12
},
"related_links": [],
"search_title": null,
"title": "Work item queue",
"topic_cluster": {
"clustered_by": {
"enabled": true,
"primary_key": "versions",
"primary_sort": "top-down",
"type": "subjecthead"
},
"clustered_labels": [
"versions"
],
"clustered_topics": [],
"clustering_title": "Zurich"
},
"topic_html": "<article class=\"hascomments\" data-page=\"bundle:zurich-source-to-pay-operations/enus/reuse/glossary/W/gloss-work-item-queue-apo.html\" id=\"bundle:zurich-source-to-pay-operations/enus/reuse/glossary/W/gloss-work-item-queue-apo.html\"><body id=\"gloss-work-item-queue-apo\"><main role=\"main\"><article role=\"article\" class=\"dita\" id=\"gloss-work-item-queue-apo\" aria-labelledby=\"title_gloss-work-item-queue-apo\">\n <h1 class=\"title glossterm topictitle1\" id=\"title_gloss-work-item-queue-apo\">Work item queue</h1>\n <div class=\"abstract glossdef\">A storage area for work items waiting to be assigned to agents.</div>\n \n<nav role=\"navigation\"></nav><nav role=\"navigation\" class=\"tasksNavigation\"></nav><nav role=\"navigation\" class=\"related-links\"></nav></article></main></body></article>",
"topic_language": "enus",
"views": 0,
"your_rating": null
} | # Work item queue
A storage area for work items waiting to be assigned to agents.
| ---
title: Work item queue
description: A storage area for work items waiting to be assigned to agents.
keywords: []
breadcrumbs:
- Finance and Supply Chain
- Accounts Payable Operations
- Accounts Payable Operations reference
- Approval Plan form
- Accounts Payable Operations glossary
- W
---
# Work item queue
A storage area for work items waiting to be assigned to agents.
|
https://www.servicenow.com/docs/en-US/bundle/zurich-telecom-media-technology/page/product/industry-products/concept/telecom-media-tech-landing.html | https://servicenow-be-prod.servicenow.com/api/bundle/zurich-telecom-media-technology/page/product/industry-products/concept/telecom-media-tech-landing.html | 2025-08-02 | daily | 0.5 | 268.xml | en-US | zurich-telecom-media-technology | product/industry-products/concept/telecom-media-tech-landing.html | zurich | Telecommunications, Media, and Technology (TMT) | The ServiceNow® Telecommunications, Media, and Technology (TMT) product suite brings together customer care, operations, order management, and partner ecosystems so that service providers can scale their business to capitalize on the fast-growing “everything-as-a-service" opportunity. | [] | [] | <article class="hascomments" data-page="bundle:zurich-telecom-media-technology/enus/product/industry-products/concept/telecom-media-tech-landing.html" id="bundle:zurich-telecom-media-technology/enus/product/industry-products/concept/telecom-media-tech-landing.html"><body id="telecom-media-tech-landing"><main role="main"><article role="article" class="dita" id="telecom-media-tech-landing" aria-labelledby="title_telecom-media-tech-landing">
<h1 class="title topictitle1" id="title_telecom-media-tech-landing">Telecommunications, Media, and Technology (TMT)</h1>
<div class="body conbody"><p class="shortdesc">The <span class="ph">ServiceNow®</span> Telecommunications, Media, and Technology (TMT) product suite brings together customer care, operations, order management, and partner ecosystems so that service providers can scale their business to
capitalize on the fast-growing “everything-as-a-service" opportunity.</p>
<section class="section" id="telecom-media-tech-landing__section_olz_s1v_j5b">
<div class="table-wrap"><table count-columns="3" class="table nav-card frame-none" id="telecom-media-tech-landing__table_cry_rvq_pvb" role="presentation"><caption></caption><colgroup><col style="width:33.33333333333333%"/><col style="width:33.33333333333333%"/><col style="width:33.33333333333333%"/></colgroup><tbody class="tbody">
<tr class="row">
<td class="entry">
<p class="p"><a data-bundleid="zurich-telecom-media-technology" data-navpath="product/industry-products/concept//csh" href="https://servicenow-be-prod.servicenow.com/csh?topicname=account-lifecycle-events-landing&version=zurich&pubname=zurich-acct-lifecycle-events" class="xref"><span class="ph nav-card-title">Customer Success Management</span>
<svg class="image svg decorative" id="telecom-media-tech-landing__image_o4b_dqp_fyb" viewBox="0 0 64 64" title="" width="64" height="64"><title></title><defs></defs><rect class="cls-1" style="fill:#62d84e;;" x="27" y="28" width="9" height="9" rx="2"></rect><rect class="cls-1" style="fill:#62d84e;;" x="14" y="28" width="9" height="9" rx="2"></rect><rect class="cls-1" style="fill:#62d84e;;" x="40" y="28" width="9" height="9" rx="2"></rect><path d="M54.5,5H47V4.5a1.5,1.5,0,0,0-3,0V5H19V4.5a1.5,1.5,0,0,0-3,0V5H8.5A4.51,4.51,0,0,0,4,9.5v46A4.51,4.51,0,0,0,8.5,60h46A4.51,4.51,0,0,0,59,55.5V9.5A4.51,4.51,0,0,0,54.5,5ZM8.5,8H16v2.5a1.5,1.5,0,0,0,3,0V8H44v2.5a1.5,1.5,0,0,0,3,0V8h7.5A1.5,1.5,0,0,1,56,9.5V17H7V9.5A1.5,1.5,0,0,1,8.5,8Zm46,49H8.5A1.5,1.5,0,0,1,7,55.5V20H56V55.5A1.5,1.5,0,0,1,54.5,57Z"></path><rect class="cls-2" style="fill:none;;" width="64" height="64"></rect></svg>
<span class="ph">Streamline, automate, and measure critical workflows across the enterprise.</span></a></p>
</td>
<td class="entry">
<p class="p"><a data-bundleid="zurich-telecom-media-technology" data-navpath="product/industry-products/concept//csh" href="https://servicenow-be-prod.servicenow.com/csh?topicname=order-mgt-overview&version=zurich&pubname=zurich-order-management" class="xref"><span class="ph nav-card-title">Sales and Order Management</span><svg class="image svg decorative" id="telecom-media-tech-landing__image_bbz_dr1_gyb" viewBox="0 0 64 64" title="" width="64" height="64"><title></title><defs></defs><path class="cls-1" style="fill:#62d84e;;" d="M28.1,30.53A4.53,4.53,0,1,1,23.57,26a4.53,4.53,0,0,1,4.53,4.53Zm2.73,13.59c.91,0,1.64-.68,1.47-1.42-.8-3.41-4.4-6-8.73-6s-7.94,2.58-8.74,6c-.17.74.56,1.42,1.47,1.42Z"></path><path d="M48.07,35.38h-15a1.12,1.12,0,0,0,0,2.24h15a1.12,1.12,0,0,0,0-2.24Z"></path><path d="M48.07,29.38h-15a1.12,1.12,0,0,0,0,2.24h15a1.12,1.12,0,0,0,0-2.24Z"></path><path d="M48.07,23.38h-15a1.12,1.12,0,0,0,0,2.24h15a1.12,1.12,0,0,0,0-2.24Z"></path><path d="M48.07,41.38h-12a1.12,1.12,0,0,0,0,2.24h12a1.12,1.12,0,0,0,0-2.24Z"></path><path d="M52.22,51H11.78A3.28,3.28,0,0,1,8.5,47.72V19.28A3.28,3.28,0,0,1,11.78,16H52.22a3.28,3.28,0,0,1,3.28,3.28V47.72A3.28,3.28,0,0,1,52.22,51ZM11.78,18a1.28,1.28,0,0,0-1.28,1.28h0V47.72A1.28,1.28,0,0,0,11.78,49H52.22a1.28,1.28,0,0,0,1.28-1.28V19.28A1.28,1.28,0,0,0,52.22,18Z"></path><rect class="cls-2" style="fill:none;;" width="64" height="64"></rect></svg><span class="ph">Capture, manage, and fulfill customer and external service orders. </span></a></p>
</td>
<td class="entry">
<p class="p"><a data-bundleid="zurich-telecom-media-technology" data-navpath="product/industry-products/concept//csh" href="https://servicenow-be-prod.servicenow.com/csh?topicname=assurance-workflows&version=zurich&pubname=zurich-proactive-service-exp-workflows" class="xref"><span class="ph nav-card-title">Proactive Service Experience Workflows</span><svg class="image svg decorative" id="telecom-media-tech-landing__image_hxs_xqp_fyb" viewBox="0 0 64 64" title="" width="64" height="64"><title></title><defs></defs><path d="M12.5,23A7.5,7.5,0,1,1,20,15.5,7.5,7.5,0,0,1,12.5,23Zm0-12A4.5,4.5,0,1,0,17,15.5,4.51,4.51,0,0,0,12.5,11Zm36,48A7.5,7.5,0,1,1,56,51.5,7.5,7.5,0,0,1,48.5,59Zm0-12A4.5,4.5,0,1,0,53,51.5,4.51,4.51,0,0,0,48.5,47Zm0-22a1.51,1.51,0,0,1-1.06-.44l-8-8a1.49,1.49,0,0,1,0-2.12l8-8a1.49,1.49,0,0,1,2.12,0l8,8a1.49,1.49,0,0,1,0,2.12l-8,8A1.51,1.51,0,0,1,48.5,25Zm-5.88-9.5,5.88,5.88,5.88-5.88L48.5,9.62Z"></path><path class="cls-1" style="fill:#62d84e;;" d="M29.44,18.44a1.49,1.49,0,0,0,0,2.12,1.5,1.5,0,0,0,2.12,0l4-4a1.49,1.49,0,0,0,0-2.12l-4-4a1.5,1.5,0,0,0-2.12,2.12L30.88,14H24.5a1.5,1.5,0,0,0,0,3h6.38Z"></path><path class="cls-1" style="fill:#62d84e;;" d="M36.5,50H30.12l1.44-1.44a1.5,1.5,0,0,0-2.12-2.12l-4,4a1.49,1.49,0,0,0,0,2.12l4,4a1.5,1.5,0,0,0,2.12,0,1.49,1.49,0,0,0,0-2.12L30.12,53H36.5a1.5,1.5,0,0,0,0-3Z"></path><path class="cls-1" style="fill:#62d84e;;" d="M53.56,33.44a1.49,1.49,0,0,0-2.12,0L50,34.88V29.5a1.5,1.5,0,0,0-3,0v5.38l-1.44-1.44a1.5,1.5,0,0,0-2.12,2.12l4,4a1.5,1.5,0,0,0,2.12,0l4-4A1.49,1.49,0,0,0,53.56,33.44Z"></path><rect class="cls-1" style="fill:#62d84e;;" x="5" y="44" width="15" height="15" rx="1.5"></rect><rect class="cls-2" style="fill:none;;" width="64" height="64"></rect></svg>
<span class="ph">Deliver end-to-end workflows to resolve network related incidents, and proactively notify impacted customers.</span></a></p>
</td>
</tr>
<tr class="row">
<td class="entry">
<p class="p"><a data-bundleid="zurich-telecom-media-technology" data-navpath="product/industry-products/concept//csh" href="https://servicenow-be-prod.servicenow.com/csh?topicname=tmt-service-bridge-both-landing-page&version=zurich&pubname=zurich-service-bridge" class="xref"><span class="ph nav-card-title">Service Bridge</span>
<svg class="image svg decorative" id="telecom-media-tech-landing__image_lg5_bmj_b2c" viewBox="0 0 64 64" title="" width="64" height="64"><title></title><defs></defs><path d="M53.76,39.66a1.5,1.5,0,0,1-.84-2.74L58.8,33,35.63,17.56a1.5,1.5,0,0,1,1.66-2.5l25,16.69a1.5,1.5,0,0,1,0,2.5l-7.74,5.16A1.52,1.52,0,0,1,53.76,39.66Z"></path><path d="M27.17,51.62a1.53,1.53,0,0,1-.83-.26L.67,34.25a1.5,1.5,0,0,1,0-2.5l8-5.31a1.5,1.5,0,1,1,1.66,2.5L4.2,33,28,48.87a1.5,1.5,0,0,1-.83,2.75Z"></path><path class="cls-1" style="fill:#62d84e;;" d="M14.77,24.71A.85.85,0,0,1,14,23.5l5.35-11.74a.84.84,0,0,1,1.48-.1l2.91,4.58,2.82-1.93A3.32,3.32,0,0,0,28,11.58V4.51a1.5,1.5,0,1,1,3,0v7.66a5.21,5.21,0,0,1-2.28,4.31l-3.37,2.31,2.46,3.89A.85.85,0,0,1,27.15,24Z"></path><path class="cls-1" style="fill:#62d84e;;" d="M33.5,62.08a1.5,1.5,0,0,1-1.5-1.5v-6a8.14,8.14,0,0,1,3.57-6.75l2.08-1.42-2.46-3.87a.82.82,0,0,1,0-.84.83.83,0,0,1,.7-.46l12.33-.71a.88.88,0,0,1,.76.39.84.84,0,0,1,.06.81L43.65,53.37a.82.82,0,0,1-.77.5h0a.84.84,0,0,1-.71-.4l-2.91-4.55-2,1.36A5.15,5.15,0,0,0,35,54.55v6A1.5,1.5,0,0,1,33.5,62.08Z"></path><rect class="cls-2" style="fill:none;;" width="64" height="64"></rect></svg><span class="ph">Help customers and providers connect and track service requests directly between their instances.</span></a></p>
</td>
<td class="entry">
<p class="p"><a data-bundleid="zurich-telecom-media-technology" data-navpath="product/industry-products/concept//csh" href="https://servicenow-be-prod.servicenow.com/csh?topicname=telecom-network-inventory&version=zurich&pubname=zurich-telecom-network-inventory" class="xref"><span class="ph nav-card-title">Telecommunications Network Inventory</span>
<svg class="image svg decorative" id="telecom-media-tech-landing__image_ll5_kmp_fyb" viewBox="0 0 64 64" title="" width="64" height="64"><title></title><defs></defs><path d="M61,28.5v-16A5.51,5.51,0,0,0,55.5,7H7.5A5.51,5.51,0,0,0,2,12.5v16a5.46,5.46,0,0,0,1.74,4A5.46,5.46,0,0,0,2,36.5v16A5.51,5.51,0,0,0,7.5,58h48A5.51,5.51,0,0,0,61,52.5v-16a5.46,5.46,0,0,0-1.74-4A5.46,5.46,0,0,0,61,28.5Zm-3,8v16A2.5,2.5,0,0,1,55.5,55H7.5A2.5,2.5,0,0,1,5,52.5v-16A2.5,2.5,0,0,1,7.5,34h48A2.5,2.5,0,0,1,58,36.5ZM7.5,31A2.5,2.5,0,0,1,5,28.5v-16A2.5,2.5,0,0,1,7.5,10h48A2.5,2.5,0,0,1,58,12.5v16A2.5,2.5,0,0,1,55.5,31ZM39,20.5A1.5,1.5,0,0,1,37.5,22h-24a1.5,1.5,0,0,1,0-3h24A1.5,1.5,0,0,1,39,20.5Zm-27,24A1.5,1.5,0,0,1,13.5,43h24a1.5,1.5,0,0,1,0,3h-24A1.5,1.5,0,0,1,12,44.5Z"></path><circle class="cls-1" style="fill:#62d84e;;" cx="49.5" cy="20.5" r="3.5"></circle><circle class="cls-1" style="fill:#62d84e;;" cx="49.5" cy="44.5" r="3.5"></circle><rect class="cls-2" style="fill:none;;" width="64" height="64"></rect></svg>
<span class="ph">Build and monitor your physical, logical networks, and provisioned services.</span></a></p>
</td>
<td class="entry">
<p class="p"><a data-bundleid="zurich-telecom-media-technology" data-navpath="product/industry-products/concept//csh" href="https://servicenow-be-prod.servicenow.com/csh?topicname=telecommunications-service-operations-management&version=zurich&pubname=zurich-telecom-service-ops" class="xref"><span class="ph nav-card-title">Telecommunications Service Operations Management</span><svg class="image svg decorative" id="telecom-media-tech-landing__image_f5y_wlp_fyb" viewBox="0 0 64 64" title="" width="64" height="64"><title></title><defs></defs><path class="cls-1" style="fill:#62d84e;;" d="M21.5,11A4.49,4.49,0,0,0,20,19.72V35.5a1.5,1.5,0,0,0,3,0V19.72A4.49,4.49,0,0,0,21.5,11Z"></path><path class="cls-1" style="fill:#62d84e;;" d="M31.5,17A4.49,4.49,0,0,0,30,25.72V35.5a1.5,1.5,0,0,0,3,0V25.72A4.49,4.49,0,0,0,31.5,17Z"></path><path class="cls-1" style="fill:#62d84e;;" d="M46,9.5a4.5,4.5,0,1,0-6,4.22V35.5a1.5,1.5,0,0,0,3,0V13.72A4.49,4.49,0,0,0,46,9.5Z"></path><path d="M40,47a2,2,0,0,1-2,2H14a2,2,0,0,1,0-4H38A2,2,0,0,1,40,47Zm9-4a4,4,0,1,0,4,4A4,4,0,0,0,49,43Zm11-4.59V55.57A4.43,4.43,0,0,1,55.57,60H7.41A4.4,4.4,0,0,1,3,55.59V38.41A4.4,4.4,0,0,1,7.41,34H55.59A4.4,4.4,0,0,1,60,38.41Zm-3,0A1.41,1.41,0,0,0,55.59,37H7.41A1.41,1.41,0,0,0,6,38.41V55.59A1.41,1.41,0,0,0,7.41,57H55.59A1.41,1.41,0,0,0,57,55.59Z"></path><rect class="cls-2" style="fill:none;;" width="64" height="64"></rect></svg>
<span class="ph">Proactively monitor the health of your networks and services to prevent downtime.</span></a></p>
</td>
</tr>
<tr class="row">
<td class="entry">
<p class="p"><a data-bundleid="zurich-telecom-media-technology" data-navpath="product/tmt-spmc/reference/now-assist-spmc.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-media-technology/page/product/tmt-spmc/reference/now-assist-spmc.html" class="xref" title="Use the ServiceNow Now Assist for Telecommunications, Media and Technology (TMT) application to summarize service problem cases, account onboarding cases, engagements, touchpoints, generate the case resolution notes, and summarize tests. You can enable your agents to understand the case context and test results so that they can propose quicker resolutions to your customers. Additionally, you can automate transformation mapping between provider and consumer instances in Service Bridge."><span class="ph">Now Assist for Telecommunications, Media, and Technology</span><svg class="image svg decorative" id="telecom-media-tech-landing__image_eb4_b4j_b2c" viewBox="0 0 64 64" title="" width="64" height="64"><title></title><defs></defs><path class="cls-1" style="fill:#62d84e;;" d="M53,39.5C53,45.3,45.39,50,36,50c-5.36,0-10.12-1.53-13.22-3.91a7.17,7.17,0,0,0,2.59-5.54,7.34,7.34,0,0,0-3.91-6.47C24.41,31,29.81,29,36,29,45.39,29,53,33.7,53,39.5Z"></path><path class="cls-2" style="fill:none;;stroke:#000;stroke-linecap:round;stroke-width:3px;;stroke-linejoin:round;;" d="M28.51,13.5l5.16,10.16a13.42,13.42,0,0,1,9.84-4.16c7.18,0,13,5.38,13,12"></path><circle class="cls-3" style="fill:none;;stroke:#000;stroke-linecap:round;stroke-width:3px;;stroke-miterlimit:10;;" cx="47.52" cy="12.5" r="7"></circle><path class="cls-3" style="fill:none;;stroke:#000;stroke-linecap:round;stroke-width:3px;;stroke-miterlimit:10;;" d="M31.51,59.5c0-6.63-5.82-12-13-12s-13,5.37-13,12"></path><circle class="cls-3" style="fill:none;;stroke:#000;stroke-linecap:round;stroke-width:3px;;stroke-miterlimit:10;;" cx="18.51" cy="40.5" r="7"></circle><rect class="cls-4" style="fill:none;;" width="64" height="64"></rect></svg><span class="ph">Helps to summarize service problem cases, generate the case resolution notes, and summarize tests.</span></a></p>
</td>
<td class="entry">
<p class="p"><a data-bundleid="zurich-telecom-media-technology" data-navpath="product/tmt-spmt/concept/spmt-overview.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-media-technology/page/product/tmt-spmt/concept/spmt-overview.html" class="xref" title="The Strategic Portfolio Management for Telecom is a product that inherits all features of Strategic Portfolio Management along with the addition of two templates for Fiber Rollout and 5G Projects."><span class="ph">Strategic Portfolio Management for Telecommunications</span><svg class="image svg decorative" id="telecom-media-tech-landing__image_y4g_f4j_b2c" viewBox="0 0 64 64" title="" width="64" height="64"><title></title><defs></defs><path d="M62.31,5.23a1.51,1.51,0,0,0-1.44-.09L31.5,18.84,2.13,5.14a1.51,1.51,0,0,0-1.44.09A1.52,1.52,0,0,0,0,6.5v38a1.51,1.51,0,0,0,.87,1.36l30,14a1.49,1.49,0,0,0,1.26,0l30-14A1.51,1.51,0,0,0,63,44.5V6.5A1.52,1.52,0,0,0,62.31,5.23ZM3,8.86l27,12.6V56.14L3,43.54ZM60,43.54,33,56.14V21.46L60,8.86Z"></path><path d="M40.05,28.93a1.56,1.56,0,0,0,.63-.14l10.4-4.86a1.5,1.5,0,0,0-1.27-2.72l-10.4,4.86a1.5,1.5,0,0,0,.64,2.86Z"></path><path d="M22.53,42.07l-10.4-4.86a1.5,1.5,0,0,0-1.26,2.72l10.39,4.86a1.61,1.61,0,0,0,.64.14,1.5,1.5,0,0,0,.63-2.86Z"></path><path d="M38.69,36.06a1.49,1.49,0,0,0,1.36.87,1.56,1.56,0,0,0,.63-.14l12.86-6a1.5,1.5,0,0,0-1.27-2.72l-12.86,6A1.49,1.49,0,0,0,38.69,36.06Z"></path><path d="M49.61,37.31l-10.2,4.76a1.5,1.5,0,0,0,.64,2.86,1.56,1.56,0,0,0,.63-.14L50.88,40a1.5,1.5,0,0,0-1.27-2.72Z"></path><path class="cls-1" style="fill:#62d84e;;" d="M9.33,31a2.09,2.09,0,0,1-1.22-2C8.5,18.41,13,14.55,15.3,23.46s8.82-5.25,9.55,10.8a1.94,1.94,0,0,1-2.52,2.11Z"></path><rect class="cls-2" style="fill:none;;" width="64" height="64"></rect></svg><span class="ph">Define and customize the tasks and requirements for your Fiber Rollout and 5G projects.</span></a></p>
</td>
<td class="entry">
<p class="p"><a data-bundleid="zurich-telecom-media-technology" data-navpath="product/tmt-field-service-management/concept/field-service-management-telecommunications.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-media-technology/page/product/tmt-field-service-management/concept/field-service-management-telecommunications.html" class="xref" title="The ServiceNow Field Service Management for Telecommunications (FSMT) application enables you to manage the field service workflow for the telecommunications customers. Use this application to streamline the appointment booking, service delivery, and assurance processes."><span class="ph">Field Service Management for Telecommunications</span><svg class="image svg decorative" id="telecom-media-tech-landing__image_wml_h4j_b2c" viewBox="0 0 64 64" title="" width="64" height="64"><title></title><defs></defs><rect class="cls-1" style="fill:none;;" width="64" height="64"></rect><polyline class="cls-2" style="fill:none;;stroke:#000;stroke-linecap:round;stroke-linejoin:round;stroke-width:2px;;" points="17.07 30.13 4 30.13 11.47 37.6 52.53 37.6 60 30.13 46.93 30.13"></polyline><path class="cls-2" style="fill:none;;stroke:#000;stroke-linecap:round;stroke-linejoin:round;stroke-width:2px;;" d="M36.33,5.37a21.48,21.48,0,0,1,17.14,21v3.73"></path><path class="cls-2" style="fill:none;;stroke:#000;stroke-linecap:round;stroke-linejoin:round;stroke-width:2px;;" d="M10.53,30.13V26.4A21.48,21.48,0,0,1,27.8,5.34"></path><path class="cls-2" style="fill:none;;stroke:#000;stroke-linecap:round;stroke-linejoin:round;stroke-width:2px;;" d="M38.53,13.33V9.6S37.6,4,32,4s-6.53,5.6-6.53,5.6v3.73"></path><path class="cls-3" style="fill:#62d84e;;" d="M41.33,28.27a9.33,9.33,0,1,0-18.66,0Z"></path><path class="cls-2" style="fill:none;;stroke:#000;stroke-linecap:round;stroke-linejoin:round;stroke-width:2px;;" d="M50.67,41.33a18.67,18.67,0,0,1-37.34,0V37.6H50.67Z"></path></svg><span class="ph">Manage the field service workflow for the telecommunication industry customers.</span></a></p>
</td>
</tr>
</tbody></table></div>
</section>
</div>
</article></main></body></article> | {
"attachments": {
"all_attachments": null,
"topic_attachments": []
},
"available_languages": [
"enus"
],
"breadcrumbs": [],
"breadcrumbs_html": "<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-media-technology\">Zurich Telecommunications, Media, and Technology</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<span class=\"active\">Telecommunications, Media, and Technology (TMT)</span>",
"bundle_id": "zurich-telecom-media-technology",
"bundle_key": 2724,
"bundle_landing_page": "product/industry-products/concept/telecom-media-tech-landing.html",
"bundle_subtitle": null,
"bundle_title": "Zurich Telecommunications, Media, and Technology",
"canonical_link": null,
"dates": {
"Added on": "2025-08-02T00:46:16.994385Z",
"Created on": "2023-02-02T00:00:00Z",
"Initial upload": "2025-07-30T22:20:16.545452Z",
"Updated on": "2025-07-31T00:00:00Z"
},
"dislike_url": "https://servicenow-be-prod.servicenow.com/dislike/55677611",
"dislikes": 0,
"es_archived_content": false,
"is_in_fav": false,
"is_liked": null,
"is_watched": false,
"keywords": [
" zurich zurich"
],
"labels": [
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "zurich",
"navtitle": "Zurich",
"outputclasses": [],
"subjectHeadId": "versions",
"subjectheadNavtitle": "Versions",
"visibility": "show-facet"
},
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "telmt",
"navtitle": "Telecommunications Media and Technology Assurance",
"outputclasses": [],
"subjectHeadId": "products",
"subjectheadNavtitle": "Products",
"visibility": "show-facet"
}
],
"labels_text": "Versions > Zurich; Products > CRM and Industry Products > Telecommunications Media and Technology Assurance",
"like_url": "https://servicenow-be-prod.servicenow.com/like/55677611",
"likes": 0,
"metadata": {
"AI Search": null,
"AI Search Assist": null,
"Application Insights": null,
"Capabilities": null,
"Code Signing": null,
"Contextual Search": null,
"DC.contributor": null,
"DC.coverage": null,
"DC.creator": "ServiceNow",
"DC.date.created": "2023-02-02",
"DC.date.modified": "2025-07-31",
"DC.format": "HTML5",
"DC.identifier": "telecom-media-tech-landing",
"DC.language": null,
"DC.relation": null,
"DC.rights.owner": "(C) Copyright 2025",
"DC.subject": null,
"DC.type": "concept",
"Data Discovery": null,
"Data Policy": null,
"Data Privacy": null,
"Discovery": null,
"External Content for AI Search": null,
"Field Administration": null,
"Field Normalization": null,
"Key Management Framework": null,
"Localization Framework": null,
"Now Platform": null,
"PlatSec": null,
"Platform": null,
"Platform Administration": null,
"Platform Performance": null,
"Platform Privacy": null,
"Proactive Triggers": null,
"Process Optimization": null,
"RN doc editing record number": null,
"Search Administration": null,
"Secrets Management": null,
"ServiceNow AI Platform": null,
"State Model": null,
"Subscription Management": null,
"Task Communications Management": null,
"Timeline Visualizations": null,
"User Administration": null,
"User Experience Analytics": null,
"Zing": null,
"ai-now-assist": null,
"app-name": null,
"app_route": null,
"azureapimanagemen": null,
"change-completed": null,
"change-item": null,
"change-request-id": null,
"change-request-reference": null,
"com.glide.embedded_help.category": null,
"component": null,
"copyright": "(C) Copyright 2025",
"crossroads": null,
"data": null,
"description": "The ServiceNow® Telecommunications, Media, and Technology (TMT) product suite brings together customer care, operations, order management, and partner ecosystems so that service providers can scale their business to capitalize on the fast-growing “everything-as-a-service\" opportunity.",
"dominant_bundle": null,
"erp-canvas-video": null,
"fsm-mobile": null,
"fsm-route": null,
"fsm-sched-opt": null,
"fsm-wrk-order": null,
"genai-round-7": null,
"generator": "DITA-OT",
"glossPartOfSpeech": null,
"glossStatus": null,
"guided setup": null,
"guided tours": null,
"keywords": null,
"min-toc": null,
"mini": null,
"mini-to truec": null,
"mini-toc": "yes",
"mini_toc": null,
"minitoc": null,
"modification": null,
"now-assist-app-gen-video": null,
"order": null,
"page-type": null,
"page-type ": null,
"prodname": null,
"product": null,
"product_name": null,
"release": null,
"resourceID": null,
"roles": null,
"route_page": null,
"route_params_listId": null,
"route_params_table": null,
"route_params_type": null,
"route_type": null,
"setconfigurationproperties": null,
"topic": null,
"translation-type": "source",
"version": null,
"workflow": "Customer and Industry",
"workplace-srvc-delvry-ditamap": null
},
"page_id": "product/industry-products/concept/telecom-media-tech-landing.html",
"page_key": 55677611,
"preprocessed_PDF": "https://downloads.docs.servicenow.com/pdf/enus/servicenow-zurich-telecom-media-technology-enus.pdf",
"rating": null,
"read_time_data": {
"char_count": 1420,
"img_count": 0,
"read_time": 1,
"video_links": [
""
],
"word_count": 175
},
"related_links": [],
"search_title": null,
"title": "Telecommunications, Media, and Technology (TMT)",
"topic_cluster": {
"clustered_by": {
"enabled": true,
"primary_key": "versions",
"primary_sort": "top-down",
"type": "subjecthead"
},
"clustered_labels": [
"versions"
],
"clustered_topics": [
{
"bundle_id": "yokohama-telecom-media-technology",
"clustering_title": "Yokohama",
"es_archived_content": false,
"page_id": "product/industry-products/concept/telecom-media-tech-landing.html"
},
{
"bundle_id": "xanadu-telecom-media-technology",
"clustering_title": "Xanadu",
"es_archived_content": false,
"page_id": "product/industry-products/concept/telecom-media-tech-landing.html"
},
{
"bundle_id": "washingtondc-telecom-media-technology",
"clustering_title": "Washington DC",
"es_archived_content": false,
"page_id": "product/industry-products/concept/telecom-media-tech-landing.html"
},
{
"bundle_id": "vancouver-telecom-media-technology",
"clustering_title": "Vancouver",
"es_archived_content": false,
"page_id": "product/industry-products/concept/telecom-media-tech-landing.html"
}
],
"clustering_title": "Zurich"
},
"topic_html": "<article class=\"hascomments\" data-page=\"bundle:zurich-telecom-media-technology/enus/product/industry-products/concept/telecom-media-tech-landing.html\" id=\"bundle:zurich-telecom-media-technology/enus/product/industry-products/concept/telecom-media-tech-landing.html\"><body id=\"telecom-media-tech-landing\"><main role=\"main\"><article role=\"article\" class=\"dita\" id=\"telecom-media-tech-landing\" aria-labelledby=\"title_telecom-media-tech-landing\">\n <h1 class=\"title topictitle1\" id=\"title_telecom-media-tech-landing\">Telecommunications, Media, and Technology (TMT)</h1>\n \n \n <div class=\"body conbody\"><p class=\"shortdesc\">The <span class=\"ph\">ServiceNow®</span> Telecommunications, Media, and Technology (TMT) product suite brings together customer care, operations, order management, and partner ecosystems so that service providers can scale their business to\n capitalize on the fast-growing “everything-as-a-service" opportunity.</p>\n <section class=\"section\" id=\"telecom-media-tech-landing__section_olz_s1v_j5b\">\n <div class=\"table-wrap\"><table count-columns=\"3\" class=\"table nav-card frame-none\" id=\"telecom-media-tech-landing__table_cry_rvq_pvb\" role=\"presentation\"><caption></caption><colgroup><col style=\"width:33.33333333333333%\"/><col style=\"width:33.33333333333333%\"/><col style=\"width:33.33333333333333%\"/></colgroup><tbody class=\"tbody\">\n <tr class=\"row\">\n <td class=\"entry\">\n <p class=\"p\"><a data-bundleid=\"zurich-telecom-media-technology\" data-navpath=\"product/industry-products/concept//csh\" href=\"https://servicenow-be-prod.servicenow.com/csh?topicname=account-lifecycle-events-landing&version=zurich&pubname=zurich-acct-lifecycle-events\" class=\"xref\"><span class=\"ph nav-card-title\">Customer Success Management</span>\n <svg class=\"image svg decorative\" id=\"telecom-media-tech-landing__image_o4b_dqp_fyb\" viewBox=\"0 0 64 64\" title=\"\" width=\"64\" height=\"64\"><title></title><defs></defs><rect class=\"cls-1\" style=\"fill:#62d84e;;\" x=\"27\" y=\"28\" width=\"9\" height=\"9\" rx=\"2\"></rect><rect class=\"cls-1\" style=\"fill:#62d84e;;\" x=\"14\" y=\"28\" width=\"9\" height=\"9\" rx=\"2\"></rect><rect class=\"cls-1\" style=\"fill:#62d84e;;\" x=\"40\" y=\"28\" width=\"9\" height=\"9\" rx=\"2\"></rect><path d=\"M54.5,5H47V4.5a1.5,1.5,0,0,0-3,0V5H19V4.5a1.5,1.5,0,0,0-3,0V5H8.5A4.51,4.51,0,0,0,4,9.5v46A4.51,4.51,0,0,0,8.5,60h46A4.51,4.51,0,0,0,59,55.5V9.5A4.51,4.51,0,0,0,54.5,5ZM8.5,8H16v2.5a1.5,1.5,0,0,0,3,0V8H44v2.5a1.5,1.5,0,0,0,3,0V8h7.5A1.5,1.5,0,0,1,56,9.5V17H7V9.5A1.5,1.5,0,0,1,8.5,8Zm46,49H8.5A1.5,1.5,0,0,1,7,55.5V20H56V55.5A1.5,1.5,0,0,1,54.5,57Z\"></path><rect class=\"cls-2\" style=\"fill:none;;\" width=\"64\" height=\"64\"></rect></svg>\n <span class=\"ph\">Streamline, automate, and measure critical workflows across the enterprise.</span></a></p>\n </td>\n <td class=\"entry\">\n <p class=\"p\"><a data-bundleid=\"zurich-telecom-media-technology\" data-navpath=\"product/industry-products/concept//csh\" href=\"https://servicenow-be-prod.servicenow.com/csh?topicname=order-mgt-overview&version=zurich&pubname=zurich-order-management\" class=\"xref\"><span class=\"ph nav-card-title\">Sales and Order Management</span><svg class=\"image svg decorative\" id=\"telecom-media-tech-landing__image_bbz_dr1_gyb\" viewBox=\"0 0 64 64\" title=\"\" width=\"64\" height=\"64\"><title></title><defs></defs><path class=\"cls-1\" style=\"fill:#62d84e;;\" d=\"M28.1,30.53A4.53,4.53,0,1,1,23.57,26a4.53,4.53,0,0,1,4.53,4.53Zm2.73,13.59c.91,0,1.64-.68,1.47-1.42-.8-3.41-4.4-6-8.73-6s-7.94,2.58-8.74,6c-.17.74.56,1.42,1.47,1.42Z\"></path><path d=\"M48.07,35.38h-15a1.12,1.12,0,0,0,0,2.24h15a1.12,1.12,0,0,0,0-2.24Z\"></path><path d=\"M48.07,29.38h-15a1.12,1.12,0,0,0,0,2.24h15a1.12,1.12,0,0,0,0-2.24Z\"></path><path d=\"M48.07,23.38h-15a1.12,1.12,0,0,0,0,2.24h15a1.12,1.12,0,0,0,0-2.24Z\"></path><path d=\"M48.07,41.38h-12a1.12,1.12,0,0,0,0,2.24h12a1.12,1.12,0,0,0,0-2.24Z\"></path><path d=\"M52.22,51H11.78A3.28,3.28,0,0,1,8.5,47.72V19.28A3.28,3.28,0,0,1,11.78,16H52.22a3.28,3.28,0,0,1,3.28,3.28V47.72A3.28,3.28,0,0,1,52.22,51ZM11.78,18a1.28,1.28,0,0,0-1.28,1.28h0V47.72A1.28,1.28,0,0,0,11.78,49H52.22a1.28,1.28,0,0,0,1.28-1.28V19.28A1.28,1.28,0,0,0,52.22,18Z\"></path><rect class=\"cls-2\" style=\"fill:none;;\" width=\"64\" height=\"64\"></rect></svg><span class=\"ph\">Capture, manage, and fulfill customer and external service orders. </span></a></p>\n </td>\n \n <td class=\"entry\">\n <p class=\"p\"><a data-bundleid=\"zurich-telecom-media-technology\" data-navpath=\"product/industry-products/concept//csh\" href=\"https://servicenow-be-prod.servicenow.com/csh?topicname=assurance-workflows&version=zurich&pubname=zurich-proactive-service-exp-workflows\" class=\"xref\"><span class=\"ph nav-card-title\">Proactive Service Experience Workflows</span><svg class=\"image svg decorative\" id=\"telecom-media-tech-landing__image_hxs_xqp_fyb\" viewBox=\"0 0 64 64\" title=\"\" width=\"64\" height=\"64\"><title></title><defs></defs><path d=\"M12.5,23A7.5,7.5,0,1,1,20,15.5,7.5,7.5,0,0,1,12.5,23Zm0-12A4.5,4.5,0,1,0,17,15.5,4.51,4.51,0,0,0,12.5,11Zm36,48A7.5,7.5,0,1,1,56,51.5,7.5,7.5,0,0,1,48.5,59Zm0-12A4.5,4.5,0,1,0,53,51.5,4.51,4.51,0,0,0,48.5,47Zm0-22a1.51,1.51,0,0,1-1.06-.44l-8-8a1.49,1.49,0,0,1,0-2.12l8-8a1.49,1.49,0,0,1,2.12,0l8,8a1.49,1.49,0,0,1,0,2.12l-8,8A1.51,1.51,0,0,1,48.5,25Zm-5.88-9.5,5.88,5.88,5.88-5.88L48.5,9.62Z\"></path><path class=\"cls-1\" style=\"fill:#62d84e;;\" d=\"M29.44,18.44a1.49,1.49,0,0,0,0,2.12,1.5,1.5,0,0,0,2.12,0l4-4a1.49,1.49,0,0,0,0-2.12l-4-4a1.5,1.5,0,0,0-2.12,2.12L30.88,14H24.5a1.5,1.5,0,0,0,0,3h6.38Z\"></path><path class=\"cls-1\" style=\"fill:#62d84e;;\" d=\"M36.5,50H30.12l1.44-1.44a1.5,1.5,0,0,0-2.12-2.12l-4,4a1.49,1.49,0,0,0,0,2.12l4,4a1.5,1.5,0,0,0,2.12,0,1.49,1.49,0,0,0,0-2.12L30.12,53H36.5a1.5,1.5,0,0,0,0-3Z\"></path><path class=\"cls-1\" style=\"fill:#62d84e;;\" d=\"M53.56,33.44a1.49,1.49,0,0,0-2.12,0L50,34.88V29.5a1.5,1.5,0,0,0-3,0v5.38l-1.44-1.44a1.5,1.5,0,0,0-2.12,2.12l4,4a1.5,1.5,0,0,0,2.12,0l4-4A1.49,1.49,0,0,0,53.56,33.44Z\"></path><rect class=\"cls-1\" style=\"fill:#62d84e;;\" x=\"5\" y=\"44\" width=\"15\" height=\"15\" rx=\"1.5\"></rect><rect class=\"cls-2\" style=\"fill:none;;\" width=\"64\" height=\"64\"></rect></svg>\n <span class=\"ph\">Deliver end-to-end workflows to resolve network related incidents, and proactively notify impacted customers.</span></a></p>\n </td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry\">\n <p class=\"p\"><a data-bundleid=\"zurich-telecom-media-technology\" data-navpath=\"product/industry-products/concept//csh\" href=\"https://servicenow-be-prod.servicenow.com/csh?topicname=tmt-service-bridge-both-landing-page&version=zurich&pubname=zurich-service-bridge\" class=\"xref\"><span class=\"ph nav-card-title\">Service Bridge</span>\n <svg class=\"image svg decorative\" id=\"telecom-media-tech-landing__image_lg5_bmj_b2c\" viewBox=\"0 0 64 64\" title=\"\" width=\"64\" height=\"64\"><title></title><defs></defs><path d=\"M53.76,39.66a1.5,1.5,0,0,1-.84-2.74L58.8,33,35.63,17.56a1.5,1.5,0,0,1,1.66-2.5l25,16.69a1.5,1.5,0,0,1,0,2.5l-7.74,5.16A1.52,1.52,0,0,1,53.76,39.66Z\"></path><path d=\"M27.17,51.62a1.53,1.53,0,0,1-.83-.26L.67,34.25a1.5,1.5,0,0,1,0-2.5l8-5.31a1.5,1.5,0,1,1,1.66,2.5L4.2,33,28,48.87a1.5,1.5,0,0,1-.83,2.75Z\"></path><path class=\"cls-1\" style=\"fill:#62d84e;;\" d=\"M14.77,24.71A.85.85,0,0,1,14,23.5l5.35-11.74a.84.84,0,0,1,1.48-.1l2.91,4.58,2.82-1.93A3.32,3.32,0,0,0,28,11.58V4.51a1.5,1.5,0,1,1,3,0v7.66a5.21,5.21,0,0,1-2.28,4.31l-3.37,2.31,2.46,3.89A.85.85,0,0,1,27.15,24Z\"></path><path class=\"cls-1\" style=\"fill:#62d84e;;\" d=\"M33.5,62.08a1.5,1.5,0,0,1-1.5-1.5v-6a8.14,8.14,0,0,1,3.57-6.75l2.08-1.42-2.46-3.87a.82.82,0,0,1,0-.84.83.83,0,0,1,.7-.46l12.33-.71a.88.88,0,0,1,.76.39.84.84,0,0,1,.06.81L43.65,53.37a.82.82,0,0,1-.77.5h0a.84.84,0,0,1-.71-.4l-2.91-4.55-2,1.36A5.15,5.15,0,0,0,35,54.55v6A1.5,1.5,0,0,1,33.5,62.08Z\"></path><rect class=\"cls-2\" style=\"fill:none;;\" width=\"64\" height=\"64\"></rect></svg><span class=\"ph\">Help customers and providers connect and track service requests directly between their instances.</span></a></p>\n </td>\n <td class=\"entry\">\n <p class=\"p\"><a data-bundleid=\"zurich-telecom-media-technology\" data-navpath=\"product/industry-products/concept//csh\" href=\"https://servicenow-be-prod.servicenow.com/csh?topicname=telecom-network-inventory&version=zurich&pubname=zurich-telecom-network-inventory\" class=\"xref\"><span class=\"ph nav-card-title\">Telecommunications Network Inventory</span>\n <svg class=\"image svg decorative\" id=\"telecom-media-tech-landing__image_ll5_kmp_fyb\" viewBox=\"0 0 64 64\" title=\"\" width=\"64\" height=\"64\"><title></title><defs></defs><path d=\"M61,28.5v-16A5.51,5.51,0,0,0,55.5,7H7.5A5.51,5.51,0,0,0,2,12.5v16a5.46,5.46,0,0,0,1.74,4A5.46,5.46,0,0,0,2,36.5v16A5.51,5.51,0,0,0,7.5,58h48A5.51,5.51,0,0,0,61,52.5v-16a5.46,5.46,0,0,0-1.74-4A5.46,5.46,0,0,0,61,28.5Zm-3,8v16A2.5,2.5,0,0,1,55.5,55H7.5A2.5,2.5,0,0,1,5,52.5v-16A2.5,2.5,0,0,1,7.5,34h48A2.5,2.5,0,0,1,58,36.5ZM7.5,31A2.5,2.5,0,0,1,5,28.5v-16A2.5,2.5,0,0,1,7.5,10h48A2.5,2.5,0,0,1,58,12.5v16A2.5,2.5,0,0,1,55.5,31ZM39,20.5A1.5,1.5,0,0,1,37.5,22h-24a1.5,1.5,0,0,1,0-3h24A1.5,1.5,0,0,1,39,20.5Zm-27,24A1.5,1.5,0,0,1,13.5,43h24a1.5,1.5,0,0,1,0,3h-24A1.5,1.5,0,0,1,12,44.5Z\"></path><circle class=\"cls-1\" style=\"fill:#62d84e;;\" cx=\"49.5\" cy=\"20.5\" r=\"3.5\"></circle><circle class=\"cls-1\" style=\"fill:#62d84e;;\" cx=\"49.5\" cy=\"44.5\" r=\"3.5\"></circle><rect class=\"cls-2\" style=\"fill:none;;\" width=\"64\" height=\"64\"></rect></svg>\n <span class=\"ph\">Build and monitor your physical, logical networks, and provisioned services.</span></a></p>\n </td>\n <td class=\"entry\">\n <p class=\"p\"><a data-bundleid=\"zurich-telecom-media-technology\" data-navpath=\"product/industry-products/concept//csh\" href=\"https://servicenow-be-prod.servicenow.com/csh?topicname=telecommunications-service-operations-management&version=zurich&pubname=zurich-telecom-service-ops\" class=\"xref\"><span class=\"ph nav-card-title\">Telecommunications Service Operations Management</span><svg class=\"image svg decorative\" id=\"telecom-media-tech-landing__image_f5y_wlp_fyb\" viewBox=\"0 0 64 64\" title=\"\" width=\"64\" height=\"64\"><title></title><defs></defs><path class=\"cls-1\" style=\"fill:#62d84e;;\" d=\"M21.5,11A4.49,4.49,0,0,0,20,19.72V35.5a1.5,1.5,0,0,0,3,0V19.72A4.49,4.49,0,0,0,21.5,11Z\"></path><path class=\"cls-1\" style=\"fill:#62d84e;;\" d=\"M31.5,17A4.49,4.49,0,0,0,30,25.72V35.5a1.5,1.5,0,0,0,3,0V25.72A4.49,4.49,0,0,0,31.5,17Z\"></path><path class=\"cls-1\" style=\"fill:#62d84e;;\" d=\"M46,9.5a4.5,4.5,0,1,0-6,4.22V35.5a1.5,1.5,0,0,0,3,0V13.72A4.49,4.49,0,0,0,46,9.5Z\"></path><path d=\"M40,47a2,2,0,0,1-2,2H14a2,2,0,0,1,0-4H38A2,2,0,0,1,40,47Zm9-4a4,4,0,1,0,4,4A4,4,0,0,0,49,43Zm11-4.59V55.57A4.43,4.43,0,0,1,55.57,60H7.41A4.4,4.4,0,0,1,3,55.59V38.41A4.4,4.4,0,0,1,7.41,34H55.59A4.4,4.4,0,0,1,60,38.41Zm-3,0A1.41,1.41,0,0,0,55.59,37H7.41A1.41,1.41,0,0,0,6,38.41V55.59A1.41,1.41,0,0,0,7.41,57H55.59A1.41,1.41,0,0,0,57,55.59Z\"></path><rect class=\"cls-2\" style=\"fill:none;;\" width=\"64\" height=\"64\"></rect></svg>\n <span class=\"ph\">Proactively monitor the health of your networks and services to prevent downtime.</span></a></p>\n </td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry\">\n <p class=\"p\"><a data-bundleid=\"zurich-telecom-media-technology\" data-navpath=\"product/tmt-spmc/reference/now-assist-spmc.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-media-technology/page/product/tmt-spmc/reference/now-assist-spmc.html\" class=\"xref\" title=\"Use the ServiceNow Now Assist for Telecommunications, Media and Technology (TMT) application to summarize service problem cases, account onboarding cases, engagements, touchpoints, generate the case resolution notes, and summarize tests. You can enable your agents to understand the case context and test results so that they can propose quicker resolutions to your customers. Additionally, you can automate transformation mapping between provider and consumer instances in Service Bridge.\"><span class=\"ph\">Now Assist for Telecommunications, Media, and Technology</span><svg class=\"image svg decorative\" id=\"telecom-media-tech-landing__image_eb4_b4j_b2c\" viewBox=\"0 0 64 64\" title=\"\" width=\"64\" height=\"64\"><title></title><defs></defs><path class=\"cls-1\" style=\"fill:#62d84e;;\" d=\"M53,39.5C53,45.3,45.39,50,36,50c-5.36,0-10.12-1.53-13.22-3.91a7.17,7.17,0,0,0,2.59-5.54,7.34,7.34,0,0,0-3.91-6.47C24.41,31,29.81,29,36,29,45.39,29,53,33.7,53,39.5Z\"></path><path class=\"cls-2\" style=\"fill:none;;stroke:#000;stroke-linecap:round;stroke-width:3px;;stroke-linejoin:round;;\" d=\"M28.51,13.5l5.16,10.16a13.42,13.42,0,0,1,9.84-4.16c7.18,0,13,5.38,13,12\"></path><circle class=\"cls-3\" style=\"fill:none;;stroke:#000;stroke-linecap:round;stroke-width:3px;;stroke-miterlimit:10;;\" cx=\"47.52\" cy=\"12.5\" r=\"7\"></circle><path class=\"cls-3\" style=\"fill:none;;stroke:#000;stroke-linecap:round;stroke-width:3px;;stroke-miterlimit:10;;\" d=\"M31.51,59.5c0-6.63-5.82-12-13-12s-13,5.37-13,12\"></path><circle class=\"cls-3\" style=\"fill:none;;stroke:#000;stroke-linecap:round;stroke-width:3px;;stroke-miterlimit:10;;\" cx=\"18.51\" cy=\"40.5\" r=\"7\"></circle><rect class=\"cls-4\" style=\"fill:none;;\" width=\"64\" height=\"64\"></rect></svg><span class=\"ph\">Helps to summarize service problem cases, generate the case resolution notes, and summarize tests.</span></a></p>\n </td>\n <td class=\"entry\">\n <p class=\"p\"><a data-bundleid=\"zurich-telecom-media-technology\" data-navpath=\"product/tmt-spmt/concept/spmt-overview.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-media-technology/page/product/tmt-spmt/concept/spmt-overview.html\" class=\"xref\" title=\"The Strategic Portfolio Management for Telecom is a product that inherits all features of Strategic Portfolio Management along with the addition of two templates for Fiber Rollout and 5G Projects.\"><span class=\"ph\">Strategic Portfolio Management for Telecommunications</span><svg class=\"image svg decorative\" id=\"telecom-media-tech-landing__image_y4g_f4j_b2c\" viewBox=\"0 0 64 64\" title=\"\" width=\"64\" height=\"64\"><title></title><defs></defs><path d=\"M62.31,5.23a1.51,1.51,0,0,0-1.44-.09L31.5,18.84,2.13,5.14a1.51,1.51,0,0,0-1.44.09A1.52,1.52,0,0,0,0,6.5v38a1.51,1.51,0,0,0,.87,1.36l30,14a1.49,1.49,0,0,0,1.26,0l30-14A1.51,1.51,0,0,0,63,44.5V6.5A1.52,1.52,0,0,0,62.31,5.23ZM3,8.86l27,12.6V56.14L3,43.54ZM60,43.54,33,56.14V21.46L60,8.86Z\"></path><path d=\"M40.05,28.93a1.56,1.56,0,0,0,.63-.14l10.4-4.86a1.5,1.5,0,0,0-1.27-2.72l-10.4,4.86a1.5,1.5,0,0,0,.64,2.86Z\"></path><path d=\"M22.53,42.07l-10.4-4.86a1.5,1.5,0,0,0-1.26,2.72l10.39,4.86a1.61,1.61,0,0,0,.64.14,1.5,1.5,0,0,0,.63-2.86Z\"></path><path d=\"M38.69,36.06a1.49,1.49,0,0,0,1.36.87,1.56,1.56,0,0,0,.63-.14l12.86-6a1.5,1.5,0,0,0-1.27-2.72l-12.86,6A1.49,1.49,0,0,0,38.69,36.06Z\"></path><path d=\"M49.61,37.31l-10.2,4.76a1.5,1.5,0,0,0,.64,2.86,1.56,1.56,0,0,0,.63-.14L50.88,40a1.5,1.5,0,0,0-1.27-2.72Z\"></path><path class=\"cls-1\" style=\"fill:#62d84e;;\" d=\"M9.33,31a2.09,2.09,0,0,1-1.22-2C8.5,18.41,13,14.55,15.3,23.46s8.82-5.25,9.55,10.8a1.94,1.94,0,0,1-2.52,2.11Z\"></path><rect class=\"cls-2\" style=\"fill:none;;\" width=\"64\" height=\"64\"></rect></svg><span class=\"ph\">Define and customize the tasks and requirements for your Fiber Rollout and 5G projects.</span></a></p>\n </td>\n <td class=\"entry\">\n <p class=\"p\"><a data-bundleid=\"zurich-telecom-media-technology\" data-navpath=\"product/tmt-field-service-management/concept/field-service-management-telecommunications.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-media-technology/page/product/tmt-field-service-management/concept/field-service-management-telecommunications.html\" class=\"xref\" title=\"The ServiceNow Field Service Management for Telecommunications (FSMT) application enables you to manage the field service workflow for the telecommunications customers. Use this application to streamline the appointment booking, service delivery, and assurance processes.\"><span class=\"ph\">Field Service Management for Telecommunications</span><svg class=\"image svg decorative\" id=\"telecom-media-tech-landing__image_wml_h4j_b2c\" viewBox=\"0 0 64 64\" title=\"\" width=\"64\" height=\"64\"><title></title><defs></defs><rect class=\"cls-1\" style=\"fill:none;;\" width=\"64\" height=\"64\"></rect><polyline class=\"cls-2\" style=\"fill:none;;stroke:#000;stroke-linecap:round;stroke-linejoin:round;stroke-width:2px;;\" points=\"17.07 30.13 4 30.13 11.47 37.6 52.53 37.6 60 30.13 46.93 30.13\"></polyline><path class=\"cls-2\" style=\"fill:none;;stroke:#000;stroke-linecap:round;stroke-linejoin:round;stroke-width:2px;;\" d=\"M36.33,5.37a21.48,21.48,0,0,1,17.14,21v3.73\"></path><path class=\"cls-2\" style=\"fill:none;;stroke:#000;stroke-linecap:round;stroke-linejoin:round;stroke-width:2px;;\" d=\"M10.53,30.13V26.4A21.48,21.48,0,0,1,27.8,5.34\"></path><path class=\"cls-2\" style=\"fill:none;;stroke:#000;stroke-linecap:round;stroke-linejoin:round;stroke-width:2px;;\" d=\"M38.53,13.33V9.6S37.6,4,32,4s-6.53,5.6-6.53,5.6v3.73\"></path><path class=\"cls-3\" style=\"fill:#62d84e;;\" d=\"M41.33,28.27a9.33,9.33,0,1,0-18.66,0Z\"></path><path class=\"cls-2\" style=\"fill:none;;stroke:#000;stroke-linecap:round;stroke-linejoin:round;stroke-width:2px;;\" d=\"M50.67,41.33a18.67,18.67,0,0,1-37.34,0V37.6H50.67Z\"></path></svg><span class=\"ph\">Manage the field service workflow for the telecommunication industry customers.</span></a></p>\n </td>\n </tr>\n </tbody></table></div>\n </section>\n </div>\n</article></main></body></article>",
"topic_language": "enus",
"views": 0,
"your_rating": null
} | # Telecommunications, Media, and Technology (TMT)
The ServiceNow® Telecommunications, Media, and Technology (TMT) product suite brings together customer care, operations, order management, and partner ecosystems so that service providers can scale their business to
capitalize on the fast-growing “everything-as-a-service" opportunity.
| Customer Success Management Streamline, automate, and measure critical workflows across the enterprise. | Sales and Order ManagementCapture, manage, and fulfill customer and external service orders. | Proactive Service Experience Workflows Deliver end-to-end workflows to resolve network related incidents, and proactively notify impacted customers. |
| --- | --- | --- |
| Service Bridge Help customers and providers connect and track service requests directly between their instances. | Telecommunications Network Inventory Build and monitor your physical, logical networks, and provisioned services. | Telecommunications Service Operations Management Proactively monitor the health of your networks and services to prevent downtime. |
| Now Assist for Telecommunications, Media, and TechnologyHelps to summarize service problem cases, generate the case resolution notes, and summarize tests. | Strategic Portfolio Management for TelecommunicationsDefine and customize the tasks and requirements for your Fiber Rollout and 5G projects. | Field Service Management for TelecommunicationsManage the field service workflow for the telecommunication industry customers. |
| ---
title: Telecommunications, Media, and Technology (TMT)
description: "The ServiceNow\xAE Telecommunications, Media, and Technology (TMT) product\
\ suite brings together customer care, operations, order management, and partner\
\ ecosystems so that service providers can scale their business to capitalize on\
\ the fast-growing \u201Ceverything-as-a-service\" opportunity."
keywords: []
breadcrumbs: []
---
# Telecommunications, Media, and Technology (TMT)
The ServiceNow® Telecommunications, Media, and Technology (TMT) product suite brings together customer care, operations, order management, and partner ecosystems so that service providers can scale their business to
capitalize on the fast-growing “everything-as-a-service" opportunity.
| Customer Success Management Streamline, automate, and measure critical workflows across the enterprise. | Sales and Order ManagementCapture, manage, and fulfill customer and external service orders. | Proactive Service Experience Workflows Deliver end-to-end workflows to resolve network related incidents, and proactively notify impacted customers. |
| --- | --- | --- |
| Service Bridge Help customers and providers connect and track service requests directly between their instances. | Telecommunications Network Inventory Build and monitor your physical, logical networks, and provisioned services. | Telecommunications Service Operations Management Proactively monitor the health of your networks and services to prevent downtime. |
| Now Assist for Telecommunications, Media, and TechnologyHelps to summarize service problem cases, generate the case resolution notes, and summarize tests. | Strategic Portfolio Management for TelecommunicationsDefine and customize the tasks and requirements for your Fiber Rollout and 5G projects. | Field Service Management for TelecommunicationsManage the field service workflow for the telecommunication industry customers. |
|
https://www.servicenow.com/docs/en-US/bundle/zurich-telecom-media-technology/page/product/tmt-field-service-management/concept/managing-work-order-telecommunication-service.html | https://servicenow-be-prod.servicenow.com/api/bundle/zurich-telecom-media-technology/page/product/tmt-field-service-management/concept/managing-work-order-telecommunication-service.html | 2025-08-02 | daily | 0.5 | 268.xml | en-US | zurich-telecom-media-technology | product/tmt-field-service-management/concept/managing-work-order-telecommunication-service.html | zurich | Managing work orders for telecommunication services | Manage the work orders for the field services to support the installation, activation, and site assessments that are needed for connectivity services. | [] | [
"Telecommunications, Media, and Technology (TMT)",
"Field Service Management for Telecommunications"
] | <article class="hascomments" data-page="bundle:zurich-telecom-media-technology/enus/product/tmt-field-service-management/concept/managing-work-order-telecommunication-service.html" id="bundle:zurich-telecom-media-technology/enus/product/tmt-field-service-management/concept/managing-work-order-telecommunication-service.html"><body id="managing-work-order-telecommunication-service"><main role="main"><article role="article" class="dita" id="managing-work-order-telecommunication-service" aria-labelledby="title_managing-work-order-telecommunication-service">
<h1 class="title topictitle1" id="title_managing-work-order-telecommunication-service">Managing work orders for telecommunication services</h1>
<div class="body conbody"><p class="shortdesc">Manage the work orders for the field services to support the installation, activation, and site assessments that are needed for connectivity services.</p>
<p class="p">With the use of the <span class="ph">ServiceNow®</span> Telecommunication Open API <code class="ph codeph">(com.sn_tmf_api)</code> application, you create and manage work orders from your system for the connectivity-related field services. To learn more about managing work
orders in <span class="ph">Field Service Management</span>, see <a data-bundleid="zurich-telecom-media-technology" data-navpath="product/tmt-field-service-management/concept//csh" href="https://servicenow-be-prod.servicenow.com/csh?topicname=c_ManageWorkOrders&version=zurich&pubname=zurich-field-service-management" class="xref">Manage work orders</a>.</p>
<div class="p">This feature supports the following:<ul class="ul" id="managing-work-order-telecommunication-service__ul_upl_j4q_rfc">
<li class="li">Create a new work order</li>
<li class="li">Update an existing work order</li>
<li class="li">Fetch the details of a work order</li>
<li class="li">Cancel a work order</li>
</ul></div>
<p class="p">The Telecommunication Open API application uses the TM Forum 697 Service Order Management API specification to support the external system to create and manage work orders for the field services. To learn more, see <a data-bundleid="zurich-telecom-media-technology" data-navpath="product/tmt-field-service-management/concept//csh" href="https://servicenow-be-prod.servicenow.com/csh?topicname=work-order-mgmt-api&version=zurich&pubname=zurich-api-reference" class="xref">Work Order Management API</a>.</p>
</div>
</article></main></body></article> | {
"attachments": {
"all_attachments": null,
"topic_attachments": []
},
"available_languages": [
"enus"
],
"breadcrumbs": [
{
"title": "Telecommunications, Media, and Technology (TMT)",
"topic_id": "product/industry-products/concept/telecom-media-tech-landing.html"
},
{
"title": "Field Service Management for Telecommunications",
"topic_id": "product/tmt-field-service-management/concept/field-service-management-telecommunications.html"
}
],
"breadcrumbs_html": "<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-media-technology\">Zurich Telecommunications, Media, and Technology</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-media-technology/page/product/industry-products/concept/telecom-media-tech-landing.html\">Telecommunications, Media, and Technology (TMT)</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-media-technology/page/product/tmt-field-service-management/concept/field-service-management-telecommunications.html\">Field Service Management for Telecommunications</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<span class=\"active\">Managing work orders for telecommunication services</span>",
"bundle_id": "zurich-telecom-media-technology",
"bundle_key": 2724,
"bundle_landing_page": "product/industry-products/concept/telecom-media-tech-landing.html",
"bundle_subtitle": null,
"bundle_title": "Zurich Telecommunications, Media, and Technology",
"canonical_link": null,
"dates": {
"Added on": "2025-08-02T00:46:16.994385Z",
"Created on": "2025-06-17T00:00:00Z",
"Initial upload": "2025-07-30T22:20:16.545452Z",
"Updated on": "2025-07-31T00:00:00Z"
},
"dislike_url": "https://servicenow-be-prod.servicenow.com/dislike/55677616",
"dislikes": 0,
"es_archived_content": false,
"is_in_fav": false,
"is_liked": null,
"is_watched": false,
"keywords": [
" zurich zurich"
],
"labels": [
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "zurich",
"navtitle": "Zurich",
"outputclasses": [],
"subjectHeadId": "versions",
"subjectheadNavtitle": "Versions",
"visibility": "show-facet"
},
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "telmt",
"navtitle": "Telecommunications Media and Technology Assurance",
"outputclasses": [],
"subjectHeadId": "products",
"subjectheadNavtitle": "Products",
"visibility": "show-facet"
}
],
"labels_text": "Versions > Zurich; Products > CRM and Industry Products > Telecommunications Media and Technology Assurance",
"like_url": "https://servicenow-be-prod.servicenow.com/like/55677616",
"likes": 0,
"metadata": {
"AI Search": null,
"AI Search Assist": null,
"Application Insights": null,
"Capabilities": null,
"Code Signing": null,
"Contextual Search": null,
"DC.contributor": null,
"DC.coverage": null,
"DC.creator": "ServiceNow",
"DC.date.created": "2025-06-17T15:06:04+05:30",
"DC.date.modified": "2025-07-31",
"DC.format": "HTML5",
"DC.identifier": "managing-work-order-telecommunication-service",
"DC.language": null,
"DC.relation": null,
"DC.rights.owner": "(C) Copyright 2025",
"DC.subject": null,
"DC.type": "concept",
"Data Discovery": null,
"Data Policy": null,
"Data Privacy": null,
"Discovery": null,
"External Content for AI Search": null,
"Field Administration": null,
"Field Normalization": null,
"Key Management Framework": null,
"Localization Framework": null,
"Now Platform": null,
"PlatSec": null,
"Platform": null,
"Platform Administration": null,
"Platform Performance": null,
"Platform Privacy": null,
"Proactive Triggers": null,
"Process Optimization": null,
"RN doc editing record number": null,
"Search Administration": null,
"Secrets Management": null,
"ServiceNow AI Platform": null,
"State Model": null,
"Subscription Management": null,
"Task Communications Management": null,
"Timeline Visualizations": null,
"User Administration": null,
"User Experience Analytics": null,
"Zing": null,
"ai-now-assist": null,
"app-name": null,
"app_route": null,
"azureapimanagemen": null,
"change-completed": null,
"change-item": null,
"change-request-id": null,
"change-request-reference": null,
"com.glide.embedded_help.category": null,
"component": null,
"copyright": "(C) Copyright 2025",
"crossroads": null,
"data": null,
"description": "Manage the work orders for the field services to support the installation, activation, and site assessments that are needed for connectivity services.",
"dominant_bundle": null,
"erp-canvas-video": null,
"fsm-mobile": null,
"fsm-route": null,
"fsm-sched-opt": null,
"fsm-wrk-order": null,
"genai-round-7": null,
"generator": "DITA-OT",
"glossPartOfSpeech": null,
"glossStatus": null,
"guided setup": null,
"guided tours": null,
"keywords": null,
"min-toc": null,
"mini": null,
"mini-to truec": null,
"mini-toc": null,
"mini_toc": null,
"minitoc": null,
"modification": null,
"now-assist-app-gen-video": null,
"order": null,
"page-type": null,
"page-type ": null,
"prodname": null,
"product": null,
"product_name": null,
"release": null,
"resourceID": null,
"roles": null,
"route_page": null,
"route_params_listId": null,
"route_params_table": null,
"route_params_type": null,
"route_type": null,
"setconfigurationproperties": null,
"topic": null,
"translation-type": "source",
"version": null,
"workflow": "Customer and Industry",
"workplace-srvc-delvry-ditamap": null
},
"page_id": "product/tmt-field-service-management/concept/managing-work-order-telecommunication-service.html",
"page_key": 55677616,
"preprocessed_PDF": "https://downloads.docs.servicenow.com/pdf/enus/servicenow-zurich-telecom-media-technology-enus.pdf",
"rating": null,
"read_time_data": {
"char_count": 822,
"img_count": 0,
"read_time": 1,
"video_links": [
""
],
"word_count": 129
},
"related_links": [],
"search_title": null,
"title": "Managing work orders for telecommunication services",
"topic_cluster": {
"clustered_by": {
"enabled": true,
"primary_key": "versions",
"primary_sort": "top-down",
"type": "subjecthead"
},
"clustered_labels": [
"versions"
],
"clustered_topics": [],
"clustering_title": "Zurich"
},
"topic_html": "<article class=\"hascomments\" data-page=\"bundle:zurich-telecom-media-technology/enus/product/tmt-field-service-management/concept/managing-work-order-telecommunication-service.html\" id=\"bundle:zurich-telecom-media-technology/enus/product/tmt-field-service-management/concept/managing-work-order-telecommunication-service.html\"><body id=\"managing-work-order-telecommunication-service\"><main role=\"main\"><article role=\"article\" class=\"dita\" id=\"managing-work-order-telecommunication-service\" aria-labelledby=\"title_managing-work-order-telecommunication-service\">\n <h1 class=\"title topictitle1\" id=\"title_managing-work-order-telecommunication-service\">Managing work orders for telecommunication services</h1>\n \n \n <div class=\"body conbody\"><p class=\"shortdesc\">Manage the work orders for the field services to support the installation, activation, and site assessments that are needed for connectivity services.</p>\n <p class=\"p\">With the use of the <span class=\"ph\">ServiceNow®</span> Telecommunication Open API <code class=\"ph codeph\">(com.sn_tmf_api)</code> application, you create and manage work orders from your system for the connectivity-related field services. To learn more about managing work\n orders in <span class=\"ph\">Field Service Management</span>, see <a data-bundleid=\"zurich-telecom-media-technology\" data-navpath=\"product/tmt-field-service-management/concept//csh\" href=\"https://servicenow-be-prod.servicenow.com/csh?topicname=c_ManageWorkOrders&version=zurich&pubname=zurich-field-service-management\" class=\"xref\">Manage work orders</a>.</p>\n <div class=\"p\">This feature supports the following:<ul class=\"ul\" id=\"managing-work-order-telecommunication-service__ul_upl_j4q_rfc\">\n <li class=\"li\">Create a new work order</li>\n <li class=\"li\">Update an existing work order</li>\n <li class=\"li\">Fetch the details of a work order</li>\n <li class=\"li\">Cancel a work order</li>\n </ul></div>\n <p class=\"p\">The Telecommunication Open API application uses the TM Forum 697 Service Order Management API specification to support the external system to create and manage work orders for the field services. To learn more, see <a data-bundleid=\"zurich-telecom-media-technology\" data-navpath=\"product/tmt-field-service-management/concept//csh\" href=\"https://servicenow-be-prod.servicenow.com/csh?topicname=work-order-mgmt-api&version=zurich&pubname=zurich-api-reference\" class=\"xref\">Work Order Management API</a>.</p>\n </div>\n</article></main></body></article>",
"topic_language": "enus",
"views": 0,
"your_rating": null
} | # Managing work orders for telecommunication services
Manage the work orders for the field services to support the installation, activation, and site assessments that are needed for connectivity services.
With the use of the ServiceNow® Telecommunication Open API `(com.sn_tmf_api)` application, you create and manage work orders from your system for the connectivity-related field services. To learn more about managing work
orders in Field Service Management, see Manage work orders.
This feature supports the following:
* Create a new work order
* Update an existing work order
* Fetch the details of a work order
* Cancel a work order
The Telecommunication Open API application uses the TM Forum 697 Service Order Management API specification to support the external system to create and manage work orders for the field services. To learn more, see Work Order Management API.
| ---
title: Managing work orders for telecommunication services
description: Manage the work orders for the field services to support the installation,
activation, and site assessments that are needed for connectivity services.
keywords: []
breadcrumbs:
- Telecommunications, Media, and Technology (TMT)
- Field Service Management for Telecommunications
---
# Managing work orders for telecommunication services
Manage the work orders for the field services to support the installation, activation, and site assessments that are needed for connectivity services.
With the use of the ServiceNow® Telecommunication Open API `(com.sn_tmf_api)` application, you create and manage work orders from your system for the connectivity-related field services. To learn more about managing work
orders in Field Service Management, see Manage work orders.
This feature supports the following:
* Create a new work order
* Update an existing work order
* Fetch the details of a work order
* Cancel a work order
The Telecommunication Open API application uses the TM Forum 697 Service Order Management API specification to support the external system to create and manage work orders for the field services. To learn more, see Work Order Management API.
|
https://www.servicenow.com/docs/en-US/bundle/zurich-telecom-media-technology/page/product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html | https://servicenow-be-prod.servicenow.com/api/bundle/zurich-telecom-media-technology/page/product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html | 2025-08-02 | daily | 0.5 | 268.xml | en-US | zurich-telecom-media-technology | product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html | zurich | Telecommunications Service Operations Management | Learn how Telecommunications Service Operations Management (TSOM) empowers communication service providers (CSPs) to proactively monitor, analyze, and resolve network and service issues before they impact customers. Built on the ServiceNow AI Platform, TSOM delivers a unified operations view across distributed, | [] | [
"Telecommunications, Media, and Technology (TMT)"
] | <article class="hascomments" data-page="bundle:zurich-telecom-media-technology/enus/product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html" id="bundle:zurich-telecom-media-technology/enus/product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html"><body id="telecommunications-service-operations-management"><main role="main"><article role="article" class="dita" id="telecommunications-service-operations-management" aria-labelledby="title_telecommunications-service-operations-management">
<h1 class="title topictitle1" id="title_telecommunications-service-operations-management"><span class="ph">Telecommunications Service Operations Management</span></h1>
<div class="body refbody"><p class="shortdesc">Learn how <span class="ph">Telecommunications Service Operations Management</span> (TSOM) empowers communication service providers (CSPs) to proactively monitor, analyze, and resolve network and service issues before they impact customers. Built on the <span class="ph">ServiceNow AI Platform</span>, TSOM delivers a unified operations view across distributed, multi-domain telecom environments, helping teams improve service availability, operational efficiency, and customer satisfaction.</p>
<section class="section" id="telecommunications-service-operations-management__cf-app-landing-get-started"><h2 id="d4754e47" class="title sectiontitle">Get started</h2>
<div class="table-wrap"><table count-columns="2" class="table nav-card presentation frame-none" id="telecommunications-service-operations-management__table_acr_hnj_wfc" role="presentation"><caption></caption><colgroup><col style="width:50%"/><col style="width:50%"/></colgroup><tbody class="tbody">
<tr class="row">
<td class="entry">
<p class="p"><a data-bundleid="zurich-telecom-media-technology" data-navpath="product/tmt-telecom-service-operations-mgt/concept//csh" href="https://servicenow-be-prod.servicenow.com/csh?topicname=exploring-tsom&version=zurich&pubname=zurich-telecom-service-ops" class="xref"><span class="ph">Explore</span><svg class="image svg decorative" id="telecommunications-service-operations-management__image_n5w_rnh_dcc" viewBox="0 0 64 64" title="" width="64" height="64"><title></title><defs></defs><path class="cls-1" style="fill:#62d84e;;" d="M44.16,17.68a1.52,1.52,0,0,0-1.71-.17L28.77,25.19a1.49,1.49,0,0,0-.33,2.37l.26.26a1.52,1.52,0,0,0,1.49.38A4.51,4.51,0,0,1,36,32.5a4.06,4.06,0,0,1-.22,1.37,1.51,1.51,0,0,0,.36,1.55l.14.14a1.52,1.52,0,0,0,1.06.44,1.73,1.73,0,0,0,.32,0A1.52,1.52,0,0,0,38.75,35l5.84-15.68A1.51,1.51,0,0,0,44.16,17.68Z"></path><path class="cls-1" style="fill:#62d84e;;" d="M34.3,37.18a1.52,1.52,0,0,0-1.49-.38A4.51,4.51,0,0,1,27,32.5a4.06,4.06,0,0,1,.22-1.37,1.51,1.51,0,0,0-.36-1.55l-.14-.14a1.5,1.5,0,0,0-2.47.54L18.41,45.66a1.5,1.5,0,0,0,1.41,2,1.45,1.45,0,0,0,.73-.19l13.68-7.68a1.49,1.49,0,0,0,.33-2.37Z"></path><path d="M62,31.08,56.8,29.35A25.54,25.54,0,0,0,34.65,7.2L32.92,2a1.49,1.49,0,0,0-2.84,0L28.35,7.2A25.54,25.54,0,0,0,6.2,29.35L1,31.08a1.49,1.49,0,0,0,0,2.84L6.2,35.65A25.54,25.54,0,0,0,28.35,57.8L30.08,63a1.49,1.49,0,0,0,2.84,0l1.73-5.17A25.54,25.54,0,0,0,56.8,35.65L62,33.92a1.49,1.49,0,0,0,0-2.84ZM31.5,55A22.5,22.5,0,1,1,54,32.5,22.52,22.52,0,0,1,31.5,55Zm0-15A7.5,7.5,0,1,1,39,32.5,7.5,7.5,0,0,1,31.5,40Zm0-12A4.5,4.5,0,1,0,36,32.5,4.51,4.51,0,0,0,31.5,28Z"></path><rect class="cls-2" style="fill:none;;" width="64" height="64"></rect></svg><span class="ph">Learn about how telecom service providers use <span class="ph">Telecommunications Service Operations Management</span>.</span></a></p>
</td>
<td class="entry">
<p class="p"><a data-bundleid="zurich-telecom-media-technology" data-navpath="product/tmt-telecom-service-operations-mgt/concept//csh" href="https://servicenow-be-prod.servicenow.com/csh?topicname=configuring-tsom&version=zurich&pubname=zurich-telecom-service-ops" class="xref"><span class="ph">Configure</span><svg class="image svg decorative" id="telecommunications-service-operations-management__image_ewd_vnh_dcc" viewBox="0 0 64 64" title="" width="64" height="64"><title></title><defs></defs><path class="cls-1" style="fill:#62d84e;;" d="M61.67,47.43l-1.91-1a12,12,0,0,0-.36-2.89,11.61,11.61,0,0,0-1-2.64l1.2-1.74a2,2,0,0,0-.21-2.52L57.78,35a2,2,0,0,0-2.52-.3l-1.75,1.13A12.41,12.41,0,0,0,48,34.21l-.88-1.85a2,2,0,0,0-2.29-1.09l-2.26.57a2,2,0,0,0-1.51,2l.1,2.06A12.38,12.38,0,0,0,37,40l-2.07-.17a2,2,0,0,0-2.09,1.44l-.64,2.24a2,2,0,0,0,1,2.33l1.88,1a11.74,11.74,0,0,0,.36,2.79,11.89,11.89,0,0,0,1,2.72l-1.22,1.77a2,2,0,0,0,.21,2.52l1.61,1.68a2,2,0,0,0,2.52.29l1.84-1.18a12.31,12.31,0,0,0,5.4,1.54l.94,2A2,2,0,0,0,50.07,62l2.26-.57a2,2,0,0,0,1.51-2l-.1-2.19a12.35,12.35,0,0,0,4-3.9l2.17.17A2,2,0,0,0,62,52l.64-2.24A2,2,0,0,0,61.67,47.43ZM48.59,51.25a4.78,4.78,0,1,1,3.47-5.79A4.78,4.78,0,0,1,48.59,51.25Z"></path><path d="M20.06,31a8,8,0,1,1,8-8A8,8,0,0,1,20.06,31Zm0-13a5,5,0,1,0,5,5A5,5,0,0,0,20.06,18Zm3.43,25.5H16.63a1.5,1.5,0,0,1-1.47-1.21l-.74-3.73a16.74,16.74,0,0,1-5-2.89l-3.6,1.22A1.49,1.49,0,0,1,4,36.22L.6,30.28a1.49,1.49,0,0,1,.3-1.87l2.82-2.48a16.35,16.35,0,0,1-.28-3,15.63,15.63,0,0,1,.26-2.87L.9,17.6a1.52,1.52,0,0,1-.31-1.88L4,9.78A1.5,1.5,0,0,1,5.8,9.11l3.48,1.18a16.69,16.69,0,0,1,5.17-3l.71-3.57A1.5,1.5,0,0,1,16.63,2.5h6.86A1.49,1.49,0,0,1,25,3.71l.72,3.57a16.81,16.81,0,0,1,5.16,3l3.48-1.17a1.5,1.5,0,0,1,1.78.67l3.43,5.94a1.48,1.48,0,0,1-.31,1.87l-2.79,2.46a16.76,16.76,0,0,1,.26,2.88,16.16,16.16,0,0,1-.28,3l2.81,2.48a1.5,1.5,0,0,1,.31,1.88L36.1,36.22a1.49,1.49,0,0,1-1.78.67l-3.6-1.22a16.74,16.74,0,0,1-5,2.89L25,42.29A1.49,1.49,0,0,1,23.49,43.5Zm-5.63-3h4.4l.68-3.38A1.48,1.48,0,0,1,24,36a13.76,13.76,0,0,0,5.37-3.1,1.52,1.52,0,0,1,1.51-.33l3.26,1.1,2.2-3.81L33.77,27.6a1.5,1.5,0,0,1-.47-1.48,13.77,13.77,0,0,0,.39-3.19,13.91,13.91,0,0,0-.36-3.09,1.46,1.46,0,0,1,.47-1.46l2.52-2.23-2.2-3.81L31,13.41a1.48,1.48,0,0,1-1.51-.34A13.69,13.69,0,0,0,24,9.87a1.51,1.51,0,0,1-1-1.14L22.26,5.5h-4.4l-.64,3.23a1.5,1.5,0,0,1-1,1.14,13.77,13.77,0,0,0-5.5,3.2,1.49,1.49,0,0,1-1.52.34L6,12.35l-2.2,3.81,2.52,2.22a1.46,1.46,0,0,1,.47,1.46,13.91,13.91,0,0,0-.36,3.09,13.7,13.7,0,0,0,.39,3.19,1.5,1.5,0,0,1-.47,1.48L3.81,29.85,6,33.66l3.26-1.11a1.52,1.52,0,0,1,1.51.33A13.76,13.76,0,0,0,16.15,36a1.48,1.48,0,0,1,1,1.14Z"></path><rect class="cls-2" style="fill:none;;" width="64" height="64"></rect></svg><span class="ph">Plan and configure your <span class="ph">Telecommunications Service Operations Management</span>.</span></a></p>
</td>
</tr>
<tr class="row">
<td class="entry">
<p class="p"><a data-bundleid="zurich-telecom-media-technology" data-navpath="product/tmt-telecom-service-operations-mgt/concept//csh" href="https://servicenow-be-prod.servicenow.com/csh?topicname=using-tsom&version=zurich&pubname=zurich-telecom-service-ops" class="xref"><span class="ph">Use</span><svg class="image svg decorative" id="telecommunications-service-operations-management__image_cgq_ll4_tfc" viewBox="0 0 64 64" title="" width="64" height="64"><title></title><defs></defs><rect class="cls-1" style="fill:#62d84e;;" x="30" y="15" width="24" height="26" rx="2" transform="translate(70 -14) rotate(90)"></rect><path class="cls-2" style="fill:#fff;;" d="M39.46,34.5a1.49,1.49,0,0,1-1.06-.44l-3.75-3.75a1.5,1.5,0,0,1,2.12-2.12l2.69,2.69,7.94-7.94a1.49,1.49,0,0,1,2.12,0,1.51,1.51,0,0,1,0,2.12l-9,9A1.51,1.51,0,0,1,39.46,34.5Z"></path><path d="M17.5,61a1.52,1.52,0,0,1-1.28-.71,1.49,1.49,0,0,1-.06-1.46L21.07,49H5a5,5,0,0,1-5-5V10.5A4.49,4.49,0,0,1,4.5,6h54A4.49,4.49,0,0,1,63,10.5V44a5,5,0,0,1-5,5H41.93l4.91,9.83a1.49,1.49,0,0,1-.06,1.46A1.52,1.52,0,0,1,45.5,61Zm2.43-3H43.07l-4.5-9H24.43ZM4.5,9A1.5,1.5,0,0,0,3,10.5v34A1.5,1.5,0,0,0,4.5,46h54A1.5,1.5,0,0,0,60,44.5v-34A1.5,1.5,0,0,0,58.5,9ZM23,19.5A1.5,1.5,0,0,0,21.5,18H9.5a1.5,1.5,0,0,0,0,3h12A1.5,1.5,0,0,0,23,19.5Zm-4,8A1.5,1.5,0,0,0,17.5,26h-8a1.5,1.5,0,0,0,0,3h8A1.5,1.5,0,0,0,19,27.5Zm4,8A1.5,1.5,0,0,0,21.5,34H9.5a1.5,1.5,0,0,0,0,3h12A1.5,1.5,0,0,0,23,35.5Z"></path><rect class="cls-3" style="fill:none;;" width="64" height="64"></rect></svg><span class="ph">Use <span class="ph">Telecommunications Service Operations Management</span> to track comprehensive telecom service operations.</span></a></p>
</td>
<td class="entry">
<p class="p"><a data-bundleid="zurich-telecom-media-technology" data-navpath="product/tmt-telecom-service-operations-mgt/concept//csh" href="https://servicenow-be-prod.servicenow.com/csh?topicname=components-installed-with-tsom&version=zurich&pubname=zurich-telecom-service-ops" class="xref"><span class="ph">Reference</span><svg class="image svg decorative" id="telecommunications-service-operations-management__image_rnx_nyj_wfc" viewBox="0 0 64 64" title="" width="64" height="64"><title></title><defs></defs><path d="M62.31,5.23a1.51,1.51,0,0,0-1.44-.09L31.5,18.84,2.13,5.14a1.51,1.51,0,0,0-1.44.09A1.52,1.52,0,0,0,0,6.5v38a1.51,1.51,0,0,0,.87,1.36l30,14a1.49,1.49,0,0,0,1.26,0l30-14A1.51,1.51,0,0,0,63,44.5V6.5A1.52,1.52,0,0,0,62.31,5.23ZM3,8.86l27,12.6V56.14L3,43.54ZM60,43.54,33,56.14V21.46L60,8.86Z"></path><path d="M40.05,28.93a1.56,1.56,0,0,0,.63-.14l10.4-4.86a1.5,1.5,0,0,0-1.27-2.72l-10.4,4.86a1.5,1.5,0,0,0,.64,2.86Z"></path><path d="M40.05,36.93a1.56,1.56,0,0,0,.63-.14l12.86-6a1.5,1.5,0,0,0-1.27-2.72l-12.86,6a1.5,1.5,0,0,0,.64,2.86Z"></path><path d="M49.61,37.31l-10.2,4.76a1.5,1.5,0,0,0,.64,2.86,1.56,1.56,0,0,0,.63-.14L50.88,40a1.5,1.5,0,0,0-1.27-2.72Z"></path><path class="cls-1" style="fill:#62d84e;;" d="M21.15,25.23,12.09,20.9a1.45,1.45,0,0,0-1.41.1A1.5,1.5,0,0,0,10,22.26V33a1.51,1.51,0,0,0,.85,1.36l9.06,4.33a1.51,1.51,0,0,0,.62.14,1.41,1.41,0,0,0,.79-.24A1.5,1.5,0,0,0,22,37.36V26.59A1.51,1.51,0,0,0,21.15,25.23Z"></path><rect class="cls-2" style="fill:none;;" width="64" height="64"></rect></svg><span class="ph">Get <span class="ph">Telecommunications Service Operations Management</span> reference information.</span></a></p>
</td>
</tr>
</tbody></table></div>
</section>
<section class="section" id="telecommunications-service-operations-management__cf-app-landing-overview">
<p class="p">The following infographic helps you understand the architecture of <span class="ph">Telecommunications Service Operations Management</span>
<img src="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-media-technology/page/product/tmt-telecom-service-operations-mgt/concept/../images/architecture-telecom-applications.png?_LANG=enus" class="image" id="telecommunications-service-operations-management__image_wzp_5dk_b2c" alt="TSOM architecture and telecom applications."/></p>
</section>
<section class="section" id="telecommunications-service-operations-management__cf-app-landing-get-help"><h2 id="d4754e158" class="title sectiontitle">Additional resources</h2>
<div class="p">Some <span class="ph">ServiceNow</span> resources that can provide you with helpful information are:<dl class="dl">
<dt class="dt dlterm"><svg class="image svg decorative icon" id="telecommunications-service-operations-management__image_r25_g5k_wfc" viewBox="0 0 775 775">
<defs>
</defs>
<g id="Impact_d4754e171">
<circle cx="387.5" cy="387.5" r="125"></circle>
<path class="cls-2" style="fill-rule: evenodd;;" d="M661.5,661.5l-88.39-88.39c-47.5,47.5-113.13,76.88-185.62,76.88-144.97,0-262.5-117.53-262.5-262.5,0-72.49,29.38-138.11,76.88-185.62l-88.39-88.39C43.37,183.62,0,280.49,0,387.5c0,214.01,173.49,387.5,387.5,387.5,107,0,203.88-43.37,274-113.5Z"></path>
<path class="cls-1" style="fill: #62d84e; ; fill-rule: evenodd;;" d="M113.5,113.5C183.62,43.37,280.49,0,387.5,0c214.01,0,387.5,173.49,387.5,387.5,0,107-43.37,203.88-113.5,274l-88.39-88.39c47.5-47.5,76.88-113.13,76.88-185.62,0-144.97-117.53-262.5-262.5-262.5-72.49,0-138.11,29.38-185.62,76.88l-88.39-88.39Z"></path>
</g>
</svg> Release Notes</dt>
<dd class="dd">Learn more about what's new and changed in this release at <a data-bundleid="zurich-telecom-media-technology" data-navpath="product/tmt-telecom-service-operations-mgt/concept//csh" href="https://servicenow-be-prod.servicenow.com/csh?topicname=telecommunications-service-operations-management-rn&version=zurich&pubname=zurich-release-notes" class="xref">Telecommunications Service Operations Management (TSOM) release notes</a></dd>
<dt class="dt dlterm"><svg class="image svg decorative icon" id="telecommunications-service-operations-management__image_community-dl" viewBox="0 0 770 749.11">
<defs>
</defs>
<g id="Community_d4754e184">
<g>
<path class="cls-2" style="fill-rule: evenodd;;" d="M325.81,131.53c-37.87,8.59-72.5,25.33-102.09,48.25-27.29,21.13-66.55,16.14-87.68-11.15s-16.14-66.55,11.15-87.68C209.95,32.34,288.26,2.49,373.6.15c96.79-2.66,186.39,30.48,255.88,87.32,26.72,21.85,30.66,61.23,8.8,87.95s-61.23,30.66-87.95,8.81c-30.54-24.98-66.7-43.17-106.24-52.39,24.66,18.21,40.64,47.48,40.64,80.49,0,55.23-44.77,100-100,100s-100-44.77-100-100c0-33.19,16.17-62.61,41.07-80.8Z"></path>
<path class="cls-1" style="fill: #62d84e; ; fill-rule: evenodd;;" d="M573.93,562.32c-28.1,12.24-61.44,11.46-90.03-5.04-47.83-27.61-64.22-88.77-36.6-136.6s88.78-64.22,136.6-36.6c28.75,16.6,46.13,45.31,49.44,75.97,11.49-37.09,14.31-75.45,9.26-112.54-4.66-34.2,19.29-65.7,53.5-70.36,34.2-4.66,65.7,19.29,70.36,53.5,10.71,78.66-2.59,161.4-43.24,236.49-46.09,85.14-119.6,146.18-203.57,177.94-32.29,12.21-68.36-4.06-80.57-36.35-12.21-32.29,4.06-68.36,36.35-80.57,36.9-13.96,70.74-36.18,98.49-65.82Z"></path>
<path class="cls-2" style="fill-rule: evenodd;;" d="M195.08,562.11c26.37,28.5,58.19,50.12,92.83,64.29,31.95,13.07,47.25,49.56,34.19,81.51s-49.56,47.25-81.51,34.19c-73.48-30.06-138.48-82.95-183.19-155.69C6.71,503.92-9.39,409.75,5.09,321.15c5.57-34.07,37.7-57.17,71.76-51.6s57.17,37.7,51.6,71.76c-6.36,38.94-4.03,79.35,7.75,118.2,3.45-30.46,20.8-58.94,49.38-75.44,47.83-27.61,108.99-11.23,136.6,36.6,27.61,47.83,11.23,108.99-36.6,136.6-28.75,16.6-62.31,17.3-90.51,4.83Z"></path>
</g>
</g>
</svg><span class="ph">ServiceNow Community</span></dt>
<dd class="dd">Connect with other <span class="ph">Telecommunications Service Operations Management</span> users at <a class="xref true-external" href="https://community.servicenow.com/community" target="_blank">ServiceNow Community</a></dd>
<dt class="dt dlterm"><svg class="image svg decorative icon" id="telecommunications-service-operations-management__image_success-dl" viewBox="0 0 800 685.61">
<defs>
</defs>
<g id="Layer_10_d4754e201">
<path class="cls-1" style="fill: #62d84e; fill-rule: evenodd;;" d="M399.99,577c-118.72,0-199.99-85.65-199.99-191.58s81.27-193.11,199.99-193.11,199.99,87.11,199.99,193.11-81.21,191.58-199.99,191.58ZM402.33,0C183.14-1.2,1.86,170.62.01,381.43c-.94,111.57,47.55,212.31,125.64,283.17,28.42,25.74,72.34,28.26,103.16,5.2,45.54-34.05,103.97-54.34,171.18-54.34s125.67,20.32,171.21,54.34c31.09,23.25,75.2,20.26,103.75-5.76,76.98-70.11,125.05-169.36,125.05-279.37C800,172.98,622.13,1.2,402.33,0Z"></path>
</g>
</svg> Customer Success Center</dt>
<dd class="dd">Find useful resources related to your role and explore best practices at the <a class="xref true-external" href="https://www.servicenow.com/success.html?" target="_blank">Customer Success Center</a></dd>
<dt class="dt dlterm"><svg xmlns:xlink="http://www.w3.org/1999/xlink" class="image svg decorative icon" id="telecommunications-service-operations-management__image_learn-dl" viewBox="0 0 800 800">
<defs>
<clipPath id="clippath_d4754e214">
<rect class="cls-1" style="fill: none;;" width="800" height="800"></rect>
</clipPath>
</defs>
<g id="Learning_d4754e214">
<g class="cls-3" style="clip-path: url(#clippath_d4754e214);;;">
<g>
<path d="M345.83,579.09c191,59.83,394.34-46.5,454.17-237.5L108.33,124.92c-59.83,191,46.5,394.34,237.5,454.17Z"></path>
<path class="cls-2" style="fill: #62d84e;;" d="M362.61,362.52c200.15,0,362.4,162.26,362.4,362.41H.21c0-200.15,162.25-362.41,362.4-362.41Z"></path>
<circle class="cls-2" style="fill: #62d84e;;" cx="637.48" cy="187.48" r="87.48"></circle>
</g>
</g>
</g>
</svg>
<span class="ph">ServiceNow University</span></dt>
<dd class="dd">Access real-time courses, self-paced training, and career resources at <a class="xref true-external" href="https://nowlearning.servicenow.com/lxp/en/pages/servicenow" target="_blank">ServiceNow University</a></dd>
<dt class="dt dlterm"><svg class="image svg decorative icon" id="telecommunications-service-operations-management__image_support" viewBox="0 0 750 750">
<defs>
</defs>
<g id="Support_d4754e229">
<path class="cls-2" style="fill-rule: evenodd;;" d="M554.63,554.63l85.54,85.54c-67.86,67.86-161.61,109.84-265.16,109.84C167.89,750,0,582.11,0,375c0-103.56,41.97-197.3,109.84-265.17l85.54,85.54c-45.97,45.97-74.4,109.48-74.4,179.63,0,31.51,5.74,61.68,16.22,89.52,13.84-51.56,60.91-89.52,116.84-89.52,66.81,0,120.97,54.16,120.97,120.97,0,55.93-37.96,103-89.52,116.84,27.84,10.49,58.01,16.22,89.52,16.22,70.15,0,133.66-28.44,179.63-74.41Z"></path>
<path class="cls-1" style="fill: #62d84e; ; fill-rule: evenodd;;" d="M375,0c-103.55,0-197.3,41.97-265.17,109.84l85.54,85.54c45.97-45.97,109.48-74.4,179.63-74.4,31.51,0,61.68,5.74,89.52,16.22-51.56,13.84-89.52,60.91-89.52,116.84,0,66.81,54.16,120.97,120.97,120.97,55.93,0,103-37.96,116.84-89.52,10.49,27.84,16.23,58.01,16.23,89.52,0,70.15-28.44,133.66-74.41,179.63l85.54,85.54c67.86-67.86,109.84-161.61,109.84-265.16C750,167.89,582.11,0,375,0Z"></path>
</g>
</svg> Support</dt>
<dd class="dd">Contact customer service support at <a class="xref true-external" href="https://support.servicenow.com/now" target="_blank">https://support.servicenow.com/now</a></dd>
</dl></div>
</section>
</div>
</article></main></body></article> | {
"attachments": {
"all_attachments": null,
"topic_attachments": []
},
"available_languages": [
"enus"
],
"breadcrumbs": [
{
"title": "Telecommunications, Media, and Technology (TMT)",
"topic_id": "product/industry-products/concept/telecom-media-tech-landing.html"
}
],
"breadcrumbs_html": "<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-media-technology\">Zurich Telecommunications, Media, and Technology</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-media-technology/page/product/industry-products/concept/telecom-media-tech-landing.html\">Telecommunications, Media, and Technology (TMT)</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<span class=\"active\">Telecommunications Service Operations Management</span>",
"bundle_id": "zurich-telecom-media-technology",
"bundle_key": 2724,
"bundle_landing_page": "product/industry-products/concept/telecom-media-tech-landing.html",
"bundle_subtitle": null,
"bundle_title": "Zurich Telecommunications, Media, and Technology",
"canonical_link": null,
"dates": {
"Added on": "2025-08-02T00:46:16.994385Z",
"Created on": "2025-07-04T00:00:00Z",
"Initial upload": "2025-07-30T22:20:16.545452Z",
"Updated on": "2025-07-31T00:00:00Z"
},
"dislike_url": "https://servicenow-be-prod.servicenow.com/dislike/55677646",
"dislikes": 0,
"es_archived_content": false,
"is_in_fav": false,
"is_liked": null,
"is_watched": false,
"keywords": [
" zurich zurich"
],
"labels": [
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "zurich",
"navtitle": "Zurich",
"outputclasses": [],
"subjectHeadId": "versions",
"subjectheadNavtitle": "Versions",
"visibility": "show-facet"
},
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "telmt",
"navtitle": "Telecommunications Media and Technology Assurance",
"outputclasses": [],
"subjectHeadId": "products",
"subjectheadNavtitle": "Products",
"visibility": "show-facet"
}
],
"labels_text": "Versions > Zurich; Products > CRM and Industry Products > Telecommunications Media and Technology Assurance",
"like_url": "https://servicenow-be-prod.servicenow.com/like/55677646",
"likes": 0,
"metadata": {
"AI Search": null,
"AI Search Assist": null,
"Application Insights": null,
"Capabilities": null,
"Code Signing": null,
"Contextual Search": null,
"DC.contributor": null,
"DC.coverage": null,
"DC.creator": "ServiceNow",
"DC.date.created": "2025-07-04T13:02:14+05:30",
"DC.date.modified": "2025-07-31",
"DC.format": "HTML5",
"DC.identifier": "telecommunications-service-operations-management",
"DC.language": null,
"DC.relation": null,
"DC.rights.owner": "(C) Copyright 2025",
"DC.subject": null,
"DC.type": "reference",
"Data Discovery": null,
"Data Policy": null,
"Data Privacy": null,
"Discovery": null,
"External Content for AI Search": null,
"Field Administration": null,
"Field Normalization": null,
"Key Management Framework": null,
"Localization Framework": null,
"Now Platform": null,
"PlatSec": null,
"Platform": null,
"Platform Administration": null,
"Platform Performance": null,
"Platform Privacy": null,
"Proactive Triggers": null,
"Process Optimization": null,
"RN doc editing record number": null,
"Search Administration": null,
"Secrets Management": null,
"ServiceNow AI Platform": null,
"State Model": null,
"Subscription Management": null,
"Task Communications Management": null,
"Timeline Visualizations": null,
"User Administration": null,
"User Experience Analytics": null,
"Zing": null,
"ai-now-assist": null,
"app-name": null,
"app_route": null,
"azureapimanagemen": null,
"change-completed": null,
"change-item": null,
"change-request-id": null,
"change-request-reference": null,
"com.glide.embedded_help.category": null,
"component": null,
"copyright": "(C) Copyright 2025",
"crossroads": null,
"data": null,
"description": "Learn how Telecommunications Service Operations Management (TSOM) empowers communication service providers (CSPs) to proactively monitor, analyze, and resolve network and service issues before they impact customers. Built on the ServiceNow AI Platform, TSOM delivers a unified operations view across distributed,",
"dominant_bundle": null,
"erp-canvas-video": null,
"fsm-mobile": null,
"fsm-route": null,
"fsm-sched-opt": null,
"fsm-wrk-order": null,
"genai-round-7": null,
"generator": "DITA-OT",
"glossPartOfSpeech": null,
"glossStatus": null,
"guided setup": null,
"guided tours": null,
"keywords": null,
"min-toc": null,
"mini": null,
"mini-to truec": null,
"mini-toc": "yes",
"mini_toc": null,
"minitoc": null,
"modification": null,
"now-assist-app-gen-video": null,
"order": null,
"page-type": "landing-framework",
"page-type ": null,
"prodname": null,
"product": null,
"product_name": null,
"release": null,
"resourceID": null,
"roles": null,
"route_page": null,
"route_params_listId": null,
"route_params_table": null,
"route_params_type": null,
"route_type": null,
"setconfigurationproperties": null,
"topic": null,
"translation-type": "source",
"version": null,
"workflow": "Customer and Industry",
"workplace-srvc-delvry-ditamap": null
},
"page_id": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html",
"page_key": 55677646,
"preprocessed_PDF": "https://downloads.docs.servicenow.com/pdf/enus/servicenow-zurich-telecom-media-technology-enus.pdf",
"rating": null,
"read_time_data": {
"char_count": 1634,
"img_count": 1,
"read_time": 1,
"video_links": [
""
],
"word_count": 197
},
"related_links": [],
"search_title": null,
"title": "Telecommunications Service Operations Management",
"topic_cluster": {
"clustered_by": {
"enabled": true,
"primary_key": "versions",
"primary_sort": "top-down",
"type": "subjecthead"
},
"clustered_labels": [
"versions"
],
"clustered_topics": [],
"clustering_title": null
},
"topic_html": "<article class=\"hascomments\" data-page=\"bundle:zurich-telecom-media-technology/enus/product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html\" id=\"bundle:zurich-telecom-media-technology/enus/product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html\"><body id=\"telecommunications-service-operations-management\"><main role=\"main\"><article role=\"article\" class=\"dita\" id=\"telecommunications-service-operations-management\" aria-labelledby=\"title_telecommunications-service-operations-management\">\n <h1 class=\"title topictitle1\" id=\"title_telecommunications-service-operations-management\"><span class=\"ph\">Telecommunications Service Operations Management</span></h1>\n \n \n <div class=\"body refbody\"><p class=\"shortdesc\">Learn how <span class=\"ph\">Telecommunications Service Operations Management</span> (TSOM) empowers communication service providers (CSPs) to proactively monitor, analyze, and resolve network and service issues before they impact customers. Built on the <span class=\"ph\">ServiceNow AI Platform</span>, TSOM delivers a unified operations view across distributed, multi-domain telecom environments, helping teams improve service availability, operational efficiency, and customer satisfaction.</p>\n <section class=\"section\" id=\"telecommunications-service-operations-management__cf-app-landing-get-started\"><h2 id=\"d4754e47\" class=\"title sectiontitle\">Get started</h2>\n \n <div class=\"table-wrap\"><table count-columns=\"2\" class=\"table nav-card presentation frame-none\" id=\"telecommunications-service-operations-management__table_acr_hnj_wfc\" role=\"presentation\"><caption></caption><colgroup><col style=\"width:50%\"/><col style=\"width:50%\"/></colgroup><tbody class=\"tbody\">\n <tr class=\"row\">\n <td class=\"entry\">\n <p class=\"p\"><a data-bundleid=\"zurich-telecom-media-technology\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept//csh\" href=\"https://servicenow-be-prod.servicenow.com/csh?topicname=exploring-tsom&version=zurich&pubname=zurich-telecom-service-ops\" class=\"xref\"><span class=\"ph\">Explore</span><svg class=\"image svg decorative\" id=\"telecommunications-service-operations-management__image_n5w_rnh_dcc\" viewBox=\"0 0 64 64\" title=\"\" width=\"64\" height=\"64\"><title></title><defs></defs><path class=\"cls-1\" style=\"fill:#62d84e;;\" d=\"M44.16,17.68a1.52,1.52,0,0,0-1.71-.17L28.77,25.19a1.49,1.49,0,0,0-.33,2.37l.26.26a1.52,1.52,0,0,0,1.49.38A4.51,4.51,0,0,1,36,32.5a4.06,4.06,0,0,1-.22,1.37,1.51,1.51,0,0,0,.36,1.55l.14.14a1.52,1.52,0,0,0,1.06.44,1.73,1.73,0,0,0,.32,0A1.52,1.52,0,0,0,38.75,35l5.84-15.68A1.51,1.51,0,0,0,44.16,17.68Z\"></path><path class=\"cls-1\" style=\"fill:#62d84e;;\" d=\"M34.3,37.18a1.52,1.52,0,0,0-1.49-.38A4.51,4.51,0,0,1,27,32.5a4.06,4.06,0,0,1,.22-1.37,1.51,1.51,0,0,0-.36-1.55l-.14-.14a1.5,1.5,0,0,0-2.47.54L18.41,45.66a1.5,1.5,0,0,0,1.41,2,1.45,1.45,0,0,0,.73-.19l13.68-7.68a1.49,1.49,0,0,0,.33-2.37Z\"></path><path d=\"M62,31.08,56.8,29.35A25.54,25.54,0,0,0,34.65,7.2L32.92,2a1.49,1.49,0,0,0-2.84,0L28.35,7.2A25.54,25.54,0,0,0,6.2,29.35L1,31.08a1.49,1.49,0,0,0,0,2.84L6.2,35.65A25.54,25.54,0,0,0,28.35,57.8L30.08,63a1.49,1.49,0,0,0,2.84,0l1.73-5.17A25.54,25.54,0,0,0,56.8,35.65L62,33.92a1.49,1.49,0,0,0,0-2.84ZM31.5,55A22.5,22.5,0,1,1,54,32.5,22.52,22.52,0,0,1,31.5,55Zm0-15A7.5,7.5,0,1,1,39,32.5,7.5,7.5,0,0,1,31.5,40Zm0-12A4.5,4.5,0,1,0,36,32.5,4.51,4.51,0,0,0,31.5,28Z\"></path><rect class=\"cls-2\" style=\"fill:none;;\" width=\"64\" height=\"64\"></rect></svg><span class=\"ph\">Learn about how telecom service providers use <span class=\"ph\">Telecommunications Service Operations Management</span>.</span></a></p>\n </td>\n <td class=\"entry\">\n <p class=\"p\"><a data-bundleid=\"zurich-telecom-media-technology\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept//csh\" href=\"https://servicenow-be-prod.servicenow.com/csh?topicname=configuring-tsom&version=zurich&pubname=zurich-telecom-service-ops\" class=\"xref\"><span class=\"ph\">Configure</span><svg class=\"image svg decorative\" id=\"telecommunications-service-operations-management__image_ewd_vnh_dcc\" viewBox=\"0 0 64 64\" title=\"\" width=\"64\" height=\"64\"><title></title><defs></defs><path class=\"cls-1\" style=\"fill:#62d84e;;\" d=\"M61.67,47.43l-1.91-1a12,12,0,0,0-.36-2.89,11.61,11.61,0,0,0-1-2.64l1.2-1.74a2,2,0,0,0-.21-2.52L57.78,35a2,2,0,0,0-2.52-.3l-1.75,1.13A12.41,12.41,0,0,0,48,34.21l-.88-1.85a2,2,0,0,0-2.29-1.09l-2.26.57a2,2,0,0,0-1.51,2l.1,2.06A12.38,12.38,0,0,0,37,40l-2.07-.17a2,2,0,0,0-2.09,1.44l-.64,2.24a2,2,0,0,0,1,2.33l1.88,1a11.74,11.74,0,0,0,.36,2.79,11.89,11.89,0,0,0,1,2.72l-1.22,1.77a2,2,0,0,0,.21,2.52l1.61,1.68a2,2,0,0,0,2.52.29l1.84-1.18a12.31,12.31,0,0,0,5.4,1.54l.94,2A2,2,0,0,0,50.07,62l2.26-.57a2,2,0,0,0,1.51-2l-.1-2.19a12.35,12.35,0,0,0,4-3.9l2.17.17A2,2,0,0,0,62,52l.64-2.24A2,2,0,0,0,61.67,47.43ZM48.59,51.25a4.78,4.78,0,1,1,3.47-5.79A4.78,4.78,0,0,1,48.59,51.25Z\"></path><path d=\"M20.06,31a8,8,0,1,1,8-8A8,8,0,0,1,20.06,31Zm0-13a5,5,0,1,0,5,5A5,5,0,0,0,20.06,18Zm3.43,25.5H16.63a1.5,1.5,0,0,1-1.47-1.21l-.74-3.73a16.74,16.74,0,0,1-5-2.89l-3.6,1.22A1.49,1.49,0,0,1,4,36.22L.6,30.28a1.49,1.49,0,0,1,.3-1.87l2.82-2.48a16.35,16.35,0,0,1-.28-3,15.63,15.63,0,0,1,.26-2.87L.9,17.6a1.52,1.52,0,0,1-.31-1.88L4,9.78A1.5,1.5,0,0,1,5.8,9.11l3.48,1.18a16.69,16.69,0,0,1,5.17-3l.71-3.57A1.5,1.5,0,0,1,16.63,2.5h6.86A1.49,1.49,0,0,1,25,3.71l.72,3.57a16.81,16.81,0,0,1,5.16,3l3.48-1.17a1.5,1.5,0,0,1,1.78.67l3.43,5.94a1.48,1.48,0,0,1-.31,1.87l-2.79,2.46a16.76,16.76,0,0,1,.26,2.88,16.16,16.16,0,0,1-.28,3l2.81,2.48a1.5,1.5,0,0,1,.31,1.88L36.1,36.22a1.49,1.49,0,0,1-1.78.67l-3.6-1.22a16.74,16.74,0,0,1-5,2.89L25,42.29A1.49,1.49,0,0,1,23.49,43.5Zm-5.63-3h4.4l.68-3.38A1.48,1.48,0,0,1,24,36a13.76,13.76,0,0,0,5.37-3.1,1.52,1.52,0,0,1,1.51-.33l3.26,1.1,2.2-3.81L33.77,27.6a1.5,1.5,0,0,1-.47-1.48,13.77,13.77,0,0,0,.39-3.19,13.91,13.91,0,0,0-.36-3.09,1.46,1.46,0,0,1,.47-1.46l2.52-2.23-2.2-3.81L31,13.41a1.48,1.48,0,0,1-1.51-.34A13.69,13.69,0,0,0,24,9.87a1.51,1.51,0,0,1-1-1.14L22.26,5.5h-4.4l-.64,3.23a1.5,1.5,0,0,1-1,1.14,13.77,13.77,0,0,0-5.5,3.2,1.49,1.49,0,0,1-1.52.34L6,12.35l-2.2,3.81,2.52,2.22a1.46,1.46,0,0,1,.47,1.46,13.91,13.91,0,0,0-.36,3.09,13.7,13.7,0,0,0,.39,3.19,1.5,1.5,0,0,1-.47,1.48L3.81,29.85,6,33.66l3.26-1.11a1.52,1.52,0,0,1,1.51.33A13.76,13.76,0,0,0,16.15,36a1.48,1.48,0,0,1,1,1.14Z\"></path><rect class=\"cls-2\" style=\"fill:none;;\" width=\"64\" height=\"64\"></rect></svg><span class=\"ph\">Plan and configure your <span class=\"ph\">Telecommunications Service Operations Management</span>.</span></a></p>\n </td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry\">\n <p class=\"p\"><a data-bundleid=\"zurich-telecom-media-technology\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept//csh\" href=\"https://servicenow-be-prod.servicenow.com/csh?topicname=using-tsom&version=zurich&pubname=zurich-telecom-service-ops\" class=\"xref\"><span class=\"ph\">Use</span><svg class=\"image svg decorative\" id=\"telecommunications-service-operations-management__image_cgq_ll4_tfc\" viewBox=\"0 0 64 64\" title=\"\" width=\"64\" height=\"64\"><title></title><defs></defs><rect class=\"cls-1\" style=\"fill:#62d84e;;\" x=\"30\" y=\"15\" width=\"24\" height=\"26\" rx=\"2\" transform=\"translate(70 -14) rotate(90)\"></rect><path class=\"cls-2\" style=\"fill:#fff;;\" d=\"M39.46,34.5a1.49,1.49,0,0,1-1.06-.44l-3.75-3.75a1.5,1.5,0,0,1,2.12-2.12l2.69,2.69,7.94-7.94a1.49,1.49,0,0,1,2.12,0,1.51,1.51,0,0,1,0,2.12l-9,9A1.51,1.51,0,0,1,39.46,34.5Z\"></path><path d=\"M17.5,61a1.52,1.52,0,0,1-1.28-.71,1.49,1.49,0,0,1-.06-1.46L21.07,49H5a5,5,0,0,1-5-5V10.5A4.49,4.49,0,0,1,4.5,6h54A4.49,4.49,0,0,1,63,10.5V44a5,5,0,0,1-5,5H41.93l4.91,9.83a1.49,1.49,0,0,1-.06,1.46A1.52,1.52,0,0,1,45.5,61Zm2.43-3H43.07l-4.5-9H24.43ZM4.5,9A1.5,1.5,0,0,0,3,10.5v34A1.5,1.5,0,0,0,4.5,46h54A1.5,1.5,0,0,0,60,44.5v-34A1.5,1.5,0,0,0,58.5,9ZM23,19.5A1.5,1.5,0,0,0,21.5,18H9.5a1.5,1.5,0,0,0,0,3h12A1.5,1.5,0,0,0,23,19.5Zm-4,8A1.5,1.5,0,0,0,17.5,26h-8a1.5,1.5,0,0,0,0,3h8A1.5,1.5,0,0,0,19,27.5Zm4,8A1.5,1.5,0,0,0,21.5,34H9.5a1.5,1.5,0,0,0,0,3h12A1.5,1.5,0,0,0,23,35.5Z\"></path><rect class=\"cls-3\" style=\"fill:none;;\" width=\"64\" height=\"64\"></rect></svg><span class=\"ph\">Use <span class=\"ph\">Telecommunications Service Operations Management</span> to track comprehensive telecom service operations.</span></a></p>\n </td>\n <td class=\"entry\">\n <p class=\"p\"><a data-bundleid=\"zurich-telecom-media-technology\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept//csh\" href=\"https://servicenow-be-prod.servicenow.com/csh?topicname=components-installed-with-tsom&version=zurich&pubname=zurich-telecom-service-ops\" class=\"xref\"><span class=\"ph\">Reference</span><svg class=\"image svg decorative\" id=\"telecommunications-service-operations-management__image_rnx_nyj_wfc\" viewBox=\"0 0 64 64\" title=\"\" width=\"64\" height=\"64\"><title></title><defs></defs><path d=\"M62.31,5.23a1.51,1.51,0,0,0-1.44-.09L31.5,18.84,2.13,5.14a1.51,1.51,0,0,0-1.44.09A1.52,1.52,0,0,0,0,6.5v38a1.51,1.51,0,0,0,.87,1.36l30,14a1.49,1.49,0,0,0,1.26,0l30-14A1.51,1.51,0,0,0,63,44.5V6.5A1.52,1.52,0,0,0,62.31,5.23ZM3,8.86l27,12.6V56.14L3,43.54ZM60,43.54,33,56.14V21.46L60,8.86Z\"></path><path d=\"M40.05,28.93a1.56,1.56,0,0,0,.63-.14l10.4-4.86a1.5,1.5,0,0,0-1.27-2.72l-10.4,4.86a1.5,1.5,0,0,0,.64,2.86Z\"></path><path d=\"M40.05,36.93a1.56,1.56,0,0,0,.63-.14l12.86-6a1.5,1.5,0,0,0-1.27-2.72l-12.86,6a1.5,1.5,0,0,0,.64,2.86Z\"></path><path d=\"M49.61,37.31l-10.2,4.76a1.5,1.5,0,0,0,.64,2.86,1.56,1.56,0,0,0,.63-.14L50.88,40a1.5,1.5,0,0,0-1.27-2.72Z\"></path><path class=\"cls-1\" style=\"fill:#62d84e;;\" d=\"M21.15,25.23,12.09,20.9a1.45,1.45,0,0,0-1.41.1A1.5,1.5,0,0,0,10,22.26V33a1.51,1.51,0,0,0,.85,1.36l9.06,4.33a1.51,1.51,0,0,0,.62.14,1.41,1.41,0,0,0,.79-.24A1.5,1.5,0,0,0,22,37.36V26.59A1.51,1.51,0,0,0,21.15,25.23Z\"></path><rect class=\"cls-2\" style=\"fill:none;;\" width=\"64\" height=\"64\"></rect></svg><span class=\"ph\">Get <span class=\"ph\">Telecommunications Service Operations Management</span> reference information.</span></a></p>\n </td>\n </tr>\n </tbody></table></div>\n </section>\n <section class=\"section\" id=\"telecommunications-service-operations-management__cf-app-landing-overview\">\n <p class=\"p\">The following infographic helps you understand the architecture of <span class=\"ph\">Telecommunications Service Operations Management</span>\n <img src=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-media-technology/page/product/tmt-telecom-service-operations-mgt/concept/../images/architecture-telecom-applications.png?_LANG=enus\" class=\"image\" id=\"telecommunications-service-operations-management__image_wzp_5dk_b2c\" alt=\"TSOM architecture and telecom applications.\"/></p>\n </section>\n <section class=\"section\" id=\"telecommunications-service-operations-management__cf-app-landing-get-help\"><h2 id=\"d4754e158\" class=\"title sectiontitle\">Additional resources</h2>\n \n <div class=\"p\">Some <span class=\"ph\">ServiceNow</span> resources that can provide you with helpful information are:<dl class=\"dl\">\n \n <dt class=\"dt dlterm\"><svg class=\"image svg decorative icon\" id=\"telecommunications-service-operations-management__image_r25_g5k_wfc\" viewBox=\"0 0 775 775\">\n <defs>\n \n </defs>\n <g id=\"Impact_d4754e171\">\n <circle cx=\"387.5\" cy=\"387.5\" r=\"125\"></circle>\n <path class=\"cls-2\" style=\"fill-rule: evenodd;;\" d=\"M661.5,661.5l-88.39-88.39c-47.5,47.5-113.13,76.88-185.62,76.88-144.97,0-262.5-117.53-262.5-262.5,0-72.49,29.38-138.11,76.88-185.62l-88.39-88.39C43.37,183.62,0,280.49,0,387.5c0,214.01,173.49,387.5,387.5,387.5,107,0,203.88-43.37,274-113.5Z\"></path>\n <path class=\"cls-1\" style=\"fill: #62d84e; ; fill-rule: evenodd;;\" d=\"M113.5,113.5C183.62,43.37,280.49,0,387.5,0c214.01,0,387.5,173.49,387.5,387.5,0,107-43.37,203.88-113.5,274l-88.39-88.39c47.5-47.5,76.88-113.13,76.88-185.62,0-144.97-117.53-262.5-262.5-262.5-72.49,0-138.11,29.38-185.62,76.88l-88.39-88.39Z\"></path>\n </g>\n</svg> Release Notes</dt>\n <dd class=\"dd\">Learn more about what's new and changed in this release at <a data-bundleid=\"zurich-telecom-media-technology\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept//csh\" href=\"https://servicenow-be-prod.servicenow.com/csh?topicname=telecommunications-service-operations-management-rn&version=zurich&pubname=zurich-release-notes\" class=\"xref\">Telecommunications Service Operations Management (TSOM) release notes</a></dd>\n \n \n <dt class=\"dt dlterm\"><svg class=\"image svg decorative icon\" id=\"telecommunications-service-operations-management__image_community-dl\" viewBox=\"0 0 770 749.11\">\n <defs>\n \n </defs>\n <g id=\"Community_d4754e184\">\n <g>\n <path class=\"cls-2\" style=\"fill-rule: evenodd;;\" d=\"M325.81,131.53c-37.87,8.59-72.5,25.33-102.09,48.25-27.29,21.13-66.55,16.14-87.68-11.15s-16.14-66.55,11.15-87.68C209.95,32.34,288.26,2.49,373.6.15c96.79-2.66,186.39,30.48,255.88,87.32,26.72,21.85,30.66,61.23,8.8,87.95s-61.23,30.66-87.95,8.81c-30.54-24.98-66.7-43.17-106.24-52.39,24.66,18.21,40.64,47.48,40.64,80.49,0,55.23-44.77,100-100,100s-100-44.77-100-100c0-33.19,16.17-62.61,41.07-80.8Z\"></path>\n <path class=\"cls-1\" style=\"fill: #62d84e; ; fill-rule: evenodd;;\" d=\"M573.93,562.32c-28.1,12.24-61.44,11.46-90.03-5.04-47.83-27.61-64.22-88.77-36.6-136.6s88.78-64.22,136.6-36.6c28.75,16.6,46.13,45.31,49.44,75.97,11.49-37.09,14.31-75.45,9.26-112.54-4.66-34.2,19.29-65.7,53.5-70.36,34.2-4.66,65.7,19.29,70.36,53.5,10.71,78.66-2.59,161.4-43.24,236.49-46.09,85.14-119.6,146.18-203.57,177.94-32.29,12.21-68.36-4.06-80.57-36.35-12.21-32.29,4.06-68.36,36.35-80.57,36.9-13.96,70.74-36.18,98.49-65.82Z\"></path>\n <path class=\"cls-2\" style=\"fill-rule: evenodd;;\" d=\"M195.08,562.11c26.37,28.5,58.19,50.12,92.83,64.29,31.95,13.07,47.25,49.56,34.19,81.51s-49.56,47.25-81.51,34.19c-73.48-30.06-138.48-82.95-183.19-155.69C6.71,503.92-9.39,409.75,5.09,321.15c5.57-34.07,37.7-57.17,71.76-51.6s57.17,37.7,51.6,71.76c-6.36,38.94-4.03,79.35,7.75,118.2,3.45-30.46,20.8-58.94,49.38-75.44,47.83-27.61,108.99-11.23,136.6,36.6,27.61,47.83,11.23,108.99-36.6,136.6-28.75,16.6-62.31,17.3-90.51,4.83Z\"></path>\n </g>\n </g>\n</svg><span class=\"ph\">ServiceNow Community</span></dt>\n <dd class=\"dd\">Connect with other <span class=\"ph\">Telecommunications Service Operations Management</span> users at <a class=\"xref true-external\" href=\"https://community.servicenow.com/community\" target=\"_blank\">ServiceNow Community</a></dd>\n \n \n <dt class=\"dt dlterm\"><svg class=\"image svg decorative icon\" id=\"telecommunications-service-operations-management__image_success-dl\" viewBox=\"0 0 800 685.61\">\n <defs>\n \n </defs>\n <g id=\"Layer_10_d4754e201\">\n <path class=\"cls-1\" style=\"fill: #62d84e; fill-rule: evenodd;;\" d=\"M399.99,577c-118.72,0-199.99-85.65-199.99-191.58s81.27-193.11,199.99-193.11,199.99,87.11,199.99,193.11-81.21,191.58-199.99,191.58ZM402.33,0C183.14-1.2,1.86,170.62.01,381.43c-.94,111.57,47.55,212.31,125.64,283.17,28.42,25.74,72.34,28.26,103.16,5.2,45.54-34.05,103.97-54.34,171.18-54.34s125.67,20.32,171.21,54.34c31.09,23.25,75.2,20.26,103.75-5.76,76.98-70.11,125.05-169.36,125.05-279.37C800,172.98,622.13,1.2,402.33,0Z\"></path>\n </g>\n</svg> Customer Success Center</dt>\n <dd class=\"dd\">Find useful resources related to your role and explore best practices at the <a class=\"xref true-external\" href=\"https://www.servicenow.com/success.html?\" target=\"_blank\">Customer Success Center</a></dd>\n \n \n <dt class=\"dt dlterm\"><svg xmlns:xlink=\"http://www.w3.org/1999/xlink\" class=\"image svg decorative icon\" id=\"telecommunications-service-operations-management__image_learn-dl\" viewBox=\"0 0 800 800\">\n <defs>\n \n <clipPath id=\"clippath_d4754e214\">\n <rect class=\"cls-1\" style=\"fill: none;;\" width=\"800\" height=\"800\"></rect>\n </clipPath>\n </defs>\n <g id=\"Learning_d4754e214\">\n <g class=\"cls-3\" style=\"clip-path: url(#clippath_d4754e214);;;\">\n <g>\n <path d=\"M345.83,579.09c191,59.83,394.34-46.5,454.17-237.5L108.33,124.92c-59.83,191,46.5,394.34,237.5,454.17Z\"></path>\n <path class=\"cls-2\" style=\"fill: #62d84e;;\" d=\"M362.61,362.52c200.15,0,362.4,162.26,362.4,362.41H.21c0-200.15,162.25-362.41,362.4-362.41Z\"></path>\n <circle class=\"cls-2\" style=\"fill: #62d84e;;\" cx=\"637.48\" cy=\"187.48\" r=\"87.48\"></circle>\n </g>\n </g>\n </g>\n</svg>\n <span class=\"ph\">ServiceNow University</span></dt>\n <dd class=\"dd\">Access real-time courses, self-paced training, and career resources at <a class=\"xref true-external\" href=\"https://nowlearning.servicenow.com/lxp/en/pages/servicenow\" target=\"_blank\">ServiceNow University</a></dd>\n \n \n <dt class=\"dt dlterm\"><svg class=\"image svg decorative icon\" id=\"telecommunications-service-operations-management__image_support\" viewBox=\"0 0 750 750\">\n <defs>\n \n </defs>\n <g id=\"Support_d4754e229\">\n <path class=\"cls-2\" style=\"fill-rule: evenodd;;\" d=\"M554.63,554.63l85.54,85.54c-67.86,67.86-161.61,109.84-265.16,109.84C167.89,750,0,582.11,0,375c0-103.56,41.97-197.3,109.84-265.17l85.54,85.54c-45.97,45.97-74.4,109.48-74.4,179.63,0,31.51,5.74,61.68,16.22,89.52,13.84-51.56,60.91-89.52,116.84-89.52,66.81,0,120.97,54.16,120.97,120.97,0,55.93-37.96,103-89.52,116.84,27.84,10.49,58.01,16.22,89.52,16.22,70.15,0,133.66-28.44,179.63-74.41Z\"></path>\n <path class=\"cls-1\" style=\"fill: #62d84e; ; fill-rule: evenodd;;\" d=\"M375,0c-103.55,0-197.3,41.97-265.17,109.84l85.54,85.54c45.97-45.97,109.48-74.4,179.63-74.4,31.51,0,61.68,5.74,89.52,16.22-51.56,13.84-89.52,60.91-89.52,116.84,0,66.81,54.16,120.97,120.97,120.97,55.93,0,103-37.96,116.84-89.52,10.49,27.84,16.23,58.01,16.23,89.52,0,70.15-28.44,133.66-74.41,179.63l85.54,85.54c67.86-67.86,109.84-161.61,109.84-265.16C750,167.89,582.11,0,375,0Z\"></path>\n </g>\n</svg> Support</dt>\n <dd class=\"dd\">Contact customer service support at <a class=\"xref true-external\" href=\"https://support.servicenow.com/now\" target=\"_blank\">https://support.servicenow.com/now</a></dd>\n \n </dl></div>\n </section>\n </div>\n</article></main></body></article>",
"topic_language": "enus",
"views": 0,
"your_rating": null
} | # Telecommunications Service Operations Management
Learn how Telecommunications Service Operations Management (TSOM) empowers communication service providers (CSPs) to proactively monitor, analyze, and resolve network and service issues before they impact customers. Built on the ServiceNow AI Platform, TSOM delivers a unified operations view across distributed, multi-domain telecom environments, helping teams improve service availability, operational efficiency, and customer satisfaction.
## Get started
| ExploreLearn about how telecom service providers use Telecommunications Service Operations Management. | ConfigurePlan and configure your Telecommunications Service Operations Management. |
| --- | --- |
| UseUse Telecommunications Service Operations Management to track comprehensive telecom service operations. | ReferenceGet Telecommunications Service Operations Management reference information. |
The following infographic helps you understand the architecture of Telecommunications Service Operations Management
## Additional resources
Some ServiceNow resources that can provide you with helpful information are:
#### Release Notes
Learn more about what's new and changed in this release at Telecommunications Service Operations Management (TSOM) release notes
#### ServiceNow Community
Connect with other Telecommunications Service Operations Management users at ServiceNow Community
#### Customer Success Center
Find useful resources related to your role and explore best practices at the Customer Success Center
#### ServiceNow University
Access real-time courses, self-paced training, and career resources at ServiceNow University
#### Support
Contact customer service support at https://support.servicenow.com/now
| ---
title: Telecommunications Service Operations Management
description: Learn how Telecommunications Service Operations Management (TSOM) empowers
communication service providers (CSPs) to proactively monitor, analyze, and resolve
network and service issues before they impact customers. Built on the ServiceNow
AI Platform, TSOM delivers a unified operations view across distributed,
keywords: []
breadcrumbs:
- Telecommunications, Media, and Technology (TMT)
---
# Telecommunications Service Operations Management
Learn how Telecommunications Service Operations Management (TSOM) empowers communication service providers (CSPs) to proactively monitor, analyze, and resolve network and service issues before they impact customers. Built on the ServiceNow AI Platform, TSOM delivers a unified operations view across distributed, multi-domain telecom environments, helping teams improve service availability, operational efficiency, and customer satisfaction.
## Get started
| ExploreLearn about how telecom service providers use Telecommunications Service Operations Management. | ConfigurePlan and configure your Telecommunications Service Operations Management. |
| --- | --- |
| UseUse Telecommunications Service Operations Management to track comprehensive telecom service operations. | ReferenceGet Telecommunications Service Operations Management reference information. |
The following infographic helps you understand the architecture of Telecommunications Service Operations Management
## Additional resources
Some ServiceNow resources that can provide you with helpful information are:
#### Release Notes
Learn more about what's new and changed in this release at Telecommunications Service Operations Management (TSOM) release notes
#### ServiceNow Community
Connect with other Telecommunications Service Operations Management users at ServiceNow Community
#### Customer Success Center
Find useful resources related to your role and explore best practices at the Customer Success Center
#### ServiceNow University
Access real-time courses, self-paced training, and career resources at ServiceNow University
#### Support
Contact customer service support at https://support.servicenow.com/now
|
https://www.servicenow.com/docs/en-US/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/configuring-service-graph-connector-nokia-altiplano.html | https://servicenow-be-prod.servicenow.com/api/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/configuring-service-graph-connector-nokia-altiplano.html | 2025-08-02 | daily | 0.5 | 268.xml | en-US | zurich-telecom-service-ops | product/tmt-telecom-service-operations-mgt/concept/configuring-service-graph-connector-nokia-altiplano.html | zurich | Configuring Nokia Altiplano service graph connector | Configure the Nokia Altiplano service graph connector to import physical and logical inventory data from the Nokia Altiplano Access Network SDN Controller into your ServiceNow Configuration Management Database (CMDB). | [] | [
"Telecommunications Service Operations Management",
"Configuring Telecommunications Service Operations Management",
"Set up Telecom Visibility"
] | <article class="hascomments" data-page="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/configuring-service-graph-connector-nokia-altiplano.html" id="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/configuring-service-graph-connector-nokia-altiplano.html"><body id="configuring-service-graph-connector-nokia-altiplano"><main role="main"><article role="article" class="dita" id="configuring-service-graph-connector-nokia-altiplano" aria-labelledby="title_configuring-service-graph-connector-nokia-altiplano">
<h1 class="title topictitle1" id="title_configuring-service-graph-connector-nokia-altiplano">Configuring Nokia Altiplano service graph connector</h1>
<div class="body conbody"><p class="shortdesc">Configure the Nokia Altiplano service graph connector to import physical and logical inventory data from the Nokia Altiplano Access Network SDN Controller into your ServiceNow Configuration Management Database
(CMDB).</p>
<div class="p">This integration uses REST APIs (via a MID Server) to ensure the CMDB reflects accurate, up-to-date telecom inventory aligned with the TM Forum-based data model.<div class="note note note_note"><span class="note__title">Note:</span> A valid <span class="ph">Telecommunications Service Operations Management</span> subscription is required to use this connector.</div></div>
<section class="section" id="configuring-service-graph-connector-nokia-altiplano__section_bwx_kby_vfc"><h2 id="d9282e50" class="title sectiontitle">Required plugins</h2>
<div class="table-wrap"><table count-columns="2" class="table" id="configuring-service-graph-connector-nokia-altiplano__table_s1h_kby_vfc"><caption></caption><colgroup><col/><col/></colgroup><thead class="thead">
<tr class="row">
<th class="entry" id="configuring-service-graph-connector-nokia-altiplano__table_s1h_kby_vfc__entry__1">Plugin</th>
<th class="entry" id="configuring-service-graph-connector-nokia-altiplano__table_s1h_kby_vfc__entry__2">ID</th>
</tr>
</thead><tbody class="tbody">
<tr class="row">
<td class="entry" headers="configuring-service-graph-connector-nokia-altiplano__table_s1h_kby_vfc__entry__1">Telecom Service Operations Core</td>
<td class="entry" headers="configuring-service-graph-connector-nokia-altiplano__table_s1h_kby_vfc__entry__2"><code class="ph codeph">sn_tsom_core</code></td>
</tr>
<tr class="row">
<td class="entry" headers="configuring-service-graph-connector-nokia-altiplano__table_s1h_kby_vfc__entry__1">Pattern Designer</td>
<td class="entry" headers="configuring-service-graph-connector-nokia-altiplano__table_s1h_kby_vfc__entry__2"><code class="ph codeph">com.snc.pattern.designer</code></td>
</tr>
<tr class="row">
<td class="entry" headers="configuring-service-graph-connector-nokia-altiplano__table_s1h_kby_vfc__entry__1">Discovery Core (automatically installed with Discovery)</td>
<td class="entry" headers="configuring-service-graph-connector-nokia-altiplano__table_s1h_kby_vfc__entry__2"><code class="ph codeph">com.snc.discovery.core</code></td>
</tr>
<tr class="row">
<td class="entry" headers="configuring-service-graph-connector-nokia-altiplano__table_s1h_kby_vfc__entry__1">ITOM Discovery License</td>
<td class="entry" headers="configuring-service-graph-connector-nokia-altiplano__table_s1h_kby_vfc__entry__2"><code class="ph codeph">com.snc.itom.discovery.license</code></td>
</tr>
<tr class="row">
<td class="entry" headers="configuring-service-graph-connector-nokia-altiplano__table_s1h_kby_vfc__entry__1">ITOM Licensing</td>
<td class="entry" headers="configuring-service-graph-connector-nokia-altiplano__table_s1h_kby_vfc__entry__2"><code class="ph codeph">com.snc.itom.license</code></td>
</tr>
<tr class="row">
<td class="entry" headers="configuring-service-graph-connector-nokia-altiplano__table_s1h_kby_vfc__entry__1">IntegrationHub ETL (for development environments only)</td>
<td class="entry" headers="configuring-service-graph-connector-nokia-altiplano__table_s1h_kby_vfc__entry__2"><code class="ph codeph">sn_int_studio</code></td>
</tr>
</tbody></table></div>
<div class="note note note_note"><span class="note__title">Note:</span> External requirements:<ul class="ul" id="configuring-service-graph-connector-nokia-altiplano__ul_x2w_pby_vfc">
<li class="li">A running Nokia Altiplano Controller instance with access to its REST northbound API.</li>
<li class="li">A MID Server with secure connectivity to the Altiplano instance.</li>
</ul></div>
</section>
<section class="section" id="configuring-service-graph-connector-nokia-altiplano__section_xxb_vby_vfc"><h2 id="d9282e153" class="title sectiontitle">Configuration tasks overview</h2>
<p class="p">The following sections are available under the Nokia Altiplano navigation pane. Use the following table for post-guided setup or perform manual configurations.</p>
<div class="table-wrap"><table count-columns="2" class="table" id="configuring-service-graph-connector-nokia-altiplano__table_pyy_vby_vfc"><caption></caption><colgroup><col/><col/></colgroup><thead class="thead">
<tr class="row">
<th class="entry" id="configuring-service-graph-connector-nokia-altiplano__table_pyy_vby_vfc__entry__1">Section</th>
<th class="entry" id="configuring-service-graph-connector-nokia-altiplano__table_pyy_vby_vfc__entry__2">Description</th>
</tr>
</thead><tbody class="tbody">
<tr class="row">
<td class="entry" headers="configuring-service-graph-connector-nokia-altiplano__table_pyy_vby_vfc__entry__1">Setup</td>
<td class="entry" headers="configuring-service-graph-connector-nokia-altiplano__table_pyy_vby_vfc__entry__2">Configure MID Server, define Altiplano connections, and schedule imports.</td>
</tr>
<tr class="row">
<td class="entry" headers="configuring-service-graph-connector-nokia-altiplano__table_pyy_vby_vfc__entry__1">Data Sources</td>
<td class="entry" headers="configuring-service-graph-connector-nokia-altiplano__table_pyy_vby_vfc__entry__2">Predefined data sources for bulk and filtered discovery (SGC-Nokia Altiplano Bulk Discovery, SGC-Nokia Altiplano Filtering Discovery). Enable parallel loading if needed. For more information on parallel loading, see <a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/task/configure-concurrent-import-and-parallel-loading.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/configure-concurrent-import-and-parallel-loading.html" class="xref" title="Improve the efficiency of large data imports from Nokia Altiplano by configuring concurrent imports and enabling parallel loading. This configuration allows the platform to run multiple data import and transformation jobs simultaneously.">Configure concurrent import and parallel loading for Nokia Altiplano</a>.</td>
</tr>
<tr class="row">
<td class="entry" headers="configuring-service-graph-connector-nokia-altiplano__table_pyy_vby_vfc__entry__1">Import Schedules</td>
<td class="entry" headers="configuring-service-graph-connector-nokia-altiplano__table_pyy_vby_vfc__entry__2">Manage scheduling for each Altiplano connection alias. Run jobs manually or at defined intervals.</td>
</tr>
<tr class="row">
<td class="entry" headers="configuring-service-graph-connector-nokia-altiplano__table_pyy_vby_vfc__entry__1">Connections & Credential Aliases</td>
<td class="entry" headers="configuring-service-graph-connector-nokia-altiplano__table_pyy_vby_vfc__entry__2">Define aliases for each Altiplano instance. Store connection metadata and credentials.</td>
</tr>
<tr class="row">
<td class="entry" headers="configuring-service-graph-connector-nokia-altiplano__table_pyy_vby_vfc__entry__1">Connections</td>
<td class="entry" headers="configuring-service-graph-connector-nokia-altiplano__table_pyy_vby_vfc__entry__2">Define Altiplano instance details, such as URL, selected MID Server, credential reference, and connection alias reference.</td>
</tr>
<tr class="row">
<td class="entry" headers="configuring-service-graph-connector-nokia-altiplano__table_pyy_vby_vfc__entry__1">Credentials</td>
<td class="entry" headers="configuring-service-graph-connector-nokia-altiplano__table_pyy_vby_vfc__entry__2">Create Altiplano credentials using Basic Auth.</td>
</tr>
<tr class="row">
<td class="entry" headers="configuring-service-graph-connector-nokia-altiplano__table_pyy_vby_vfc__entry__1">Filters</td>
<td class="entry" headers="configuring-service-graph-connector-nokia-altiplano__table_pyy_vby_vfc__entry__2">Configure filtering parameters used in filtered discovery (for example, by device IP or name).</td>
</tr>
<tr class="row">
<td class="entry" headers="configuring-service-graph-connector-nokia-altiplano__table_pyy_vby_vfc__entry__1">Properties</td>
<td class="entry" headers="configuring-service-graph-connector-nokia-altiplano__table_pyy_vby_vfc__entry__2">Modify system behavior using connector-specific properties. For more information, see <a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/reference/properties-installed-with-nokia-altiplano.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/reference/properties-installed-with-nokia-altiplano.html" class="xref" title="System properties control how the connector operates, including discovery options and performance settings.">System components installed with Nokia Altiplano</a>.</td>
</tr>
</tbody></table></div>
</section>
<section class="section" id="configuring-service-graph-connector-nokia-altiplano__section_opx_lcy_vfc"><h2 id="d9282e274" class="title sectiontitle">Supported Nokia Altiplano versions</h2>
<div class="p">
<ul class="ul" id="configuring-service-graph-connector-nokia-altiplano__ul_ppx_lcy_vfc">
<li class="li">Minimum supported version: 24.6</li>
<li class="li">Supported OLT: Lightspan MF-2</li>
</ul>
<div class="note note note_note"><span class="note__title">Note:</span> Fore more information, see <a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/concept/data-mapping.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/data-mapping.html" class="xref" title="Use the Service Graph Connector for Nokia Altiplano to map discovered physical and logical network resources to telecom-aligned Configuration Item (CI) classes in the CMDB. The connector supports consistent service modeling, visibility into chassis-level components, and automation of logical and physical relationships.">Mapping Nokia Altiplano CIs and Relationships in CMDB</a>.</div>
</div>
</section>
<section class="section" id="configuring-service-graph-connector-nokia-altiplano__section_uyj_rz1_wfc"><h2 id="d9282e302" class="title sectiontitle">Access the Guided Setup</h2>
<p class="p">Use the guided setup to simplify the configuration process. This setup provides an organized sequence of steps to help you complete integration quickly and correctly. To access the guided setup:</p>
<ol class="ol" id="configuring-service-graph-connector-nokia-altiplano__ol_vyj_rz1_wfc">
<li class="li">Navigate to <span class="ph menucascade"><span class="ph uicontrol">All</span><abbr> > </abbr><span class="ph uicontrol">Service Graph Connectors</span><abbr> > </abbr><span class="ph uicontrol">Nokia Altiplano</span><abbr> > </abbr><span class="ph uicontrol">Setup</span></span>.</li>
<li class="li">Follow the task sequence to configure MID Server settings, Nokia Altiplano connections, filters, and import schedules. For more information, see <a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/task/initial-setup-procedure.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/initial-setup-procedure.html" class="xref" title="Learn how to install and configure the Service Graph Connector for Nokia Altiplano, including optional demo data, connectivity setup, and data collection schedules.">Install and configure the Nokia Altiplano</a>.</li>
</ol>
</section>
</div>
<nav role="navigation"></nav><nav role="navigation" class="tasksNavigation"></nav><nav role="navigation" class="related-links"><div class="col-md-4"><dt>Related tasks</dt><dd><ul><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/task/initial-setup-procedure.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/initial-setup-procedure.html" class="link" title="Learn how to install and configure the Service Graph Connector for Nokia Altiplano, including optional demo data, connectivity setup, and data collection schedules.">Install and configure the Nokia Altiplano</a></li><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/task/multi-instance-setup.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/multi-instance-setup.html" class="link" title="Learn how to configure and manage multiple Nokia Altiplano instances within a single ServiceNow environment. This enables administrators and integrators to create independent connection aliases and import schedules customized to specific filtering or frequency needs.">Set up multiple Nokia Altiplano instances</a></li><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/task/configure-concurrent-import-and-parallel-loading.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/configure-concurrent-import-and-parallel-loading.html" class="link" title="Improve the efficiency of large data imports from Nokia Altiplano by configuring concurrent imports and enabling parallel loading. This configuration allows the platform to run multiple data import and transformation jobs simultaneously.">Configure concurrent import and parallel loading for Nokia Altiplano</a></li><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/task/run-and-verify-import-for-nokia-altiplano-service-graph-connector.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/run-and-verify-import-for-nokia-altiplano-service-graph-connector.html" class="link" title="Manually execute a configured import schedule for the Nokia Altiplano Service Graph Connector. You can also execute the import to validate the connector setup, run ad-hoc imports, or test newly configured connection aliases. This task helps ensure that data from Altiplano is successfully imported or updated in the CMDB.">Run and verify import for Nokia Altiplano Service Graph Connector</a></li></ul></dd></div><div class="col-md-4"><dt>Related concepts</dt><dd><ul><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/concept/data-mapping.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/data-mapping.html" class="link" title="Use the Service Graph Connector for Nokia Altiplano to map discovered physical and logical network resources to telecom-aligned Configuration Item (CI) classes in the CMDB. The connector supports consistent service modeling, visibility into chassis-level components, and automation of logical and physical relationships.">Mapping Nokia Altiplano CIs and Relationships in CMDB</a></li><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/concept/service-graph-connector-for-nokia-altiplano.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/service-graph-connector-for-nokia-altiplano.html" class="link" title="The Service Graph Connector for Nokia Altiplano offers a telecom-aware integration that brings real-time network inventory from the Nokia Altiplano Access Network SDN Controller into your ServiceNow CMDB.">Telecom Discovery via Nokia Altiplano</a></li></ul></dd></div><div class="col-md-4"><dt>Related reference</dt><dd><ul><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/reference/properties-installed-with-nokia-altiplano.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/reference/properties-installed-with-nokia-altiplano.html" class="link" title="System properties control how the connector operates, including discovery options and performance settings.">System components installed with Nokia Altiplano</a></li></ul></dd></div></nav>
</article></main></body></article> | {
"attachments": {
"all_attachments": null,
"topic_attachments": []
},
"available_languages": [
"enus"
],
"breadcrumbs": [
{
"title": "Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html"
},
{
"title": "Configuring Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/configuring-tsom.html"
},
{
"title": "Set up Telecom Visibility",
"topic_id": "product/tmt-telecom-service-operations-mgt/task/configuring-tsom-visibility.html"
}
],
"breadcrumbs_html": "<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops\">Zurich Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html\">Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/configuring-tsom.html\">Configuring Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/configuring-tsom-visibility.html\">Set up Telecom Visibility</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<span class=\"active\">Configuring Nokia Altiplano service graph connector</span>",
"bundle_id": "zurich-telecom-service-ops",
"bundle_key": 2733,
"bundle_landing_page": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html",
"bundle_subtitle": null,
"bundle_title": "Zurich Telecommunications Service Operations Management",
"canonical_link": null,
"dates": {
"Added on": "2025-08-02T00:48:08.794016Z",
"Created on": "2025-01-15T00:00:00Z",
"Initial upload": "2025-07-30T22:24:33.519043Z",
"Updated on": "2025-07-31T00:00:00Z"
},
"dislike_url": "https://servicenow-be-prod.servicenow.com/dislike/55686927",
"dislikes": 0,
"es_archived_content": false,
"is_in_fav": false,
"is_liked": null,
"is_watched": false,
"keywords": [
" zurich zurich"
],
"labels": [
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "zurich",
"navtitle": "Zurich",
"outputclasses": [],
"subjectHeadId": "versions",
"subjectheadNavtitle": "Versions",
"visibility": "show-facet"
},
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "tsom",
"navtitle": "Telecommunications Service Operations Management",
"outputclasses": [],
"subjectHeadId": "products",
"subjectheadNavtitle": "Products",
"visibility": "show-facet"
}
],
"labels_text": "Versions > Zurich; Products > CRM and Industry Products > Telecommunications Media and Technology Assurance > Telecommunications Service Operations Management",
"like_url": "https://servicenow-be-prod.servicenow.com/like/55686927",
"likes": 0,
"metadata": {
"AI Search": null,
"AI Search Assist": null,
"Application Insights": null,
"Capabilities": null,
"Code Signing": null,
"Contextual Search": null,
"DC.contributor": null,
"DC.coverage": null,
"DC.creator": "ServiceNow",
"DC.date.created": "2025-01-15T12:05:35+05:30",
"DC.date.modified": "2025-07-31",
"DC.format": "HTML5",
"DC.identifier": "configuring-service-graph-connector-nokia-altiplano",
"DC.language": null,
"DC.relation": "../task/initial-setup-procedure.html",
"DC.rights.owner": "(C) Copyright 2025",
"DC.subject": null,
"DC.type": "concept",
"Data Discovery": null,
"Data Policy": null,
"Data Privacy": null,
"Discovery": null,
"External Content for AI Search": null,
"Field Administration": null,
"Field Normalization": null,
"Key Management Framework": null,
"Localization Framework": null,
"Now Platform": null,
"PlatSec": null,
"Platform": null,
"Platform Administration": null,
"Platform Performance": null,
"Platform Privacy": null,
"Proactive Triggers": null,
"Process Optimization": null,
"RN doc editing record number": null,
"Search Administration": null,
"Secrets Management": null,
"ServiceNow AI Platform": null,
"State Model": null,
"Subscription Management": null,
"Task Communications Management": null,
"Timeline Visualizations": null,
"User Administration": null,
"User Experience Analytics": null,
"Zing": null,
"ai-now-assist": null,
"app-name": null,
"app_route": null,
"azureapimanagemen": null,
"change-completed": null,
"change-item": null,
"change-request-id": null,
"change-request-reference": null,
"com.glide.embedded_help.category": null,
"component": null,
"copyright": "(C) Copyright 2025",
"crossroads": null,
"data": null,
"description": "Configure the Nokia Altiplano service graph connector to import physical and logical inventory data from the Nokia Altiplano Access Network SDN Controller into your ServiceNow Configuration Management Database (CMDB).",
"dominant_bundle": null,
"erp-canvas-video": null,
"fsm-mobile": null,
"fsm-route": null,
"fsm-sched-opt": null,
"fsm-wrk-order": null,
"genai-round-7": null,
"generator": "DITA-OT",
"glossPartOfSpeech": null,
"glossStatus": null,
"guided setup": null,
"guided tours": null,
"keywords": null,
"min-toc": null,
"mini": null,
"mini-to truec": null,
"mini-toc": "yes",
"mini_toc": null,
"minitoc": null,
"modification": null,
"now-assist-app-gen-video": null,
"order": null,
"page-type": null,
"page-type ": null,
"prodname": null,
"product": null,
"product_name": null,
"release": null,
"resourceID": null,
"roles": null,
"route_page": null,
"route_params_listId": null,
"route_params_table": null,
"route_params_type": null,
"route_type": null,
"setconfigurationproperties": null,
"topic": null,
"translation-type": "source",
"version": null,
"workflow": "Customer and Industry",
"workplace-srvc-delvry-ditamap": null
},
"page_id": "product/tmt-telecom-service-operations-mgt/concept/configuring-service-graph-connector-nokia-altiplano.html",
"page_key": 55686927,
"preprocessed_PDF": "https://downloads.docs.servicenow.com/pdf/enus/servicenow-zurich-telecom-service-ops-enus.pdf",
"rating": null,
"read_time_data": {
"char_count": 2928,
"img_count": 0,
"read_time": 2,
"video_links": [
""
],
"word_count": 388
},
"related_links": [
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "Learn how to install and configure the Service Graph Connector for Nokia Altiplano, including optional demo data, connectivity setup, and data collection schedules.",
"title": "Install and configure the Nokia Altiplano",
"topic": "/product/tmt-telecom-service-operations-mgt/task/initial-setup-procedure.html",
"type": "task",
"url": null
},
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "Learn how to configure and manage multiple Nokia Altiplano instances within a single ServiceNow environment. This enables administrators and integrators to create independent connection aliases and import schedules customized to specific filtering or frequency needs.",
"title": "Set up multiple Nokia Altiplano instances",
"topic": "/product/tmt-telecom-service-operations-mgt/task/multi-instance-setup.html",
"type": "task",
"url": null
},
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "Improve the efficiency of large data imports from Nokia Altiplano by configuring concurrent imports and enabling parallel loading. This configuration allows the platform to run multiple data import and transformation jobs simultaneously.",
"title": "Configure concurrent import and parallel loading for Nokia Altiplano",
"topic": "/product/tmt-telecom-service-operations-mgt/task/configure-concurrent-import-and-parallel-loading.html",
"type": "task",
"url": null
},
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "Use the Service Graph Connector for Nokia Altiplano to map discovered physical and logical network resources to telecom-aligned Configuration Item (CI) classes in the CMDB. The connector supports consistent service modeling, visibility into chassis-level components, and automation of logical and physical relationships.",
"title": "Mapping Nokia Altiplano CIs and Relationships in CMDB",
"topic": "/product/tmt-telecom-service-operations-mgt/concept/data-mapping.html",
"type": "concept",
"url": null
},
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "Manually execute a configured import schedule for the Nokia Altiplano Service Graph Connector. You can also execute the import to validate the connector setup, run ad-hoc imports, or test newly configured connection aliases. This task helps ensure that data from Altiplano is successfully imported or updated in the CMDB.",
"title": "Run and verify import for Nokia Altiplano Service Graph Connector",
"topic": "/product/tmt-telecom-service-operations-mgt/task/run-and-verify-import-for-nokia-altiplano-service-graph-connector.html",
"type": "task",
"url": null
},
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "System properties control how the connector operates, including discovery options and performance settings.",
"title": "System components installed with Nokia Altiplano",
"topic": "/product/tmt-telecom-service-operations-mgt/reference/properties-installed-with-nokia-altiplano.html",
"type": "reference",
"url": null
},
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "The Service Graph Connector for Nokia Altiplano offers a telecom-aware integration that brings real-time network inventory from the Nokia Altiplano Access Network SDN Controller into your ServiceNow CMDB.",
"title": "Telecom Discovery via Nokia Altiplano",
"topic": "/product/tmt-telecom-service-operations-mgt/concept/service-graph-connector-for-nokia-altiplano.html",
"type": "concept",
"url": null
}
],
"search_title": null,
"title": "Configuring Nokia Altiplano service graph connector",
"topic_cluster": {
"clustered_by": {
"enabled": true,
"primary_key": "versions",
"primary_sort": "top-down",
"type": "subjecthead"
},
"clustered_labels": [
"versions"
],
"clustered_topics": [
{
"bundle_id": "yokohama-telecom-service-ops",
"clustering_title": "Yokohama",
"es_archived_content": false,
"page_id": "product/tmt-telecom-service-operations-mgt/concept/configuring-service-graph-connector-nokia-altiplano.html"
}
],
"clustering_title": "Zurich"
},
"topic_html": "<article class=\"hascomments\" data-page=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/configuring-service-graph-connector-nokia-altiplano.html\" id=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/configuring-service-graph-connector-nokia-altiplano.html\"><body id=\"configuring-service-graph-connector-nokia-altiplano\"><main role=\"main\"><article role=\"article\" class=\"dita\" id=\"configuring-service-graph-connector-nokia-altiplano\" aria-labelledby=\"title_configuring-service-graph-connector-nokia-altiplano\">\n <h1 class=\"title topictitle1\" id=\"title_configuring-service-graph-connector-nokia-altiplano\">Configuring Nokia Altiplano service graph connector</h1>\n \n \n <div class=\"body conbody\"><p class=\"shortdesc\">Configure the Nokia Altiplano service graph connector to import physical and logical inventory data from the Nokia Altiplano Access Network SDN Controller into your ServiceNow Configuration Management Database\n (CMDB).</p>\n <div class=\"p\">This integration uses REST APIs (via a MID Server) to ensure the CMDB reflects accurate, up-to-date telecom inventory aligned with the TM Forum-based data model.<div class=\"note note note_note\"><span class=\"note__title\">Note:</span> A valid <span class=\"ph\">Telecommunications Service Operations Management</span> subscription is required to use this connector.</div></div>\n <section class=\"section\" id=\"configuring-service-graph-connector-nokia-altiplano__section_bwx_kby_vfc\"><h2 id=\"d9282e50\" class=\"title sectiontitle\">Required plugins</h2>\n \n <div class=\"table-wrap\"><table count-columns=\"2\" class=\"table\" id=\"configuring-service-graph-connector-nokia-altiplano__table_s1h_kby_vfc\"><caption></caption><colgroup><col/><col/></colgroup><thead class=\"thead\">\n <tr class=\"row\">\n <th class=\"entry\" id=\"configuring-service-graph-connector-nokia-altiplano__table_s1h_kby_vfc__entry__1\">Plugin</th>\n <th class=\"entry\" id=\"configuring-service-graph-connector-nokia-altiplano__table_s1h_kby_vfc__entry__2\">ID</th>\n </tr>\n </thead><tbody class=\"tbody\">\n <tr class=\"row\">\n <td class=\"entry\" headers=\"configuring-service-graph-connector-nokia-altiplano__table_s1h_kby_vfc__entry__1\">Telecom Service Operations Core</td>\n <td class=\"entry\" headers=\"configuring-service-graph-connector-nokia-altiplano__table_s1h_kby_vfc__entry__2\"><code class=\"ph codeph\">sn_tsom_core</code></td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry\" headers=\"configuring-service-graph-connector-nokia-altiplano__table_s1h_kby_vfc__entry__1\">Pattern Designer</td>\n <td class=\"entry\" headers=\"configuring-service-graph-connector-nokia-altiplano__table_s1h_kby_vfc__entry__2\"><code class=\"ph codeph\">com.snc.pattern.designer</code></td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry\" headers=\"configuring-service-graph-connector-nokia-altiplano__table_s1h_kby_vfc__entry__1\">Discovery Core (automatically installed with Discovery)</td>\n <td class=\"entry\" headers=\"configuring-service-graph-connector-nokia-altiplano__table_s1h_kby_vfc__entry__2\"><code class=\"ph codeph\">com.snc.discovery.core</code></td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry\" headers=\"configuring-service-graph-connector-nokia-altiplano__table_s1h_kby_vfc__entry__1\">ITOM Discovery License</td>\n <td class=\"entry\" headers=\"configuring-service-graph-connector-nokia-altiplano__table_s1h_kby_vfc__entry__2\"><code class=\"ph codeph\">com.snc.itom.discovery.license</code></td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry\" headers=\"configuring-service-graph-connector-nokia-altiplano__table_s1h_kby_vfc__entry__1\">ITOM Licensing</td>\n <td class=\"entry\" headers=\"configuring-service-graph-connector-nokia-altiplano__table_s1h_kby_vfc__entry__2\"><code class=\"ph codeph\">com.snc.itom.license</code></td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry\" headers=\"configuring-service-graph-connector-nokia-altiplano__table_s1h_kby_vfc__entry__1\">IntegrationHub ETL (for development environments only)</td>\n <td class=\"entry\" headers=\"configuring-service-graph-connector-nokia-altiplano__table_s1h_kby_vfc__entry__2\"><code class=\"ph codeph\">sn_int_studio</code></td>\n </tr>\n </tbody></table></div>\n <div class=\"note note note_note\"><span class=\"note__title\">Note:</span> External requirements:<ul class=\"ul\" id=\"configuring-service-graph-connector-nokia-altiplano__ul_x2w_pby_vfc\">\n <li class=\"li\">A running Nokia Altiplano Controller instance with access to its REST northbound API.</li>\n <li class=\"li\">A MID Server with secure connectivity to the Altiplano instance.</li>\n </ul></div>\n </section>\n <section class=\"section\" id=\"configuring-service-graph-connector-nokia-altiplano__section_xxb_vby_vfc\"><h2 id=\"d9282e153\" class=\"title sectiontitle\">Configuration tasks overview</h2>\n \n <p class=\"p\">The following sections are available under the Nokia Altiplano navigation pane. Use the following table for post-guided setup or perform manual configurations.</p>\n <div class=\"table-wrap\"><table count-columns=\"2\" class=\"table\" id=\"configuring-service-graph-connector-nokia-altiplano__table_pyy_vby_vfc\"><caption></caption><colgroup><col/><col/></colgroup><thead class=\"thead\">\n <tr class=\"row\">\n <th class=\"entry\" id=\"configuring-service-graph-connector-nokia-altiplano__table_pyy_vby_vfc__entry__1\">Section</th>\n <th class=\"entry\" id=\"configuring-service-graph-connector-nokia-altiplano__table_pyy_vby_vfc__entry__2\">Description</th>\n </tr>\n </thead><tbody class=\"tbody\">\n <tr class=\"row\">\n <td class=\"entry\" headers=\"configuring-service-graph-connector-nokia-altiplano__table_pyy_vby_vfc__entry__1\">Setup</td>\n <td class=\"entry\" headers=\"configuring-service-graph-connector-nokia-altiplano__table_pyy_vby_vfc__entry__2\">Configure MID Server, define Altiplano connections, and schedule imports.</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry\" headers=\"configuring-service-graph-connector-nokia-altiplano__table_pyy_vby_vfc__entry__1\">Data Sources</td>\n <td class=\"entry\" headers=\"configuring-service-graph-connector-nokia-altiplano__table_pyy_vby_vfc__entry__2\">Predefined data sources for bulk and filtered discovery (SGC-Nokia Altiplano Bulk Discovery, SGC-Nokia Altiplano Filtering Discovery). Enable parallel loading if needed. For more information on parallel loading, see <a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/task/configure-concurrent-import-and-parallel-loading.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/configure-concurrent-import-and-parallel-loading.html\" class=\"xref\" title=\"Improve the efficiency of large data imports from Nokia Altiplano by configuring concurrent imports and enabling parallel loading. This configuration allows the platform to run multiple data import and transformation jobs simultaneously.\">Configure concurrent import and parallel loading for Nokia Altiplano</a>.</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry\" headers=\"configuring-service-graph-connector-nokia-altiplano__table_pyy_vby_vfc__entry__1\">Import Schedules</td>\n <td class=\"entry\" headers=\"configuring-service-graph-connector-nokia-altiplano__table_pyy_vby_vfc__entry__2\">Manage scheduling for each Altiplano connection alias. Run jobs manually or at defined intervals.</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry\" headers=\"configuring-service-graph-connector-nokia-altiplano__table_pyy_vby_vfc__entry__1\">Connections & Credential Aliases</td>\n <td class=\"entry\" headers=\"configuring-service-graph-connector-nokia-altiplano__table_pyy_vby_vfc__entry__2\">Define aliases for each Altiplano instance. Store connection metadata and credentials.</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry\" headers=\"configuring-service-graph-connector-nokia-altiplano__table_pyy_vby_vfc__entry__1\">Connections</td>\n <td class=\"entry\" headers=\"configuring-service-graph-connector-nokia-altiplano__table_pyy_vby_vfc__entry__2\">Define Altiplano instance details, such as URL, selected MID Server, credential reference, and connection alias reference.</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry\" headers=\"configuring-service-graph-connector-nokia-altiplano__table_pyy_vby_vfc__entry__1\">Credentials</td>\n <td class=\"entry\" headers=\"configuring-service-graph-connector-nokia-altiplano__table_pyy_vby_vfc__entry__2\">Create Altiplano credentials using Basic Auth.</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry\" headers=\"configuring-service-graph-connector-nokia-altiplano__table_pyy_vby_vfc__entry__1\">Filters</td>\n <td class=\"entry\" headers=\"configuring-service-graph-connector-nokia-altiplano__table_pyy_vby_vfc__entry__2\">Configure filtering parameters used in filtered discovery (for example, by device IP or name).</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry\" headers=\"configuring-service-graph-connector-nokia-altiplano__table_pyy_vby_vfc__entry__1\">Properties</td>\n <td class=\"entry\" headers=\"configuring-service-graph-connector-nokia-altiplano__table_pyy_vby_vfc__entry__2\">Modify system behavior using connector-specific properties. For more information, see <a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/reference/properties-installed-with-nokia-altiplano.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/reference/properties-installed-with-nokia-altiplano.html\" class=\"xref\" title=\"System properties control how the connector operates, including discovery options and performance settings.\">System components installed with Nokia Altiplano</a>.</td>\n </tr>\n </tbody></table></div>\n </section>\n <section class=\"section\" id=\"configuring-service-graph-connector-nokia-altiplano__section_opx_lcy_vfc\"><h2 id=\"d9282e274\" class=\"title sectiontitle\">Supported Nokia Altiplano versions</h2>\n \n <div class=\"p\">\n <ul class=\"ul\" id=\"configuring-service-graph-connector-nokia-altiplano__ul_ppx_lcy_vfc\">\n <li class=\"li\">Minimum supported version: 24.6</li>\n <li class=\"li\">Supported OLT: Lightspan MF-2</li>\n </ul>\n <div class=\"note note note_note\"><span class=\"note__title\">Note:</span> Fore more information, see <a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept/data-mapping.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/data-mapping.html\" class=\"xref\" title=\"Use the Service Graph Connector for Nokia Altiplano to map discovered physical and logical network resources to telecom-aligned Configuration Item (CI) classes in the CMDB. The connector supports consistent service modeling, visibility into chassis-level components, and automation of logical and physical relationships.\">Mapping Nokia Altiplano CIs and Relationships in CMDB</a>.</div>\n </div>\n </section>\n <section class=\"section\" id=\"configuring-service-graph-connector-nokia-altiplano__section_uyj_rz1_wfc\"><h2 id=\"d9282e302\" class=\"title sectiontitle\">Access the Guided Setup</h2>\n \n <p class=\"p\">Use the guided setup to simplify the configuration process. This setup provides an organized sequence of steps to help you complete integration quickly and correctly. To access the guided setup:</p>\n <ol class=\"ol\" id=\"configuring-service-graph-connector-nokia-altiplano__ol_vyj_rz1_wfc\">\n <li class=\"li\">Navigate to <span class=\"ph menucascade\"><span class=\"ph uicontrol\">All</span><abbr> > </abbr><span class=\"ph uicontrol\">Service Graph Connectors</span><abbr> > </abbr><span class=\"ph uicontrol\">Nokia Altiplano</span><abbr> > </abbr><span class=\"ph uicontrol\">Setup</span></span>.</li>\n <li class=\"li\">Follow the task sequence to configure MID Server settings, Nokia Altiplano connections, filters, and import schedules. For more information, see <a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/task/initial-setup-procedure.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/initial-setup-procedure.html\" class=\"xref\" title=\"Learn how to install and configure the Service Graph Connector for Nokia Altiplano, including optional demo data, connectivity setup, and data collection schedules.\">Install and configure the Nokia Altiplano</a>.</li>\n </ol>\n </section>\n </div>\n <nav role=\"navigation\"></nav><nav role=\"navigation\" class=\"tasksNavigation\"></nav><nav role=\"navigation\" class=\"related-links\"><div class=\"col-md-4\"><dt>Related tasks</dt><dd><ul><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/task/initial-setup-procedure.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/initial-setup-procedure.html\" class=\"link\" title=\"Learn how to install and configure the Service Graph Connector for Nokia Altiplano, including optional demo data, connectivity setup, and data collection schedules.\">Install and configure the Nokia Altiplano</a></li><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/task/multi-instance-setup.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/multi-instance-setup.html\" class=\"link\" title=\"Learn how to configure and manage multiple Nokia Altiplano instances within a single ServiceNow environment. This enables administrators and integrators to create independent connection aliases and import schedules customized to specific filtering or frequency needs.\">Set up multiple Nokia Altiplano instances</a></li><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/task/configure-concurrent-import-and-parallel-loading.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/configure-concurrent-import-and-parallel-loading.html\" class=\"link\" title=\"Improve the efficiency of large data imports from Nokia Altiplano by configuring concurrent imports and enabling parallel loading. This configuration allows the platform to run multiple data import and transformation jobs simultaneously.\">Configure concurrent import and parallel loading for Nokia Altiplano</a></li><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/task/run-and-verify-import-for-nokia-altiplano-service-graph-connector.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/run-and-verify-import-for-nokia-altiplano-service-graph-connector.html\" class=\"link\" title=\"Manually execute a configured import schedule for the Nokia Altiplano Service Graph Connector. You can also execute the import to validate the connector setup, run ad-hoc imports, or test newly configured connection aliases. This task helps ensure that data from Altiplano is successfully imported or updated in the CMDB.\">Run and verify import for Nokia Altiplano Service Graph Connector</a></li></ul></dd></div><div class=\"col-md-4\"><dt>Related concepts</dt><dd><ul><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept/data-mapping.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/data-mapping.html\" class=\"link\" title=\"Use the Service Graph Connector for Nokia Altiplano to map discovered physical and logical network resources to telecom-aligned Configuration Item (CI) classes in the CMDB. The connector supports consistent service modeling, visibility into chassis-level components, and automation of logical and physical relationships.\">Mapping Nokia Altiplano CIs and Relationships in CMDB</a></li><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept/service-graph-connector-for-nokia-altiplano.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/service-graph-connector-for-nokia-altiplano.html\" class=\"link\" title=\"The Service Graph Connector for Nokia Altiplano offers a telecom-aware integration that brings real-time network inventory from the Nokia Altiplano Access Network SDN Controller into your ServiceNow CMDB.\">Telecom Discovery via Nokia Altiplano</a></li></ul></dd></div><div class=\"col-md-4\"><dt>Related reference</dt><dd><ul><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/reference/properties-installed-with-nokia-altiplano.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/reference/properties-installed-with-nokia-altiplano.html\" class=\"link\" title=\"System properties control how the connector operates, including discovery options and performance settings.\">System components installed with Nokia Altiplano</a></li></ul></dd></div></nav>\n</article></main></body></article>",
"topic_language": "enus",
"views": 0,
"your_rating": null
} | # Configuring Nokia Altiplano service graph connector
Configure the Nokia Altiplano service graph connector to import physical and logical inventory data from the Nokia Altiplano Access Network SDN Controller into your ServiceNow Configuration Management Database
(CMDB).
This integration uses REST APIs (via a MID Server) to ensure the CMDB reflects accurate, up-to-date telecom inventory aligned with the TM Forum-based data model.Note: A valid Telecommunications Service Operations Management subscription is required to use this connector.
## Required plugins
| Plugin | ID |
| --- | --- |
| Telecom Service Operations Core | `sn_tsom_core` |
| Pattern Designer | `com.snc.pattern.designer` |
| Discovery Core (automatically installed with Discovery) | `com.snc.discovery.core` |
| ITOM Discovery License | `com.snc.itom.discovery.license` |
| ITOM Licensing | `com.snc.itom.license` |
| IntegrationHub ETL (for development environments only) | `sn_int_studio` |
Note: External requirements:
* A running Nokia Altiplano Controller instance with access to its REST northbound API.
* A MID Server with secure connectivity to the Altiplano instance.
## Configuration tasks overview
The following sections are available under the Nokia Altiplano navigation pane. Use the following table for post-guided setup or perform manual configurations.
| Section | Description |
| --- | --- |
| Setup | Configure MID Server, define Altiplano connections, and schedule imports. |
| Data Sources | Predefined data sources for bulk and filtered discovery (SGC-Nokia Altiplano Bulk Discovery, SGC-Nokia Altiplano Filtering Discovery). Enable parallel loading if needed. For more information on parallel loading, see Configure concurrent import and parallel loading for Nokia Altiplano. |
| Import Schedules | Manage scheduling for each Altiplano connection alias. Run jobs manually or at defined intervals. |
| Connections & Credential Aliases | Define aliases for each Altiplano instance. Store connection metadata and credentials. |
| Connections | Define Altiplano instance details, such as URL, selected MID Server, credential reference, and connection alias reference. |
| Credentials | Create Altiplano credentials using Basic Auth. |
| Filters | Configure filtering parameters used in filtered discovery (for example, by device IP or name). |
| Properties | Modify system behavior using connector-specific properties. For more information, see System components installed with Nokia Altiplano. |
## Supported Nokia Altiplano versions
* Minimum supported version: 24.6
* Supported OLT: Lightspan MF-2
Note: Fore more information, see Mapping Nokia Altiplano CIs and Relationships in CMDB.
## Access the Guided Setup
Use the guided setup to simplify the configuration process. This setup provides an organized sequence of steps to help you complete integration quickly and correctly. To access the guided setup:
1. Navigate to All > Service Graph Connectors > Nokia Altiplano > Setup.
2. Follow the task sequence to configure MID Server settings, Nokia Altiplano connections, filters, and import schedules. For more information, see Install and configure the Nokia Altiplano.
| ---
title: Configuring Nokia Altiplano service graph connector
description: Configure the Nokia Altiplano service graph connector to import physical
and logical inventory data from the Nokia Altiplano Access Network SDN Controller
into your ServiceNow Configuration Management Database (CMDB).
keywords: []
breadcrumbs:
- Telecommunications Service Operations Management
- Configuring Telecommunications Service Operations Management
- Set up Telecom Visibility
---
# Configuring Nokia Altiplano service graph connector
Configure the Nokia Altiplano service graph connector to import physical and logical inventory data from the Nokia Altiplano Access Network SDN Controller into your ServiceNow Configuration Management Database
(CMDB).
This integration uses REST APIs (via a MID Server) to ensure the CMDB reflects accurate, up-to-date telecom inventory aligned with the TM Forum-based data model.Note: A valid Telecommunications Service Operations Management subscription is required to use this connector.
## Required plugins
| Plugin | ID |
| --- | --- |
| Telecom Service Operations Core | `sn_tsom_core` |
| Pattern Designer | `com.snc.pattern.designer` |
| Discovery Core (automatically installed with Discovery) | `com.snc.discovery.core` |
| ITOM Discovery License | `com.snc.itom.discovery.license` |
| ITOM Licensing | `com.snc.itom.license` |
| IntegrationHub ETL (for development environments only) | `sn_int_studio` |
Note: External requirements:
* A running Nokia Altiplano Controller instance with access to its REST northbound API.
* A MID Server with secure connectivity to the Altiplano instance.
## Configuration tasks overview
The following sections are available under the Nokia Altiplano navigation pane. Use the following table for post-guided setup or perform manual configurations.
| Section | Description |
| --- | --- |
| Setup | Configure MID Server, define Altiplano connections, and schedule imports. |
| Data Sources | Predefined data sources for bulk and filtered discovery (SGC-Nokia Altiplano Bulk Discovery, SGC-Nokia Altiplano Filtering Discovery). Enable parallel loading if needed. For more information on parallel loading, see Configure concurrent import and parallel loading for Nokia Altiplano. |
| Import Schedules | Manage scheduling for each Altiplano connection alias. Run jobs manually or at defined intervals. |
| Connections & Credential Aliases | Define aliases for each Altiplano instance. Store connection metadata and credentials. |
| Connections | Define Altiplano instance details, such as URL, selected MID Server, credential reference, and connection alias reference. |
| Credentials | Create Altiplano credentials using Basic Auth. |
| Filters | Configure filtering parameters used in filtered discovery (for example, by device IP or name). |
| Properties | Modify system behavior using connector-specific properties. For more information, see System components installed with Nokia Altiplano. |
## Supported Nokia Altiplano versions
* Minimum supported version: 24.6
* Supported OLT: Lightspan MF-2
Note: Fore more information, see Mapping Nokia Altiplano CIs and Relationships in CMDB.
## Access the Guided Setup
Use the guided setup to simplify the configuration process. This setup provides an organized sequence of steps to help you complete integration quickly and correctly. To access the guided setup:
1. Navigate to All > Service Graph Connectors > Nokia Altiplano > Setup.
2. Follow the task sequence to configure MID Server settings, Nokia Altiplano connections, filters, and import schedules. For more information, see Install and configure the Nokia Altiplano.
|
https://www.servicenow.com/docs/en-US/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/configuring-telecommunications-api-notifications.html | https://servicenow-be-prod.servicenow.com/api/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/configuring-telecommunications-api-notifications.html | 2025-08-02 | daily | 0.5 | 268.xml | en-US | zurich-telecom-service-ops | product/tmt-telecom-service-operations-mgt/concept/configuring-telecommunications-api-notifications.html | zurich | Configuring Telecommunications API notifications | Configure the Telecommunications API notification in the ServiceNow instance. | [] | [
"Telecommunications Service Operations Management",
"Configuring Telecommunications Service Operations Management"
] | <article class="hascomments" data-page="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/configuring-telecommunications-api-notifications.html" id="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/configuring-telecommunications-api-notifications.html"><body id="configuring-telecommunications-api-notifications"><main role="main"><article role="article" class="dita" id="configuring-telecommunications-api-notifications" aria-labelledby="title_configuring-telecommunications-api-notifications">
<h1 class="title topictitle1" id="title_configuring-telecommunications-api-notifications">Configuring Telecommunications API notifications</h1>
<div class="body conbody"><p class="shortdesc">Configure the Telecommunications API notification in the <span class="ph">ServiceNow</span> instance.</p>
<section class="section" id="configuring-telecommunications-api-notifications__section_wf3_bz1_dzb"><h2 id="d6318e45" class="title sectiontitle">Modeling the Telecommunications API notification workflow</h2>
<p class="p">The following steps help to configure the Telecommunications API notification in the <span class="ph">ServiceNow</span> instance.</p>
<div class="p">
<ol class="ol" id="configuring-telecommunications-api-notifications__ol_xts_cz1_dzb">
<li class="li"><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/task/create-topic-API-notification.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/create-topic-API-notification.html" class="xref" title="Create a topic and publish the incoming notifications from the external system to the topic. By creating the topics, subscribers can select the topics to which they want to subscribe.">Create a topic</a>: You can create topics either by manually typing the external message details or automatically collecting the available topics from the external system.</li>
<li class="li"><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/task/create-subscription-api-notification.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/create-subscription-api-notification.html" class="xref" title="Subscribe to the topic in the ServiceNow AI Platform that you want respond to the incoming notification from the external system. By subscribing to the topic, the subscriber receives the notifications based on the topics that you subscribe to.">Create a topic subscription</a>: You subscribe to the available topics for incoming notifications from the external system, based on the customer preference. Additionally, you generate the callback URL and register
the subscription.</li>
<li class="li"><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/task/activate-endpoint-in-the-telecommunications-alarm-management-open-api.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/activate-endpoint-in-the-telecommunications-alarm-management-open-api.html" class="xref" title="Activate the endpoint of the Telecommunications Alarm Management Open API connection. By activating the endpoint, you receive the incoming notifications from the external system for the topic that you registered.">Activate the endpoint of the Telecommunications Alarm Management Open API connection</a>: To receive responses from the external system, activate the subscribed endpoints of the Telecommunications Alarm Management Open API connection in the <span class="ph">Workflow Studio</span>.</li>
<li class="li">Provide the callback URL to the external system for receiving notifications. Customer can also reuse the callback URL. When requests from TMF 688 hit the Callback URL, it initiates the
<span class="keyword apiname">Default Alarm Event Notification Trigger</span> flow to create an event.<p class="p">To learn more about the functions to handle Event Notification Management Open API requests that are triggered by external trigger definitions to
create, update, and delete events, see <a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/concept//csh" href="https://servicenow-be-prod.servicenow.com/csh?topicname=event_open-api&version=zurich&pubname=zurich-api-reference" class="xref">Event Notification Management Open API</a> and <a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/concept//csh" href="https://servicenow-be-prod.servicenow.com/csh?topicname=tmftopiceventapiutiloobScopedAPI&version=zurich&pubname=zurich-api-reference" class="xref">TMFTopicEventAPIUtilOOB - Scoped</a>.</p></li>
</ol>
</div>
<p class="p">This workflow creates an event in the <span class="ph">Event Management</span> application. To learn more about using <span class="ph">Event Management</span>, see <a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/concept//csh" href="https://servicenow-be-prod.servicenow.com/csh?topicname=c_EM&version=zurich&pubname=zurich-it-operations-management" class="xref">Event Management</a>.</p>
</section>
</div>
<nav role="navigation"></nav><nav role="navigation" class="tasksNavigation"></nav><nav role="navigation" class="related-links"><div class="col-md-4"><dt>Related concepts</dt><dd><ul><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/concept/telecommunications-api-notification.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/telecommunications-api-notification.html" class="link" title="Use the Telecommunications API notification to receive the external events that occurring in the customer network system so that you can promptly respond to them in the ServiceNow.">External event management via Telecommunications API notifications</a></li></ul></dd></div><div class="col-md-4"><dt>Related reference</dt><dd><ul><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/reference/alarm-management-user-roles.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/reference/alarm-management-user-roles.html" class="link" title="Administrators can assign user roles to grant access to the API notification database tables. The following standard roles for the Topic [sn_api_notif_mgmt_topic] and Topic Subscription [sn_api_notif_mgmt_subscription] tables are included in the ServiceNow system.">System components installed with Telecommunications API notifications</a></li></ul></dd></div></nav>
</article></main></body></article> | {
"attachments": {
"all_attachments": null,
"topic_attachments": []
},
"available_languages": [
"enus"
],
"breadcrumbs": [
{
"title": "Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html"
},
{
"title": "Configuring Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/configuring-tsom.html"
}
],
"breadcrumbs_html": "<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops\">Zurich Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html\">Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/configuring-tsom.html\">Configuring Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<span class=\"active\">Configuring Telecommunications API notifications</span>",
"bundle_id": "zurich-telecom-service-ops",
"bundle_key": 2733,
"bundle_landing_page": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html",
"bundle_subtitle": null,
"bundle_title": "Zurich Telecommunications Service Operations Management",
"canonical_link": null,
"dates": {
"Added on": "2025-08-02T00:48:08.794016Z",
"Created on": "2025-06-24T00:00:00Z",
"Initial upload": "2025-07-30T22:24:33.519043Z",
"Updated on": "2025-07-31T00:00:00Z"
},
"dislike_url": "https://servicenow-be-prod.servicenow.com/dislike/55686928",
"dislikes": 0,
"es_archived_content": false,
"is_in_fav": false,
"is_liked": null,
"is_watched": false,
"keywords": [
" zurich zurich"
],
"labels": [
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "zurich",
"navtitle": "Zurich",
"outputclasses": [],
"subjectHeadId": "versions",
"subjectheadNavtitle": "Versions",
"visibility": "show-facet"
},
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "tsom",
"navtitle": "Telecommunications Service Operations Management",
"outputclasses": [],
"subjectHeadId": "products",
"subjectheadNavtitle": "Products",
"visibility": "show-facet"
}
],
"labels_text": "Versions > Zurich; Products > CRM and Industry Products > Telecommunications Media and Technology Assurance > Telecommunications Service Operations Management",
"like_url": "https://servicenow-be-prod.servicenow.com/like/55686928",
"likes": 0,
"metadata": {
"AI Search": null,
"AI Search Assist": null,
"Application Insights": null,
"Capabilities": null,
"Code Signing": null,
"Contextual Search": null,
"DC.contributor": null,
"DC.coverage": null,
"DC.creator": "ServiceNow",
"DC.date.created": "2025-06-24T16:41:43+05:30",
"DC.date.modified": "2025-07-31",
"DC.format": "HTML5",
"DC.identifier": "configuring-telecommunications-api-notifications",
"DC.language": null,
"DC.relation": "../reference/alarm-management-user-roles.html",
"DC.rights.owner": "(C) Copyright 2025",
"DC.subject": null,
"DC.type": "concept",
"Data Discovery": null,
"Data Policy": null,
"Data Privacy": null,
"Discovery": null,
"External Content for AI Search": null,
"Field Administration": null,
"Field Normalization": null,
"Key Management Framework": null,
"Localization Framework": null,
"Now Platform": null,
"PlatSec": null,
"Platform": null,
"Platform Administration": null,
"Platform Performance": null,
"Platform Privacy": null,
"Proactive Triggers": null,
"Process Optimization": null,
"RN doc editing record number": null,
"Search Administration": null,
"Secrets Management": null,
"ServiceNow AI Platform": null,
"State Model": null,
"Subscription Management": null,
"Task Communications Management": null,
"Timeline Visualizations": null,
"User Administration": null,
"User Experience Analytics": null,
"Zing": null,
"ai-now-assist": null,
"app-name": null,
"app_route": null,
"azureapimanagemen": null,
"change-completed": null,
"change-item": null,
"change-request-id": null,
"change-request-reference": null,
"com.glide.embedded_help.category": null,
"component": null,
"copyright": "(C) Copyright 2025",
"crossroads": null,
"data": null,
"description": "Configure the Telecommunications API notification in the ServiceNow instance.",
"dominant_bundle": null,
"erp-canvas-video": null,
"fsm-mobile": null,
"fsm-route": null,
"fsm-sched-opt": null,
"fsm-wrk-order": null,
"genai-round-7": null,
"generator": "DITA-OT",
"glossPartOfSpeech": null,
"glossStatus": null,
"guided setup": null,
"guided tours": null,
"keywords": null,
"min-toc": null,
"mini": null,
"mini-to truec": null,
"mini-toc": "yes",
"mini_toc": null,
"minitoc": null,
"modification": null,
"now-assist-app-gen-video": null,
"order": null,
"page-type": null,
"page-type ": null,
"prodname": null,
"product": null,
"product_name": null,
"release": null,
"resourceID": null,
"roles": null,
"route_page": null,
"route_params_listId": null,
"route_params_table": null,
"route_params_type": null,
"route_type": null,
"setconfigurationproperties": null,
"topic": null,
"translation-type": "source",
"version": null,
"workflow": "Customer and Industry",
"workplace-srvc-delvry-ditamap": null
},
"page_id": "product/tmt-telecom-service-operations-mgt/concept/configuring-telecommunications-api-notifications.html",
"page_key": 55686928,
"preprocessed_PDF": "https://downloads.docs.servicenow.com/pdf/enus/servicenow-zurich-telecom-service-ops-enus.pdf",
"rating": null,
"read_time_data": {
"char_count": 1559,
"img_count": 0,
"read_time": 1,
"video_links": [
""
],
"word_count": 224
},
"related_links": [
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "Administrators can assign user roles to grant access to the API notification database tables. The following standard roles for the Topic [sn_api_notif_mgmt_topic] and Topic Subscription [sn_api_notif_mgmt_subscription] tables are included in the ServiceNow system.",
"title": "System components installed with Telecommunications API notifications",
"topic": "/product/tmt-telecom-service-operations-mgt/reference/alarm-management-user-roles.html",
"type": "reference",
"url": null
},
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "Use the Telecommunications API notification to receive the external events that occurring in the customer network system so that you can promptly respond to them in the ServiceNow.",
"title": "External event management via Telecommunications API notifications",
"topic": "/product/tmt-telecom-service-operations-mgt/concept/telecommunications-api-notification.html",
"type": "concept",
"url": null
}
],
"search_title": null,
"title": "Configuring Telecommunications API notifications",
"topic_cluster": {
"clustered_by": {
"enabled": true,
"primary_key": "versions",
"primary_sort": "top-down",
"type": "subjecthead"
},
"clustered_labels": [
"versions"
],
"clustered_topics": [],
"clustering_title": "Zurich"
},
"topic_html": "<article class=\"hascomments\" data-page=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/configuring-telecommunications-api-notifications.html\" id=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/configuring-telecommunications-api-notifications.html\"><body id=\"configuring-telecommunications-api-notifications\"><main role=\"main\"><article role=\"article\" class=\"dita\" id=\"configuring-telecommunications-api-notifications\" aria-labelledby=\"title_configuring-telecommunications-api-notifications\">\n <h1 class=\"title topictitle1\" id=\"title_configuring-telecommunications-api-notifications\">Configuring Telecommunications API notifications</h1>\n \n \n <div class=\"body conbody\"><p class=\"shortdesc\">Configure the Telecommunications API notification in the <span class=\"ph\">ServiceNow</span> instance.</p>\n <section class=\"section\" id=\"configuring-telecommunications-api-notifications__section_wf3_bz1_dzb\"><h2 id=\"d6318e45\" class=\"title sectiontitle\">Modeling the Telecommunications API notification workflow</h2>\n \n <p class=\"p\">The following steps help to configure the Telecommunications API notification in the <span class=\"ph\">ServiceNow</span> instance.</p>\n <div class=\"p\">\n <ol class=\"ol\" id=\"configuring-telecommunications-api-notifications__ol_xts_cz1_dzb\">\n <li class=\"li\"><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/task/create-topic-API-notification.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/create-topic-API-notification.html\" class=\"xref\" title=\"Create a topic and publish the incoming notifications from the external system to the topic. By creating the topics, subscribers can select the topics to which they want to subscribe.\">Create a topic</a>: You can create topics either by manually typing the external message details or automatically collecting the available topics from the external system.</li>\n <li class=\"li\"><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/task/create-subscription-api-notification.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/create-subscription-api-notification.html\" class=\"xref\" title=\"Subscribe to the topic in the ServiceNow AI Platform that you want respond to the incoming notification from the external system. By subscribing to the topic, the subscriber receives the notifications based on the topics that you subscribe to.\">Create a topic subscription</a>: You subscribe to the available topics for incoming notifications from the external system, based on the customer preference. Additionally, you generate the callback URL and register\n the subscription.</li>\n <li class=\"li\"><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/task/activate-endpoint-in-the-telecommunications-alarm-management-open-api.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/activate-endpoint-in-the-telecommunications-alarm-management-open-api.html\" class=\"xref\" title=\"Activate the endpoint of the Telecommunications Alarm Management Open API connection. By activating the endpoint, you receive the incoming notifications from the external system for the topic that you registered.\">Activate the endpoint of the Telecommunications Alarm Management Open API connection</a>: To receive responses from the external system, activate the subscribed endpoints of the Telecommunications Alarm Management Open API connection in the <span class=\"ph\">Workflow Studio</span>.</li>\n \n \n <li class=\"li\">Provide the callback URL to the external system for receiving notifications. Customer can also reuse the callback URL. When requests from TMF 688 hit the Callback URL, it initiates the\n <span class=\"keyword apiname\">Default Alarm Event Notification Trigger</span> flow to create an event.<p class=\"p\">To learn more about the functions to handle Event Notification Management Open API requests that are triggered by external trigger definitions to\n create, update, and delete events, see <a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept//csh\" href=\"https://servicenow-be-prod.servicenow.com/csh?topicname=event_open-api&version=zurich&pubname=zurich-api-reference\" class=\"xref\">Event Notification Management Open API</a> and <a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept//csh\" href=\"https://servicenow-be-prod.servicenow.com/csh?topicname=tmftopiceventapiutiloobScopedAPI&version=zurich&pubname=zurich-api-reference\" class=\"xref\">TMFTopicEventAPIUtilOOB - Scoped</a>.</p></li>\n </ol>\n </div>\n <p class=\"p\">This workflow creates an event in the <span class=\"ph\">Event Management</span> application. To learn more about using <span class=\"ph\">Event Management</span>, see <a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept//csh\" href=\"https://servicenow-be-prod.servicenow.com/csh?topicname=c_EM&version=zurich&pubname=zurich-it-operations-management\" class=\"xref\">Event Management</a>.</p>\n </section>\n </div>\n <nav role=\"navigation\"></nav><nav role=\"navigation\" class=\"tasksNavigation\"></nav><nav role=\"navigation\" class=\"related-links\"><div class=\"col-md-4\"><dt>Related concepts</dt><dd><ul><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept/telecommunications-api-notification.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/telecommunications-api-notification.html\" class=\"link\" title=\"Use the Telecommunications API notification to receive the external events that occurring in the customer network system so that you can promptly respond to them in the ServiceNow.\">External event management via Telecommunications API notifications</a></li></ul></dd></div><div class=\"col-md-4\"><dt>Related reference</dt><dd><ul><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/reference/alarm-management-user-roles.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/reference/alarm-management-user-roles.html\" class=\"link\" title=\"Administrators can assign user roles to grant access to the API notification database tables. The following standard roles for the Topic [sn_api_notif_mgmt_topic] and Topic Subscription [sn_api_notif_mgmt_subscription] tables are included in the ServiceNow system.\">System components installed with Telecommunications API notifications</a></li></ul></dd></div></nav>\n</article></main></body></article>",
"topic_language": "enus",
"views": 0,
"your_rating": null
} | # Configuring Telecommunications API notifications
Configure the Telecommunications API notification in the ServiceNow instance.
## Modeling the Telecommunications API notification workflow
The following steps help to configure the Telecommunications API notification in the ServiceNow instance.
1. Create a topic: You can create topics either by manually typing the external message details or automatically collecting the available topics from the external system.
2. Create a topic subscription: You subscribe to the available topics for incoming notifications from the external system, based on the customer preference. Additionally, you generate the callback URL and register
the subscription.
3. Activate the endpoint of the Telecommunications Alarm Management Open API connection: To receive responses from the external system, activate the subscribed endpoints of the Telecommunications Alarm Management Open API connection in the Workflow Studio.
4. Provide the callback URL to the external system for receiving notifications. Customer can also reuse the callback URL. When requests from TMF 688 hit the Callback URL, it initiates the
Default Alarm Event Notification Trigger flow to create an event.
To learn more about the functions to handle Event Notification Management Open API requests that are triggered by external trigger definitions to
create, update, and delete events, see Event Notification Management Open API and TMFTopicEventAPIUtilOOB - Scoped.
This workflow creates an event in the Event Management application. To learn more about using Event Management, see Event Management.
| ---
title: Configuring Telecommunications API notifications
description: Configure the Telecommunications API notification in the ServiceNow instance.
keywords: []
breadcrumbs:
- Telecommunications Service Operations Management
- Configuring Telecommunications Service Operations Management
---
# Configuring Telecommunications API notifications
Configure the Telecommunications API notification in the ServiceNow instance.
## Modeling the Telecommunications API notification workflow
The following steps help to configure the Telecommunications API notification in the ServiceNow instance.
1. Create a topic: You can create topics either by manually typing the external message details or automatically collecting the available topics from the external system.
2. Create a topic subscription: You subscribe to the available topics for incoming notifications from the external system, based on the customer preference. Additionally, you generate the callback URL and register
the subscription.
3. Activate the endpoint of the Telecommunications Alarm Management Open API connection: To receive responses from the external system, activate the subscribed endpoints of the Telecommunications Alarm Management Open API connection in the Workflow Studio.
4. Provide the callback URL to the external system for receiving notifications. Customer can also reuse the callback URL. When requests from TMF 688 hit the Callback URL, it initiates the
Default Alarm Event Notification Trigger flow to create an event.
To learn more about the functions to handle Event Notification Management Open API requests that are triggered by external trigger definitions to
create, update, and delete events, see Event Notification Management Open API and TMFTopicEventAPIUtilOOB - Scoped.
This workflow creates an event in the Event Management application. To learn more about using Event Management, see Event Management.
|
https://www.servicenow.com/docs/en-US/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/configuring-the-telco-generic-schema-etl.html | https://servicenow-be-prod.servicenow.com/api/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/configuring-the-telco-generic-schema-etl.html | 2025-08-02 | daily | 0.5 | 268.xml | en-US | zurich-telecom-service-ops | product/tmt-telecom-service-operations-mgt/concept/configuring-the-telco-generic-schema-etl.html | zurich | Configuring the Telecom Discovery Builder framework ETL in a connector | Leverage the prebuilt Telecom Discovery Builder framework ETL by duplicating it into your connector scope, assigning the appropriate data source, and deploying it as part of a new service graph connector. | [] | [
"Telecommunications Service Operations Management",
"Configuring Telecommunications Service Operations Management",
"Set up Telecom Visibility"
] | <article class="hascomments" data-page="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/configuring-the-telco-generic-schema-etl.html" id="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/configuring-the-telco-generic-schema-etl.html"><body id="configuring-the-telco-generic-schema-etl"><main role="main"><article role="article" class="dita" id="configuring-the-telco-generic-schema-etl" aria-labelledby="title_configuring-the-telco-generic-schema-etl">
<h1 class="title topictitle1" id="title_configuring-the-telco-generic-schema-etl">Configuring the Telecom Discovery Builder framework ETL in a connector</h1>
<div class="body conbody"><p class="shortdesc">Leverage the prebuilt Telecom Discovery Builder framework ETL by duplicating it into your connector scope, assigning the appropriate data source, and deploying it as part of a new service graph connector.</p>
<p class="p">The Telecom Discovery Builder framework ETL provided with the Telecom Service Operations Management (TSOM) Core is a ready-to-use framework designed to streamline data ingestion into the CMDB across telecom connectors. Rather than
configuring it directly, as an administrator, you can duplicate the ETL into a connector’s application scope and update the data source to align with the connector’s discovery payload.</p>
<section class="section" id="configuring-the-telco-generic-schema-etl__section_m1l_5p4_ffc"><h2 id="d9665e45" class="title sectiontitle">Steps to use the Telecom Discovery Builder framework ETL in a connector</h2>
<div class="p">
<ol class="ol" id="configuring-the-telco-generic-schema-etl__ol_uvh_vp4_ffc">
<li class="li">Create a temporary data source: Create a data source in your connector’s application scope based on the Generic Schema multi source data source from TSOM Core. This enables you to run and test the duplicated ETL with schema-aligned
placeholder data. For more information, see <a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/task/create-a-data-source-similar-to-tsom-core-data-source.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/create-a-data-source-similar-to-tsom-core-data-source.html" class="xref" title="Set up a schema-compliant data source in the connector’s application scope to simulate telecom data and ensure successful testing and validation of the Telecom Discovery Builder framework ETL before integrating with live device data.">Create a data source similar to Telecom core data source</a></li>
<li class="li">Duplicate the Telecom Discovery Builder framework ETL: Access ETL Studio, locate the Telco Generic Schema ETL, and duplicate it into the connector’s scope. During duplication: Provide a new name. Assign the temporary data source.
Use importSet as the discovery source. For more information, see <a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/task/duplicate-the-generic-etl-to-use-a-specific-connector.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/duplicate-the-generic-etl-to-use-a-specific-connector.html" class="xref" title="The Telecom Discovery Builder framework ETL enables Service Graph Connector (SGC) teams to rapidly adopt a standardized, schema-compliant data ingestion pipeline without building ETL logic from scratch.">Duplicate the Telecom Discovery Builder framework ETL into a connector scope</a></li>
<li class="li">After duplication, open the new ETL and replace the temporary data source with the connector’s actual discovery data source. For more information, see <a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/task/update-data-source-of-the-connector.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/update-data-source-of-the-connector.html" class="xref" title="Link the duplicated ETL to a valid data source for your specific connector.">Update the data source of the connector</a>.</li>
<li class="li">Test or deploy the service graph connector. For more information, see <a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/task/deploy-a-new-service-graph-connector-with-duplicated-etl.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/deploy-a-new-service-graph-connector-with-duplicated-etl.html" class="xref" title="Associate a new Service Graph Connector (SGC) with an existing ETL.">Deploy a new service graph connector with existing ETL</a></li>
</ol>
</div>
</section>
</div>
</article></main></body></article> | {
"attachments": {
"all_attachments": null,
"topic_attachments": []
},
"available_languages": [
"enus"
],
"breadcrumbs": [
{
"title": "Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html"
},
{
"title": "Configuring Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/configuring-tsom.html"
},
{
"title": "Set up Telecom Visibility",
"topic_id": "product/tmt-telecom-service-operations-mgt/task/configuring-tsom-visibility.html"
}
],
"breadcrumbs_html": "<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops\">Zurich Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html\">Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/configuring-tsom.html\">Configuring Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/configuring-tsom-visibility.html\">Set up Telecom Visibility</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<span class=\"active\">Configuring the Telecom Discovery Builder framework ETL in a connector</span>",
"bundle_id": "zurich-telecom-service-ops",
"bundle_key": 2733,
"bundle_landing_page": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html",
"bundle_subtitle": null,
"bundle_title": "Zurich Telecommunications Service Operations Management",
"canonical_link": null,
"dates": {
"Added on": "2025-08-02T00:48:08.794016Z",
"Created on": "2025-04-14T00:00:00Z",
"Initial upload": "2025-07-30T22:24:33.519043Z",
"Updated on": "2025-07-31T00:00:00Z"
},
"dislike_url": "https://servicenow-be-prod.servicenow.com/dislike/55686929",
"dislikes": 0,
"es_archived_content": false,
"is_in_fav": false,
"is_liked": null,
"is_watched": false,
"keywords": [
" zurich zurich"
],
"labels": [
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "zurich",
"navtitle": "Zurich",
"outputclasses": [],
"subjectHeadId": "versions",
"subjectheadNavtitle": "Versions",
"visibility": "show-facet"
},
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "tsom",
"navtitle": "Telecommunications Service Operations Management",
"outputclasses": [],
"subjectHeadId": "products",
"subjectheadNavtitle": "Products",
"visibility": "show-facet"
}
],
"labels_text": "Versions > Zurich; Products > CRM and Industry Products > Telecommunications Media and Technology Assurance > Telecommunications Service Operations Management",
"like_url": "https://servicenow-be-prod.servicenow.com/like/55686929",
"likes": 0,
"metadata": {
"AI Search": null,
"AI Search Assist": null,
"Application Insights": null,
"Capabilities": null,
"Code Signing": null,
"Contextual Search": null,
"DC.contributor": null,
"DC.coverage": null,
"DC.creator": "ServiceNow",
"DC.date.created": "2025-04-14T13:21:58+05:30",
"DC.date.modified": "2025-07-31",
"DC.format": "HTML5",
"DC.identifier": "configuring-the-telco-generic-schema-etl",
"DC.language": null,
"DC.relation": null,
"DC.rights.owner": "(C) Copyright 2025",
"DC.subject": null,
"DC.type": "concept",
"Data Discovery": null,
"Data Policy": null,
"Data Privacy": null,
"Discovery": null,
"External Content for AI Search": null,
"Field Administration": null,
"Field Normalization": null,
"Key Management Framework": null,
"Localization Framework": null,
"Now Platform": null,
"PlatSec": null,
"Platform": null,
"Platform Administration": null,
"Platform Performance": null,
"Platform Privacy": null,
"Proactive Triggers": null,
"Process Optimization": null,
"RN doc editing record number": null,
"Search Administration": null,
"Secrets Management": null,
"ServiceNow AI Platform": null,
"State Model": null,
"Subscription Management": null,
"Task Communications Management": null,
"Timeline Visualizations": null,
"User Administration": null,
"User Experience Analytics": null,
"Zing": null,
"ai-now-assist": null,
"app-name": null,
"app_route": null,
"azureapimanagemen": null,
"change-completed": null,
"change-item": null,
"change-request-id": null,
"change-request-reference": null,
"com.glide.embedded_help.category": null,
"component": null,
"copyright": "(C) Copyright 2025",
"crossroads": null,
"data": null,
"description": "Leverage the prebuilt Telecom Discovery Builder framework ETL by duplicating it into your connector scope, assigning the appropriate data source, and deploying it as part of a new service graph connector.",
"dominant_bundle": null,
"erp-canvas-video": null,
"fsm-mobile": null,
"fsm-route": null,
"fsm-sched-opt": null,
"fsm-wrk-order": null,
"genai-round-7": null,
"generator": "DITA-OT",
"glossPartOfSpeech": null,
"glossStatus": null,
"guided setup": null,
"guided tours": null,
"keywords": null,
"min-toc": null,
"mini": null,
"mini-to truec": null,
"mini-toc": "yes",
"mini_toc": null,
"minitoc": null,
"modification": null,
"now-assist-app-gen-video": null,
"order": null,
"page-type": null,
"page-type ": null,
"prodname": null,
"product": null,
"product_name": null,
"release": null,
"resourceID": null,
"roles": null,
"route_page": null,
"route_params_listId": null,
"route_params_table": null,
"route_params_type": null,
"route_type": null,
"setconfigurationproperties": null,
"topic": null,
"translation-type": "source",
"version": null,
"workflow": "Customer and Industry",
"workplace-srvc-delvry-ditamap": null
},
"page_id": "product/tmt-telecom-service-operations-mgt/concept/configuring-the-telco-generic-schema-etl.html",
"page_key": 55686929,
"preprocessed_PDF": "https://downloads.docs.servicenow.com/pdf/enus/servicenow-zurich-telecom-service-ops-enus.pdf",
"rating": null,
"read_time_data": {
"char_count": 1730,
"img_count": 0,
"read_time": 1,
"video_links": [
""
],
"word_count": 263
},
"related_links": [],
"search_title": null,
"title": "Configuring the Telecom Discovery Builder framework ETL in a connector",
"topic_cluster": {
"clustered_by": {
"enabled": true,
"primary_key": "versions",
"primary_sort": "top-down",
"type": "subjecthead"
},
"clustered_labels": [
"versions"
],
"clustered_topics": [],
"clustering_title": "Zurich"
},
"topic_html": "<article class=\"hascomments\" data-page=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/configuring-the-telco-generic-schema-etl.html\" id=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/configuring-the-telco-generic-schema-etl.html\"><body id=\"configuring-the-telco-generic-schema-etl\"><main role=\"main\"><article role=\"article\" class=\"dita\" id=\"configuring-the-telco-generic-schema-etl\" aria-labelledby=\"title_configuring-the-telco-generic-schema-etl\">\n <h1 class=\"title topictitle1\" id=\"title_configuring-the-telco-generic-schema-etl\">Configuring the Telecom Discovery Builder framework ETL in a connector</h1>\n \n \n <div class=\"body conbody\"><p class=\"shortdesc\">Leverage the prebuilt Telecom Discovery Builder framework ETL by duplicating it into your connector scope, assigning the appropriate data source, and deploying it as part of a new service graph connector.</p>\n <p class=\"p\">The Telecom Discovery Builder framework ETL provided with the Telecom Service Operations Management (TSOM) Core is a ready-to-use framework designed to streamline data ingestion into the CMDB across telecom connectors. Rather than\n configuring it directly, as an administrator, you can duplicate the ETL into a connector’s application scope and update the data source to align with the connector’s discovery payload.</p>\n <section class=\"section\" id=\"configuring-the-telco-generic-schema-etl__section_m1l_5p4_ffc\"><h2 id=\"d9665e45\" class=\"title sectiontitle\">Steps to use the Telecom Discovery Builder framework ETL in a connector</h2>\n \n <div class=\"p\">\n <ol class=\"ol\" id=\"configuring-the-telco-generic-schema-etl__ol_uvh_vp4_ffc\">\n <li class=\"li\">Create a temporary data source: Create a data source in your connector’s application scope based on the Generic Schema multi source data source from TSOM Core. This enables you to run and test the duplicated ETL with schema-aligned\n placeholder data. For more information, see <a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/task/create-a-data-source-similar-to-tsom-core-data-source.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/create-a-data-source-similar-to-tsom-core-data-source.html\" class=\"xref\" title=\"Set up a schema-compliant data source in the connector’s application scope to simulate telecom data and ensure successful testing and validation of the Telecom Discovery Builder framework ETL before integrating with live device data.\">Create a data source similar to Telecom core data source</a></li>\n <li class=\"li\">Duplicate the Telecom Discovery Builder framework ETL: Access ETL Studio, locate the Telco Generic Schema ETL, and duplicate it into the connector’s scope. During duplication: Provide a new name. Assign the temporary data source.\n Use importSet as the discovery source. For more information, see <a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/task/duplicate-the-generic-etl-to-use-a-specific-connector.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/duplicate-the-generic-etl-to-use-a-specific-connector.html\" class=\"xref\" title=\"The Telecom Discovery Builder framework ETL enables Service Graph Connector (SGC) teams to rapidly adopt a standardized, schema-compliant data ingestion pipeline without building ETL logic from scratch.\">Duplicate the Telecom Discovery Builder framework ETL into a connector scope</a></li>\n <li class=\"li\">After duplication, open the new ETL and replace the temporary data source with the connector’s actual discovery data source. For more information, see <a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/task/update-data-source-of-the-connector.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/update-data-source-of-the-connector.html\" class=\"xref\" title=\"Link the duplicated ETL to a valid data source for your specific connector.\">Update the data source of the connector</a>.</li>\n <li class=\"li\">Test or deploy the service graph connector. For more information, see <a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/task/deploy-a-new-service-graph-connector-with-duplicated-etl.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/deploy-a-new-service-graph-connector-with-duplicated-etl.html\" class=\"xref\" title=\"Associate a new Service Graph Connector (SGC) with an existing ETL.\">Deploy a new service graph connector with existing ETL</a></li>\n </ol>\n </div>\n </section>\n </div>\n</article></main></body></article>",
"topic_language": "enus",
"views": 0,
"your_rating": null
} | # Configuring the Telecom Discovery Builder framework ETL in a connector
Leverage the prebuilt Telecom Discovery Builder framework ETL by duplicating it into your connector scope, assigning the appropriate data source, and deploying it as part of a new service graph connector.
The Telecom Discovery Builder framework ETL provided with the Telecom Service Operations Management (TSOM) Core is a ready-to-use framework designed to streamline data ingestion into the CMDB across telecom connectors. Rather than
configuring it directly, as an administrator, you can duplicate the ETL into a connector’s application scope and update the data source to align with the connector’s discovery payload.
## Steps to use the Telecom Discovery Builder framework ETL in a connector
1. Create a temporary data source: Create a data source in your connector’s application scope based on the Generic Schema multi source data source from TSOM Core. This enables you to run and test the duplicated ETL with schema-aligned
placeholder data. For more information, see Create a data source similar to Telecom core data source
2. Duplicate the Telecom Discovery Builder framework ETL: Access ETL Studio, locate the Telco Generic Schema ETL, and duplicate it into the connector’s scope. During duplication: Provide a new name. Assign the temporary data source.
Use importSet as the discovery source. For more information, see Duplicate the Telecom Discovery Builder framework ETL into a connector scope
3. After duplication, open the new ETL and replace the temporary data source with the connector’s actual discovery data source. For more information, see Update the data source of the connector.
4. Test or deploy the service graph connector. For more information, see Deploy a new service graph connector with existing ETL
| ---
title: Configuring the Telecom Discovery Builder framework ETL in a connector
description: Leverage the prebuilt Telecom Discovery Builder framework ETL by duplicating
it into your connector scope, assigning the appropriate data source, and deploying
it as part of a new service graph connector.
keywords: []
breadcrumbs:
- Telecommunications Service Operations Management
- Configuring Telecommunications Service Operations Management
- Set up Telecom Visibility
---
# Configuring the Telecom Discovery Builder framework ETL in a connector
Leverage the prebuilt Telecom Discovery Builder framework ETL by duplicating it into your connector scope, assigning the appropriate data source, and deploying it as part of a new service graph connector.
The Telecom Discovery Builder framework ETL provided with the Telecom Service Operations Management (TSOM) Core is a ready-to-use framework designed to streamline data ingestion into the CMDB across telecom connectors. Rather than
configuring it directly, as an administrator, you can duplicate the ETL into a connector’s application scope and update the data source to align with the connector’s discovery payload.
## Steps to use the Telecom Discovery Builder framework ETL in a connector
1. Create a temporary data source: Create a data source in your connector’s application scope based on the Generic Schema multi source data source from TSOM Core. This enables you to run and test the duplicated ETL with schema-aligned
placeholder data. For more information, see Create a data source similar to Telecom core data source
2. Duplicate the Telecom Discovery Builder framework ETL: Access ETL Studio, locate the Telco Generic Schema ETL, and duplicate it into the connector’s scope. During duplication: Provide a new name. Assign the temporary data source.
Use importSet as the discovery source. For more information, see Duplicate the Telecom Discovery Builder framework ETL into a connector scope
3. After duplication, open the new ETL and replace the temporary data source with the connector’s actual discovery data source. For more information, see Update the data source of the connector.
4. Test or deploy the service graph connector. For more information, see Deploy a new service graph connector with existing ETL
|
https://www.servicenow.com/docs/en-US/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/configuring-tsom.html | https://servicenow-be-prod.servicenow.com/api/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/configuring-tsom.html | 2025-08-02 | daily | 0.5 | 268.xml | en-US | zurich-telecom-service-ops | product/tmt-telecom-service-operations-mgt/concept/configuring-tsom.html | zurich | Configuring Telecommunications Service Operations Management | Configure Telecommunications Service Operations Management (TSOM) to enable real-time event ingestion, correlation, and automated remediation by integrating with external network monitoring and discovery systems. | [] | [
"Telecommunications Service Operations Management"
] | <article class="hascomments" data-page="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/configuring-tsom.html" id="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/configuring-tsom.html"><body id="configuring-tsom"><main role="main"><article role="article" class="dita" id="configuring-tsom" aria-labelledby="title_configuring-tsom">
<h1 class="title topictitle1" id="title_configuring-tsom">Configuring <span class="ph">Telecommunications Service Operations Management</span></h1>
<div class="body conbody"><p class="shortdesc">Configure <span class="ph">Telecommunications Service Operations Management</span> (TSOM) to enable real-time event ingestion, correlation, and automated remediation by integrating with external network monitoring and discovery systems.</p>
<p class="p">Set up TSOM to enable end-to-end telecom service operations, including alarm ingestion, CMDB population, discrepancy detection, and service impact visibility. This configuration involves activating Telecommunications API
notifications, setting up discovery and service graph connectors, enabling visibility, and configuring audit and reconciliation frameworks.</p>
<section class="section" id="configuring-tsom__section_tvj_gxb_1gc"><h2 id="d10122e50" class="title sectiontitle">Configuration overview</h2>
<div class="p">Telecommunications Service Operations Management (TSOM) requires configuring multiple components across alarm ingestion, discovery, data normalization, and reconciliation to support end-to-end telecom operations. The configuration
flow typically includes:<ol class="ol" id="configuring-tsom__ol_kzz_qhz_bgc">
<li class="li">Activate the following plugins to have TSOM Core in your system<ul class="ul" id="configuring-tsom__ul_iqx_rhz_bgc">
<li class="li">Pattern Designer (com.snc.pattern.designer)</li>
<li class="li">ServiceNow IntegrationHub Started Pack Installer (com.glide.hub.integrations)</li>
<li class="li">Discovery (com.snc.discovery)</li>
<li class="li">CMDB CI Class Models (sn_cmdb_ci_class) 1.69.0</li>
<li class="li">Visibility Content (sn_pattern_design) 6.23.0</li>
<li class="li">Integration Commons for CMDB (sn_cmdb_int_util) 2.19.0</li>
</ul></li>
<li class="li">Enable alarm ingestion: Activate the Telecommunications API notifications and set up topic subscriptions to receive alarms from external systems. For more information, see <a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/concept/configuring-telecommunications-api-notifications.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/configuring-telecommunications-api-notifications.html" class="xref" title="Configure the Telecommunications API notification in the ServiceNow instance.">Configuring Telecommunications API notifications</a>.</li>
<li class="li">Set up visibility: Configure Telecom Visibility to view service-to-infrastructure mappings and monitor network health. For more information, see <a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/task/configuring-tsom-visibility.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/configuring-tsom-visibility.html" class="xref" title="Telecom Visibility provides foundational capabilities that support both Telecom Discovery and Telecom Discrepancy Identification & Reconciliation. It includes shared logic, enhanced CI class models, and Identification and Reconciliation Engine (IRE) updates tailored for telecom network elements.">Set up Telecom Visibility</a><ol class="ol" type="a" id="configuring-tsom__ol_dts_vhz_bgc">
<li class="li">Populate the telecom-aware CMDB:<ul class="ul" id="configuring-tsom__ul_jlf_hxb_1gc">
<li class="li">Install and configure Horizontal Discovery. For more information, see <a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/task/install-horizontal-telecommunication-discoverypatterns.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/install-horizontal-telecommunication-discoverypatterns.html" class="xref" title="Install Horizontal Discovery patterns understanding the dependencies and requirements.">Install Horizontal Discovery and set up Discovery Patterns</a>.</li>
<li class="li">Set up Telecom Discovery Builder (TDB) ETL flows in connectors. For more information, see <a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/concept/configuring-the-telco-generic-schema-etl.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/configuring-the-telco-generic-schema-etl.html" class="xref" title="Leverage the prebuilt Telecom Discovery Builder framework ETL by duplicating it into your connector scope, assigning the appropriate data source, and deploying it as part of a new service graph connector.">Configuring the Telecom Discovery Builder framework ETL in a connector</a>.</li>
<li class="li">Use service graph connectors (e.g., Nokia Altiplano) to import topology and configuration data. For more information, see <a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/concept/configuring-service-graph-connector-nokia-altiplano.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/configuring-service-graph-connector-nokia-altiplano.html" class="xref" title="Configure the Nokia Altiplano service graph connector to import physical and logical inventory data from the Nokia Altiplano Access Network SDN Controller into your ServiceNow Configuration Management Database (CMDB).">Configuring Nokia Altiplano service graph connector</a>.</li>
</ul></li>
<li class="li">Enable discrepancy detection:<ul class="ul" id="configuring-tsom__ul_ibf_5xb_1gc">
<li class="li">Activate Telecom Discrepancy Identification and Reconciliation. For more information, see <a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/task/configure-telecom-reconciliation.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/configure-telecom-reconciliation.html" class="xref" title="Activate the Telecom Discrepancy Identification and Reconciliation feature (part of the Telecom Visibility plugin) to ensure consistency between telecom network resources discovered in the live network and the data represented in the CMDB or Telecom Network Inventory (TNI). This feature helps detect and remediate mismatches automatically, supporting service accuracy and data integrity across your telecom environment.">Activate Telecom Discrepancy Identification and Reconciliation</a>.</li>
<li class="li">Define filters for telecom audits and configure attribute value discrepancy checks in CMDB 360.</li>
</ul></li>
</ol></li>
</ol></div>
<p class="p">Each step is modular and can be configured based on your environment and available integrations.</p>
</section>
</div>
</article></main></body></article> | {
"attachments": {
"all_attachments": null,
"topic_attachments": []
},
"available_languages": [
"enus"
],
"breadcrumbs": [
{
"title": "Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html"
}
],
"breadcrumbs_html": "<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops\">Zurich Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html\">Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<span class=\"active\">Configuring Telecommunications Service Operations Management</span>",
"bundle_id": "zurich-telecom-service-ops",
"bundle_key": 2733,
"bundle_landing_page": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html",
"bundle_subtitle": null,
"bundle_title": "Zurich Telecommunications Service Operations Management",
"canonical_link": null,
"dates": {
"Added on": "2025-08-02T00:48:08.794016Z",
"Created on": "2025-06-24T00:00:00Z",
"Initial upload": "2025-07-30T22:24:33.519043Z",
"Updated on": "2025-07-31T00:00:00Z"
},
"dislike_url": "https://servicenow-be-prod.servicenow.com/dislike/55686930",
"dislikes": 0,
"es_archived_content": false,
"is_in_fav": false,
"is_liked": null,
"is_watched": false,
"keywords": [
" zurich zurich"
],
"labels": [
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "zurich",
"navtitle": "Zurich",
"outputclasses": [],
"subjectHeadId": "versions",
"subjectheadNavtitle": "Versions",
"visibility": "show-facet"
},
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "tsom",
"navtitle": "Telecommunications Service Operations Management",
"outputclasses": [],
"subjectHeadId": "products",
"subjectheadNavtitle": "Products",
"visibility": "show-facet"
}
],
"labels_text": "Versions > Zurich; Products > CRM and Industry Products > Telecommunications Media and Technology Assurance > Telecommunications Service Operations Management",
"like_url": "https://servicenow-be-prod.servicenow.com/like/55686930",
"likes": 0,
"metadata": {
"AI Search": null,
"AI Search Assist": null,
"Application Insights": null,
"Capabilities": null,
"Code Signing": null,
"Contextual Search": null,
"DC.contributor": null,
"DC.coverage": null,
"DC.creator": "ServiceNow",
"DC.date.created": "2025-06-24T09:32:48+05:30",
"DC.date.modified": "2025-07-31",
"DC.format": "HTML5",
"DC.identifier": "configuring-tsom",
"DC.language": null,
"DC.relation": null,
"DC.rights.owner": "(C) Copyright 2025",
"DC.subject": null,
"DC.type": "concept",
"Data Discovery": null,
"Data Policy": null,
"Data Privacy": null,
"Discovery": null,
"External Content for AI Search": null,
"Field Administration": null,
"Field Normalization": null,
"Key Management Framework": null,
"Localization Framework": null,
"Now Platform": null,
"PlatSec": null,
"Platform": null,
"Platform Administration": null,
"Platform Performance": null,
"Platform Privacy": null,
"Proactive Triggers": null,
"Process Optimization": null,
"RN doc editing record number": null,
"Search Administration": null,
"Secrets Management": null,
"ServiceNow AI Platform": null,
"State Model": null,
"Subscription Management": null,
"Task Communications Management": null,
"Timeline Visualizations": null,
"User Administration": null,
"User Experience Analytics": null,
"Zing": null,
"ai-now-assist": null,
"app-name": null,
"app_route": null,
"azureapimanagemen": null,
"change-completed": null,
"change-item": null,
"change-request-id": null,
"change-request-reference": null,
"com.glide.embedded_help.category": null,
"component": null,
"copyright": "(C) Copyright 2025",
"crossroads": null,
"data": null,
"description": "Configure Telecommunications Service Operations Management (TSOM) to enable real-time event ingestion, correlation, and automated remediation by integrating with external network monitoring and discovery systems.",
"dominant_bundle": null,
"erp-canvas-video": null,
"fsm-mobile": null,
"fsm-route": null,
"fsm-sched-opt": null,
"fsm-wrk-order": null,
"genai-round-7": null,
"generator": "DITA-OT",
"glossPartOfSpeech": null,
"glossStatus": null,
"guided setup": null,
"guided tours": null,
"keywords": null,
"min-toc": null,
"mini": null,
"mini-to truec": null,
"mini-toc": "yes",
"mini_toc": null,
"minitoc": null,
"modification": null,
"now-assist-app-gen-video": null,
"order": null,
"page-type": null,
"page-type ": null,
"prodname": null,
"product": null,
"product_name": null,
"release": null,
"resourceID": null,
"roles": null,
"route_page": null,
"route_params_listId": null,
"route_params_table": null,
"route_params_type": null,
"route_type": null,
"setconfigurationproperties": null,
"topic": null,
"translation-type": "source",
"version": null,
"workflow": "Customer and Industry",
"workplace-srvc-delvry-ditamap": null
},
"page_id": "product/tmt-telecom-service-operations-mgt/concept/configuring-tsom.html",
"page_key": 55686930,
"preprocessed_PDF": "https://downloads.docs.servicenow.com/pdf/enus/servicenow-zurich-telecom-service-ops-enus.pdf",
"rating": null,
"read_time_data": {
"char_count": 2505,
"img_count": 0,
"read_time": 2,
"video_links": [
""
],
"word_count": 303
},
"related_links": [],
"search_title": null,
"title": "Configuring Telecommunications Service Operations Management",
"topic_cluster": {
"clustered_by": {
"enabled": true,
"primary_key": "versions",
"primary_sort": "top-down",
"type": "subjecthead"
},
"clustered_labels": [
"versions"
],
"clustered_topics": [],
"clustering_title": "Zurich"
},
"topic_html": "<article class=\"hascomments\" data-page=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/configuring-tsom.html\" id=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/configuring-tsom.html\"><body id=\"configuring-tsom\"><main role=\"main\"><article role=\"article\" class=\"dita\" id=\"configuring-tsom\" aria-labelledby=\"title_configuring-tsom\">\n <h1 class=\"title topictitle1\" id=\"title_configuring-tsom\">Configuring <span class=\"ph\">Telecommunications Service Operations Management</span></h1>\n \n \n <div class=\"body conbody\"><p class=\"shortdesc\">Configure <span class=\"ph\">Telecommunications Service Operations Management</span> (TSOM) to enable real-time event ingestion, correlation, and automated remediation by integrating with external network monitoring and discovery systems.</p>\n <p class=\"p\">Set up TSOM to enable end-to-end telecom service operations, including alarm ingestion, CMDB population, discrepancy detection, and service impact visibility. This configuration involves activating Telecommunications API\n notifications, setting up discovery and service graph connectors, enabling visibility, and configuring audit and reconciliation frameworks.</p>\n <section class=\"section\" id=\"configuring-tsom__section_tvj_gxb_1gc\"><h2 id=\"d10122e50\" class=\"title sectiontitle\">Configuration overview</h2>\n \n <div class=\"p\">Telecommunications Service Operations Management (TSOM) requires configuring multiple components across alarm ingestion, discovery, data normalization, and reconciliation to support end-to-end telecom operations. The configuration\n flow typically includes:<ol class=\"ol\" id=\"configuring-tsom__ol_kzz_qhz_bgc\">\n <li class=\"li\">Activate the following plugins to have TSOM Core in your system<ul class=\"ul\" id=\"configuring-tsom__ul_iqx_rhz_bgc\">\n <li class=\"li\">Pattern Designer (com.snc.pattern.designer)</li>\n <li class=\"li\">ServiceNow IntegrationHub Started Pack Installer (com.glide.hub.integrations)</li>\n <li class=\"li\">Discovery (com.snc.discovery)</li>\n <li class=\"li\">CMDB CI Class Models (sn_cmdb_ci_class) 1.69.0</li>\n <li class=\"li\">Visibility Content (sn_pattern_design) 6.23.0</li>\n <li class=\"li\">Integration Commons for CMDB (sn_cmdb_int_util) 2.19.0</li>\n </ul></li>\n <li class=\"li\">Enable alarm ingestion: Activate the Telecommunications API notifications and set up topic subscriptions to receive alarms from external systems. For more information, see <a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept/configuring-telecommunications-api-notifications.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/configuring-telecommunications-api-notifications.html\" class=\"xref\" title=\"Configure the Telecommunications API notification in the ServiceNow instance.\">Configuring Telecommunications API notifications</a>.</li>\n <li class=\"li\">Set up visibility: Configure Telecom Visibility to view service-to-infrastructure mappings and monitor network health. For more information, see <a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/task/configuring-tsom-visibility.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/configuring-tsom-visibility.html\" class=\"xref\" title=\"Telecom Visibility provides foundational capabilities that support both Telecom Discovery and Telecom Discrepancy Identification & Reconciliation. It includes shared logic, enhanced CI class models, and Identification and Reconciliation Engine (IRE) updates tailored for telecom network elements.\">Set up Telecom Visibility</a><ol class=\"ol\" type=\"a\" id=\"configuring-tsom__ol_dts_vhz_bgc\">\n <li class=\"li\">Populate the telecom-aware CMDB:<ul class=\"ul\" id=\"configuring-tsom__ul_jlf_hxb_1gc\">\n <li class=\"li\">Install and configure Horizontal Discovery. For more information, see <a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/task/install-horizontal-telecommunication-discoverypatterns.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/install-horizontal-telecommunication-discoverypatterns.html\" class=\"xref\" title=\"Install Horizontal Discovery patterns understanding the dependencies and requirements.\">Install Horizontal Discovery and set up Discovery Patterns</a>.</li>\n <li class=\"li\">Set up Telecom Discovery Builder (TDB) ETL flows in connectors. For more information, see <a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept/configuring-the-telco-generic-schema-etl.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/configuring-the-telco-generic-schema-etl.html\" class=\"xref\" title=\"Leverage the prebuilt Telecom Discovery Builder framework ETL by duplicating it into your connector scope, assigning the appropriate data source, and deploying it as part of a new service graph connector.\">Configuring the Telecom Discovery Builder framework ETL in a connector</a>.</li>\n <li class=\"li\">Use service graph connectors (e.g., Nokia Altiplano) to import topology and configuration data. For more information, see <a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept/configuring-service-graph-connector-nokia-altiplano.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/configuring-service-graph-connector-nokia-altiplano.html\" class=\"xref\" title=\"Configure the Nokia Altiplano service graph connector to import physical and logical inventory data from the Nokia Altiplano Access Network SDN Controller into your ServiceNow Configuration Management Database (CMDB).\">Configuring Nokia Altiplano service graph connector</a>.</li>\n </ul></li>\n <li class=\"li\">Enable discrepancy detection:<ul class=\"ul\" id=\"configuring-tsom__ul_ibf_5xb_1gc\">\n <li class=\"li\">Activate Telecom Discrepancy Identification and Reconciliation. For more information, see <a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/task/configure-telecom-reconciliation.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/configure-telecom-reconciliation.html\" class=\"xref\" title=\"Activate the Telecom Discrepancy Identification and Reconciliation feature (part of the Telecom Visibility plugin) to ensure consistency between telecom network resources discovered in the live network and the data represented in the CMDB or Telecom Network Inventory (TNI). This feature helps detect and remediate mismatches automatically, supporting service accuracy and data integrity across your telecom environment.\">Activate Telecom Discrepancy Identification and Reconciliation</a>.</li>\n <li class=\"li\">Define filters for telecom audits and configure attribute value discrepancy checks in CMDB 360.</li>\n </ul></li>\n </ol></li>\n </ol></div>\n <p class=\"p\">Each step is modular and can be configured based on your environment and available integrations.</p>\n </section>\n </div>\n</article></main></body></article>",
"topic_language": "enus",
"views": 0,
"your_rating": null
} | # Configuring Telecommunications Service Operations Management
Configure Telecommunications Service Operations Management (TSOM) to enable real-time event ingestion, correlation, and automated remediation by integrating with external network monitoring and discovery systems.
Set up TSOM to enable end-to-end telecom service operations, including alarm ingestion, CMDB population, discrepancy detection, and service impact visibility. This configuration involves activating Telecommunications API
notifications, setting up discovery and service graph connectors, enabling visibility, and configuring audit and reconciliation frameworks.
## Configuration overview
Telecommunications Service Operations Management (TSOM) requires configuring multiple components across alarm ingestion, discovery, data normalization, and reconciliation to support end-to-end telecom operations. The configuration
flow typically includes:
1. Activate the following plugins to have TSOM Core in your system
* Pattern Designer (com.snc.pattern.designer)
* ServiceNow IntegrationHub Started Pack Installer (com.glide.hub.integrations)
* Discovery (com.snc.discovery)
* CMDB CI Class Models (sn\_cmdb\_ci\_class) 1.69.0
* Visibility Content (sn\_pattern\_design) 6.23.0
* Integration Commons for CMDB (sn\_cmdb\_int\_util) 2.19.0
2. Enable alarm ingestion: Activate the Telecommunications API notifications and set up topic subscriptions to receive alarms from external systems. For more information, see Configuring Telecommunications API notifications.
3. Set up visibility: Configure Telecom Visibility to view service-to-infrastructure mappings and monitor network health. For more information, see Set up Telecom Visibility
1. Populate the telecom-aware CMDB:
* Install and configure Horizontal Discovery. For more information, see Install Horizontal Discovery and set up Discovery Patterns.
* Set up Telecom Discovery Builder (TDB) ETL flows in connectors. For more information, see Configuring the Telecom Discovery Builder framework ETL in a connector.
* Use service graph connectors (e.g., Nokia Altiplano) to import topology and configuration data. For more information, see Configuring Nokia Altiplano service graph connector.
2. Enable discrepancy detection:
* Activate Telecom Discrepancy Identification and Reconciliation. For more information, see Activate Telecom Discrepancy Identification and Reconciliation.
* Define filters for telecom audits and configure attribute value discrepancy checks in CMDB 360.
Each step is modular and can be configured based on your environment and available integrations.
| ---
title: Configuring Telecommunications Service Operations Management
description: Configure Telecommunications Service Operations Management (TSOM) to
enable real-time event ingestion, correlation, and automated remediation by integrating
with external network monitoring and discovery systems.
keywords: []
breadcrumbs:
- Telecommunications Service Operations Management
---
# Configuring Telecommunications Service Operations Management
Configure Telecommunications Service Operations Management (TSOM) to enable real-time event ingestion, correlation, and automated remediation by integrating with external network monitoring and discovery systems.
Set up TSOM to enable end-to-end telecom service operations, including alarm ingestion, CMDB population, discrepancy detection, and service impact visibility. This configuration involves activating Telecommunications API
notifications, setting up discovery and service graph connectors, enabling visibility, and configuring audit and reconciliation frameworks.
## Configuration overview
Telecommunications Service Operations Management (TSOM) requires configuring multiple components across alarm ingestion, discovery, data normalization, and reconciliation to support end-to-end telecom operations. The configuration
flow typically includes:
1. Activate the following plugins to have TSOM Core in your system
* Pattern Designer (com.snc.pattern.designer)
* ServiceNow IntegrationHub Started Pack Installer (com.glide.hub.integrations)
* Discovery (com.snc.discovery)
* CMDB CI Class Models (sn\_cmdb\_ci\_class) 1.69.0
* Visibility Content (sn\_pattern\_design) 6.23.0
* Integration Commons for CMDB (sn\_cmdb\_int\_util) 2.19.0
2. Enable alarm ingestion: Activate the Telecommunications API notifications and set up topic subscriptions to receive alarms from external systems. For more information, see Configuring Telecommunications API notifications.
3. Set up visibility: Configure Telecom Visibility to view service-to-infrastructure mappings and monitor network health. For more information, see Set up Telecom Visibility
1. Populate the telecom-aware CMDB:
* Install and configure Horizontal Discovery. For more information, see Install Horizontal Discovery and set up Discovery Patterns.
* Set up Telecom Discovery Builder (TDB) ETL flows in connectors. For more information, see Configuring the Telecom Discovery Builder framework ETL in a connector.
* Use service graph connectors (e.g., Nokia Altiplano) to import topology and configuration data. For more information, see Configuring Nokia Altiplano service graph connector.
2. Enable discrepancy detection:
* Activate Telecom Discrepancy Identification and Reconciliation. For more information, see Activate Telecom Discrepancy Identification and Reconciliation.
* Define filters for telecom audits and configure attribute value discrepancy checks in CMDB 360.
Each step is modular and can be configured based on your environment and available integrations.
|
https://www.servicenow.com/docs/en-US/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/data-mapping.html | https://servicenow-be-prod.servicenow.com/api/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/data-mapping.html | 2025-08-02 | daily | 0.5 | 268.xml | en-US | zurich-telecom-service-ops | product/tmt-telecom-service-operations-mgt/concept/data-mapping.html | zurich | Mapping Nokia Altiplano CIs and Relationships in CMDB | Use the Service Graph Connector for Nokia Altiplano to map discovered physical and logical network resources to telecom-aligned Configuration Item (CI) classes in the CMDB. The connector supports consistent service modeling, visibility into chassis-level components, and automation of logical and | [] | [
"Telecommunications Service Operations Management",
"Configuring Telecommunications Service Operations Management",
"Set up Telecom Visibility",
"Configuring Nokia Altiplano service graph connector"
] | <article class="hascomments" data-page="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/data-mapping.html" id="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/data-mapping.html"><body id="data-mapping"><main role="main"><article role="article" class="dita" id="data-mapping" aria-labelledby="title_data-mapping">
<h1 class="title topictitle1" id="title_data-mapping">Mapping Nokia Altiplano CIs and Relationships in CMDB</h1>
<div class="body conbody"><p class="shortdesc">Use the Service Graph Connector for Nokia Altiplano to map discovered physical and logical network resources to telecom-aligned Configuration Item (CI) classes in the CMDB. The connector supports consistent service modeling,
visibility into chassis-level components, and automation of logical and physical relationships.</p>
<p class="p">To confirm accurate CI classification and insertion, the connector uses the Robust Transform Engine (RTE) and Identification and Reconciliation Engine (IRE).</p>
<p class="p">The connector classifies and relates discovered CIs using telecom-specific models based on device type, function, and chassis structure. This helps maintain a clean and normalized CMDB across vendors. Discovered model names from Nokia
Altiplano are automatically transformed into ServiceNow standard model identifiers and categories for slot and subslot components.</p>
<section class="section" id="data-mapping__section_tt1_q15_xfc"><h2 id="d5786e48" class="title sectiontitle">CI mapping and relationships</h2>
<div class="p">The following tables describe how Altiplano CIs are represented in the CMDB and how they relate to each other across physical and logical layers.<div class="table-wrap"><table count-columns="3" class="table" id="data-mapping__table_m5l_m1b_wfc"><caption><span class="table--title-label">Table 1. </span><span class="title">CMDB CI Mapping and Relationships (Physical Layer)</span></caption><colgroup><col/><col/><col/></colgroup><thead class="thead">
<tr class="row">
<th class="entry" id="data-mapping__table_m5l_m1b_wfc__entry__1">CI Type</th>
<th class="entry" id="data-mapping__table_m5l_m1b_wfc__entry__2">CMDB Table</th>
<th class="entry" id="data-mapping__table_m5l_m1b_wfc__entry__3">Description and Relationships</th>
</tr>
</thead><tbody class="tbody">
<tr class="row">
<td class="entry" headers="data-mapping__table_m5l_m1b_wfc__entry__1">OLT CI</td>
<td class="entry" headers="data-mapping__table_m5l_m1b_wfc__entry__2"><code class="ph codeph">cmdb_ci_optical_line_terminal</code></td>
<td class="entry" headers="data-mapping__table_m5l_m1b_wfc__entry__3">Represents the OLT device. Contains Slot CIs and Logical Network Interface CIs.</td>
</tr>
<tr class="row">
<td class="entry" headers="data-mapping__table_m5l_m1b_wfc__entry__1">ONU/ONT CI</td>
<td class="entry" headers="data-mapping__table_m5l_m1b_wfc__entry__2"><code class="ph codeph">cmdb_ci_optical_network_terminal</code> or <code class="ph codeph">cmdb_ci_optical_network_unit</code></td>
<td class="entry" headers="data-mapping__table_m5l_m1b_wfc__entry__3">Represents ONU or ONT devices. The class is determined by the system property <code class="ph codeph">sn_sgc_altiplano.onu_ci_class</code>. Contains Network Interface CIs.</td>
</tr>
<tr class="row">
<td class="entry" headers="data-mapping__table_m5l_m1b_wfc__entry__1">Slot CI</td>
<td class="entry" headers="data-mapping__table_m5l_m1b_wfc__entry__2"><code class="ph codeph">cmdb_ci_container_slot</code></td>
<td class="entry" headers="data-mapping__table_m5l_m1b_wfc__entry__3">Represents main chassis slots. Contained by OLT CIs. Contains Interface Card CIs (for example, LT/NT, PSU, fan). Model transformations are applied in the data source. For more information, see the above mentioned Model
transformation for slot and subslot CIs table.</td>
</tr>
<tr class="row">
<td class="entry" headers="data-mapping__table_m5l_m1b_wfc__entry__1">Subslot CI</td>
<td class="entry" headers="data-mapping__table_m5l_m1b_wfc__entry__2"><code class="ph codeph">cmdb_ci_container_subslot</code></td>
<td class="entry" headers="data-mapping__table_m5l_m1b_wfc__entry__3">Represents subcomponents within interface cards (for example, cages for SFPs). Contained by LT/NT cards. Contains transceiver card CIs. For more information, see the above mentioned Model transformation for slot and subslot
CIs table.</td>
</tr>
<tr class="row">
<td class="entry" headers="data-mapping__table_m5l_m1b_wfc__entry__1">Interface Card CI</td>
<td class="entry" headers="data-mapping__table_m5l_m1b_wfc__entry__2"><code class="ph codeph">cmdb_ci_interface_card</code></td>
<td class="entry" headers="data-mapping__table_m5l_m1b_wfc__entry__3">Represents LT/NT cards, transceivers, and control units. Can contain subslots and network interfaces.</td>
</tr>
<tr class="row">
<td class="entry" headers="data-mapping__table_m5l_m1b_wfc__entry__1">Network Interface CI</td>
<td class="entry" headers="data-mapping__table_m5l_m1b_wfc__entry__2"><code class="ph codeph">cmdb_ci_ni_interface</code></td>
<td class="entry" headers="data-mapping__table_m5l_m1b_wfc__entry__3">Represents both physical (for example, PON, Ethernet) and logical (for example, VLAN) ports. Contained by interface cards or ONU/ONT CIs. Logical ports are related to physical ports using Members::Member of.</td>
</tr>
<tr class="row">
<td class="entry" headers="data-mapping__table_m5l_m1b_wfc__entry__1">Logical Connection CI</td>
<td class="entry" headers="data-mapping__table_m5l_m1b_wfc__entry__2"><code class="ph codeph">cmdb_ci_ni_logical_path</code></td>
<td class="entry" headers="data-mapping__table_m5l_m1b_wfc__entry__3">Represents logical paths such as PON or VLAN between OLT and ONU. Defined with Port A and Port Z attributes referencing terminating Network Interface CIs. VLAN paths consume PON paths.</td>
</tr>
<tr class="row">
<td class="entry" headers="data-mapping__table_m5l_m1b_wfc__entry__1">IP Address CI</td>
<td class="entry" headers="data-mapping__table_m5l_m1b_wfc__entry__2"><code class="ph codeph">cmdb_ci_ip_address</code></td>
<td class="entry" headers="data-mapping__table_m5l_m1b_wfc__entry__3">Represents discovered IP addresses for OLTs. Owned by the corresponding OLT CI.</td>
</tr>
</tbody></table></div></div>
</section>
<section class="section" id="data-mapping__section_syv_s1b_wfc"><h2 id="d5786e200" class="title sectiontitle">Key Relationship Examples</h2>
<div class="p">
<ul class="ul" id="data-mapping__ul_msk_s1b_wfc">
<li class="li">Containment relationships<ul class="ul" id="data-mapping__ul_nsk_s1b_wfc">
<li class="li">OLT CI → contains Slot CI</li>
<li class="li">Slot CI → contains Interface Card CI</li>
<li class="li">Interface Card CI → contains Subslot CI</li>
<li class="li">Subslot CI → contains transceiver Interface Card CI</li>
<li class="li">ONU/ONT CI → contains Network Interface CIs</li>
</ul></li>
<li class="li">Interface relationships:<ul class="ul" id="data-mapping__ul_osk_s1b_wfc">
<li class="li">Logical Connections -> terminated by Network Interfaces</li>
<li class="li">Network Interfaces -> members of Network Interfaces</li>
</ul></li>
<li class="li">Logical path relationships:<ul class="ul" id="data-mapping__ul_psk_s1b_wfc">
<li class="li">VLAN path (parent) → consumes → PON path (child)</li>
<li class="li">Logical paths → terminate at → Network Interface CIs via Port A and Port Z</li>
</ul></li>
<li class="li">Ownership: IP Address CI → owned by OLT device</li>
</ul>
</div>
</section>
<section class="section" id="data-mapping__section_x3f_2db_wfc"><h2 id="d5786e257" class="title sectiontitle">Supported models</h2>
<div class="p">
<ol class="ol" id="data-mapping__ol_txf_phy_yfc">
<li class="li">Network equipment models (sn_ent_nw_equipment_model)<ul class="ul" id="data-mapping__ul_hbl_nhy_yfc">
<li class="li">The supported OLT is Nokia Lightspan MF-2, by default the model name is "Nokia MF-2"</li>
<li class="li">ONU/ONT models are manufacturer + ONU/ONT. the system property sn_sgc_altiplano.onu_ci_class defines if ONU or ONT will be used.</li>
<li class="li">If the model wasn’t found in the model table, a new model is created in the CI. and the CI will be created as "Network gear"</li>
</ul></li>
<li class="li">Equipment holder models: (sn_ent_nw_holder_model)<ul class="ul" id="data-mapping__ul_ibl_nhy_yfc">
<li class="li">Slots models: "Traffic Slot", "FAN Slot", "Power Slot"</li>
<li class="li">Subslots models: "SFP Subslot"</li>
<li class="li">The used model name can be customized by the customer through the Altiplano extension point (sn_sgc_altiplano.AltiplanoCustomizedModels)</li>
<li class="li">If the model wasn’t found in the model table, a new model is created in the CI.</li>
</ul></li>
<li class="li">Network card models (sn_ent_nw_card_model)<ul class="ul" id="data-mapping__ul_jbl_nhy_yfc">
<li class="li">Card models are found by the model name, manufacturer, and model number discovered from the Altiplano API</li>
<li class="li">If the model wasn’t found in the model table, a new model is created in the CI.</li>
</ul></li>
<li class="li">Network Interface Models: (sn_ent_nw_interface_model).<ul class="ul" id="data-mapping__ul_kbl_nhy_yfc">
<li class="li">Ethernet ports models are found by the "port bandwidth" column in the Network Interface table (sn_ent_nw_interface_model). the port bandwidth of the port CI is located by the discovered port speed in the Bandwidth table
(bandwidth)</li>
<li class="li">PON physical ports models: "PON Access Interface", "PON Network Interfaces"</li>
<li class="li">Logical ports models: "ENET Interface", "VLAN Interface", "LAG Interface", PON Logical Interface"</li>
<li class="li">If the model wasn’t found in the model table, the reference to the "Model ID" will remain empty.</li>
</ul></li>
<li class="li">Logical network connection models (sn_ent_logical_nw_connection_model)<ul class="ul" id="data-mapping__ul_lbl_nhy_yfc">
<li class="li">PON Access Path</li>
<li class="li">VLAN Path</li>
<li class="li">If the model wasn’t found in the model table, the reference to the "Model ID" will remain empty.</li>
</ul></li>
</ol>
<div class="note note note_note"><span class="note__title">Note:</span>
<ul class="ul" id="data-mapping__ul_mbl_nhy_yfc">
<li class="li">If the connector cannot match a discovered equipment to an existing model in the product model table the CI is created as <code class="ph codeph">Network Gear</code> by default.</li>
<li class="li">If demo data is installed, default models are created for OLT, ONU, ONT, Slots, Subslots, Cards, Network Interfaces, and Logical connections.</li>
<li class="li">Equipment and Equipment holder model names can be customized using an extension point</li>
</ul>
</div>
</div>
</section>
<section class="section" id="data-mapping__section_uq3_315_xfc"><h2 id="d5786e361" class="title sectiontitle">Model transformation for slot and subslot CIs</h2>
<p class="p">During ingestion, specific discovered model names are mapped to predefined CMDB model identifiers to confirm consistent slot categorization. The transformation logic is embedded in the SGC data source script and applies to the Nokia
Altiplano source.</p>
<p class="p">Slot components such as fan, power, and traffic slots are mapped to the <code class="ph codeph">Slot</code> category in the CMDB. Subslot components such as SFP cages or synthetic subslots are mapped to the <code class="ph codeph">Subslot</code> category in the
CMDB.</p>
<div class="table-wrap"><table count-columns="4" class="table" id="data-mapping__table_utm_k15_xfc"><caption><span class="table--title-label">Table 2. </span><span class="title">Example: Nokia Altiplano slot and sub slot model mappings</span></caption><colgroup><col/><col/><col/><col/></colgroup><thead class="thead">
<tr class="row">
<th class="entry" id="data-mapping__table_utm_k15_xfc__entry__1">Source</th>
<th class="entry" id="data-mapping__table_utm_k15_xfc__entry__2">Discovered Model Name</th>
<th class="entry" id="data-mapping__table_utm_k15_xfc__entry__3">Target CMDB Model ID</th>
<th class="entry" id="data-mapping__table_utm_k15_xfc__entry__4">Model Category</th>
</tr>
</thead><tbody class="tbody">
<tr class="row">
<td class="entry" headers="data-mapping__table_utm_k15_xfc__entry__1">Altiplano</td>
<td class="entry" headers="data-mapping__table_utm_k15_xfc__entry__2">slot-fan</td>
<td class="entry" headers="data-mapping__table_utm_k15_xfc__entry__3">Fan Slot</td>
<td class="entry" headers="data-mapping__table_utm_k15_xfc__entry__4">Slot</td>
</tr>
<tr class="row">
<td class="entry" headers="data-mapping__table_utm_k15_xfc__entry__1">Altiplano</td>
<td class="entry" headers="data-mapping__table_utm_k15_xfc__entry__2">slot-lt</td>
<td class="entry" headers="data-mapping__table_utm_k15_xfc__entry__3">Traffic Slot</td>
<td class="entry" headers="data-mapping__table_utm_k15_xfc__entry__4">Slot</td>
</tr>
<tr class="row">
<td class="entry" headers="data-mapping__table_utm_k15_xfc__entry__1">Altiplano</td>
<td class="entry" headers="data-mapping__table_utm_k15_xfc__entry__2">cage</td>
<td class="entry" headers="data-mapping__table_utm_k15_xfc__entry__3">SFP Subslot</td>
<td class="entry" headers="data-mapping__table_utm_k15_xfc__entry__4">Subslot</td>
</tr>
<tr class="row">
<td class="entry" headers="data-mapping__table_utm_k15_xfc__entry__1">Altiplano</td>
<td class="entry" headers="data-mapping__table_utm_k15_xfc__entry__2">slot-nt</td>
<td class="entry" headers="data-mapping__table_utm_k15_xfc__entry__3">Traffic Slot</td>
<td class="entry" headers="data-mapping__table_utm_k15_xfc__entry__4">Slot</td>
</tr>
<tr class="row">
<td class="entry" headers="data-mapping__table_utm_k15_xfc__entry__1">Altiplano</td>
<td class="entry" headers="data-mapping__table_utm_k15_xfc__entry__2">synthetic nt-slot</td>
<td class="entry" headers="data-mapping__table_utm_k15_xfc__entry__3">SFP Subslot</td>
<td class="entry" headers="data-mapping__table_utm_k15_xfc__entry__4">Subslot</td>
</tr>
<tr class="row">
<td class="entry" headers="data-mapping__table_utm_k15_xfc__entry__1">Altiplano</td>
<td class="entry" headers="data-mapping__table_utm_k15_xfc__entry__2">slot-psu</td>
<td class="entry" headers="data-mapping__table_utm_k15_xfc__entry__3">Power Slot</td>
<td class="entry" headers="data-mapping__table_utm_k15_xfc__entry__4">Slot</td>
</tr>
</tbody></table></div>
</section>
<section class="section" id="data-mapping__section_z2f_2db_wfc"><h2 id="d5786e509" class="title sectiontitle">CI relationship structure</h2>
<p class="p">The following infographics describes the CI relationships.</p>
<p class="p"><img src="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/../images/ci-relationships.png?_LANG=enus" class="image" id="data-mapping__image_qty_qcb_wfc" alt="CI relationships structure"/><img src="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/../images/ci-relationship-diagram.png?_LANG=enus" class="image" id="data-mapping__image_f3n_tnt_xfc" alt="CI relationship structure"/></p>
</section>
<section class="section" id="data-mapping__section_rpp_ycb_wfc"><h2 id="d5786e530" class="title sectiontitle">Example: OLT to ONU Structure</h2>
<div class="p">The following structure enables end-to-end traceability from OLT through its hardware layers to the connected ONU and associated logical paths.<pre class="prettyprint language-plaintext"><code class="pre codeblock language-plaintext">OLT (cmdb_ci_optical_line_terminal)
├── Slot
│ ├── Interface Card (LT/NT)
│ │ ├── Subslot
│ │ │ └── Interface Card (Transceiver)
│ │ │ └── Network Interface (PON port)
├── Logical Connections (PON/VLAN) → Connected to →
└── ONU/ONT (cmdb_ci_optical_network_terminal)
└── Network Interface (ONT port)
</code></pre></div>
</section>
</div>
</article></main></body></article> | {
"attachments": {
"all_attachments": null,
"topic_attachments": []
},
"available_languages": [
"enus"
],
"breadcrumbs": [
{
"title": "Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html"
},
{
"title": "Configuring Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/configuring-tsom.html"
},
{
"title": "Set up Telecom Visibility",
"topic_id": "product/tmt-telecom-service-operations-mgt/task/configuring-tsom-visibility.html"
},
{
"title": "Configuring Nokia Altiplano service graph connector",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/configuring-service-graph-connector-nokia-altiplano.html"
}
],
"breadcrumbs_html": "<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops\">Zurich Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html\">Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/configuring-tsom.html\">Configuring Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/configuring-tsom-visibility.html\">Set up Telecom Visibility</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/configuring-service-graph-connector-nokia-altiplano.html\">Configuring Nokia Altiplano service graph connector</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<span class=\"active\">Mapping Nokia Altiplano CIs and Relationships in CMDB</span>",
"bundle_id": "zurich-telecom-service-ops",
"bundle_key": 2733,
"bundle_landing_page": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html",
"bundle_subtitle": null,
"bundle_title": "Zurich Telecommunications Service Operations Management",
"canonical_link": null,
"dates": {
"Added on": "2025-08-02T00:48:08.794016Z",
"Created on": "2025-01-13T00:00:00Z",
"Initial upload": "2025-07-30T22:24:33.519043Z",
"Updated on": "2025-07-31T00:00:00Z"
},
"dislike_url": "https://servicenow-be-prod.servicenow.com/dislike/55686931",
"dislikes": 0,
"es_archived_content": false,
"is_in_fav": false,
"is_liked": null,
"is_watched": false,
"keywords": [
" zurich zurich"
],
"labels": [
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "zurich",
"navtitle": "Zurich",
"outputclasses": [],
"subjectHeadId": "versions",
"subjectheadNavtitle": "Versions",
"visibility": "show-facet"
},
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "tsom",
"navtitle": "Telecommunications Service Operations Management",
"outputclasses": [],
"subjectHeadId": "products",
"subjectheadNavtitle": "Products",
"visibility": "show-facet"
}
],
"labels_text": "Versions > Zurich; Products > CRM and Industry Products > Telecommunications Media and Technology Assurance > Telecommunications Service Operations Management",
"like_url": "https://servicenow-be-prod.servicenow.com/like/55686931",
"likes": 0,
"metadata": {
"AI Search": null,
"AI Search Assist": null,
"Application Insights": null,
"Capabilities": null,
"Code Signing": null,
"Contextual Search": null,
"DC.contributor": null,
"DC.coverage": null,
"DC.creator": "ServiceNow",
"DC.date.created": "2025-01-13T11:09:09+05:30",
"DC.date.modified": "2025-07-31",
"DC.format": "HTML5",
"DC.identifier": "data-mapping",
"DC.language": null,
"DC.relation": null,
"DC.rights.owner": "(C) Copyright 2025",
"DC.subject": null,
"DC.type": "concept",
"Data Discovery": null,
"Data Policy": null,
"Data Privacy": null,
"Discovery": null,
"External Content for AI Search": null,
"Field Administration": null,
"Field Normalization": null,
"Key Management Framework": null,
"Localization Framework": null,
"Now Platform": null,
"PlatSec": null,
"Platform": null,
"Platform Administration": null,
"Platform Performance": null,
"Platform Privacy": null,
"Proactive Triggers": null,
"Process Optimization": null,
"RN doc editing record number": null,
"Search Administration": null,
"Secrets Management": null,
"ServiceNow AI Platform": null,
"State Model": null,
"Subscription Management": null,
"Task Communications Management": null,
"Timeline Visualizations": null,
"User Administration": null,
"User Experience Analytics": null,
"Zing": null,
"ai-now-assist": null,
"app-name": null,
"app_route": null,
"azureapimanagemen": null,
"change-completed": null,
"change-item": null,
"change-request-id": null,
"change-request-reference": null,
"com.glide.embedded_help.category": null,
"component": null,
"copyright": "(C) Copyright 2025",
"crossroads": null,
"data": null,
"description": "Use the Service Graph Connector for Nokia Altiplano to map discovered physical and logical network resources to telecom-aligned Configuration Item (CI) classes in the CMDB. The connector supports consistent service modeling, visibility into chassis-level components, and automation of logical and",
"dominant_bundle": null,
"erp-canvas-video": null,
"fsm-mobile": null,
"fsm-route": null,
"fsm-sched-opt": null,
"fsm-wrk-order": null,
"genai-round-7": null,
"generator": "DITA-OT",
"glossPartOfSpeech": null,
"glossStatus": null,
"guided setup": null,
"guided tours": null,
"keywords": null,
"min-toc": null,
"mini": null,
"mini-to truec": null,
"mini-toc": "yes",
"mini_toc": null,
"minitoc": null,
"modification": null,
"now-assist-app-gen-video": null,
"order": null,
"page-type": null,
"page-type ": null,
"prodname": null,
"product": null,
"product_name": null,
"release": null,
"resourceID": null,
"roles": null,
"route_page": null,
"route_params_listId": null,
"route_params_table": null,
"route_params_type": null,
"route_type": null,
"setconfigurationproperties": null,
"topic": null,
"translation-type": "source",
"version": null,
"workflow": "Customer and Industry",
"workplace-srvc-delvry-ditamap": null
},
"page_id": "product/tmt-telecom-service-operations-mgt/concept/data-mapping.html",
"page_key": 55686931,
"preprocessed_PDF": "https://downloads.docs.servicenow.com/pdf/enus/servicenow-zurich-telecom-service-ops-enus.pdf",
"rating": null,
"read_time_data": {
"char_count": 6826,
"img_count": 2,
"read_time": 5,
"video_links": [
""
],
"word_count": 976
},
"related_links": [],
"search_title": null,
"title": "Mapping Nokia Altiplano CIs and Relationships in CMDB",
"topic_cluster": {
"clustered_by": {
"enabled": true,
"primary_key": "versions",
"primary_sort": "top-down",
"type": "subjecthead"
},
"clustered_labels": [
"versions"
],
"clustered_topics": [],
"clustering_title": "Zurich"
},
"topic_html": "<article class=\"hascomments\" data-page=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/data-mapping.html\" id=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/data-mapping.html\"><body id=\"data-mapping\"><main role=\"main\"><article role=\"article\" class=\"dita\" id=\"data-mapping\" aria-labelledby=\"title_data-mapping\">\n <h1 class=\"title topictitle1\" id=\"title_data-mapping\">Mapping Nokia Altiplano CIs and Relationships in CMDB</h1>\n \n \n <div class=\"body conbody\"><p class=\"shortdesc\">Use the Service Graph Connector for Nokia Altiplano to map discovered physical and logical network resources to telecom-aligned Configuration Item (CI) classes in the CMDB. The connector supports consistent service modeling,\n visibility into chassis-level components, and automation of logical and physical relationships.</p>\n <p class=\"p\">To confirm accurate CI classification and insertion, the connector uses the Robust Transform Engine (RTE) and Identification and Reconciliation Engine (IRE).</p>\n <p class=\"p\">The connector classifies and relates discovered CIs using telecom-specific models based on device type, function, and chassis structure. This helps maintain a clean and normalized CMDB across vendors. Discovered model names from Nokia\n Altiplano are automatically transformed into ServiceNow standard model identifiers and categories for slot and subslot components.</p>\n <section class=\"section\" id=\"data-mapping__section_tt1_q15_xfc\"><h2 id=\"d5786e48\" class=\"title sectiontitle\">CI mapping and relationships</h2>\n \n <div class=\"p\">The following tables describe how Altiplano CIs are represented in the CMDB and how they relate to each other across physical and logical layers.<div class=\"table-wrap\"><table count-columns=\"3\" class=\"table\" id=\"data-mapping__table_m5l_m1b_wfc\"><caption><span class=\"table--title-label\">Table 1. </span><span class=\"title\">CMDB CI Mapping and Relationships (Physical Layer)</span></caption><colgroup><col/><col/><col/></colgroup><thead class=\"thead\">\n <tr class=\"row\">\n <th class=\"entry\" id=\"data-mapping__table_m5l_m1b_wfc__entry__1\">CI Type</th>\n <th class=\"entry\" id=\"data-mapping__table_m5l_m1b_wfc__entry__2\">CMDB Table</th>\n <th class=\"entry\" id=\"data-mapping__table_m5l_m1b_wfc__entry__3\">Description and Relationships</th>\n </tr>\n </thead><tbody class=\"tbody\">\n <tr class=\"row\">\n <td class=\"entry\" headers=\"data-mapping__table_m5l_m1b_wfc__entry__1\">OLT CI</td>\n <td class=\"entry\" headers=\"data-mapping__table_m5l_m1b_wfc__entry__2\"><code class=\"ph codeph\">cmdb_ci_optical_line_terminal</code></td>\n <td class=\"entry\" headers=\"data-mapping__table_m5l_m1b_wfc__entry__3\">Represents the OLT device. Contains Slot CIs and Logical Network Interface CIs.</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry\" headers=\"data-mapping__table_m5l_m1b_wfc__entry__1\">ONU/ONT CI</td>\n <td class=\"entry\" headers=\"data-mapping__table_m5l_m1b_wfc__entry__2\"><code class=\"ph codeph\">cmdb_ci_optical_network_terminal</code> or <code class=\"ph codeph\">cmdb_ci_optical_network_unit</code></td>\n <td class=\"entry\" headers=\"data-mapping__table_m5l_m1b_wfc__entry__3\">Represents ONU or ONT devices. The class is determined by the system property <code class=\"ph codeph\">sn_sgc_altiplano.onu_ci_class</code>. Contains Network Interface CIs.</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry\" headers=\"data-mapping__table_m5l_m1b_wfc__entry__1\">Slot CI</td>\n <td class=\"entry\" headers=\"data-mapping__table_m5l_m1b_wfc__entry__2\"><code class=\"ph codeph\">cmdb_ci_container_slot</code></td>\n <td class=\"entry\" headers=\"data-mapping__table_m5l_m1b_wfc__entry__3\">Represents main chassis slots. Contained by OLT CIs. Contains Interface Card CIs (for example, LT/NT, PSU, fan). Model transformations are applied in the data source. For more information, see the above mentioned Model\n transformation for slot and subslot CIs table.</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry\" headers=\"data-mapping__table_m5l_m1b_wfc__entry__1\">Subslot CI</td>\n <td class=\"entry\" headers=\"data-mapping__table_m5l_m1b_wfc__entry__2\"><code class=\"ph codeph\">cmdb_ci_container_subslot</code></td>\n <td class=\"entry\" headers=\"data-mapping__table_m5l_m1b_wfc__entry__3\">Represents subcomponents within interface cards (for example, cages for SFPs). Contained by LT/NT cards. Contains transceiver card CIs. For more information, see the above mentioned Model transformation for slot and subslot\n CIs table.</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry\" headers=\"data-mapping__table_m5l_m1b_wfc__entry__1\">Interface Card CI</td>\n <td class=\"entry\" headers=\"data-mapping__table_m5l_m1b_wfc__entry__2\"><code class=\"ph codeph\">cmdb_ci_interface_card</code></td>\n <td class=\"entry\" headers=\"data-mapping__table_m5l_m1b_wfc__entry__3\">Represents LT/NT cards, transceivers, and control units. Can contain subslots and network interfaces.</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry\" headers=\"data-mapping__table_m5l_m1b_wfc__entry__1\">Network Interface CI</td>\n <td class=\"entry\" headers=\"data-mapping__table_m5l_m1b_wfc__entry__2\"><code class=\"ph codeph\">cmdb_ci_ni_interface</code></td>\n <td class=\"entry\" headers=\"data-mapping__table_m5l_m1b_wfc__entry__3\">Represents both physical (for example, PON, Ethernet) and logical (for example, VLAN) ports. Contained by interface cards or ONU/ONT CIs. Logical ports are related to physical ports using Members::Member of.</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry\" headers=\"data-mapping__table_m5l_m1b_wfc__entry__1\">Logical Connection CI</td>\n <td class=\"entry\" headers=\"data-mapping__table_m5l_m1b_wfc__entry__2\"><code class=\"ph codeph\">cmdb_ci_ni_logical_path</code></td>\n <td class=\"entry\" headers=\"data-mapping__table_m5l_m1b_wfc__entry__3\">Represents logical paths such as PON or VLAN between OLT and ONU. Defined with Port A and Port Z attributes referencing terminating Network Interface CIs. VLAN paths consume PON paths.</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry\" headers=\"data-mapping__table_m5l_m1b_wfc__entry__1\">IP Address CI</td>\n <td class=\"entry\" headers=\"data-mapping__table_m5l_m1b_wfc__entry__2\"><code class=\"ph codeph\">cmdb_ci_ip_address</code></td>\n <td class=\"entry\" headers=\"data-mapping__table_m5l_m1b_wfc__entry__3\">Represents discovered IP addresses for OLTs. Owned by the corresponding OLT CI.</td>\n </tr>\n </tbody></table></div></div>\n </section>\n <section class=\"section\" id=\"data-mapping__section_syv_s1b_wfc\"><h2 id=\"d5786e200\" class=\"title sectiontitle\">Key Relationship Examples</h2>\n \n <div class=\"p\">\n <ul class=\"ul\" id=\"data-mapping__ul_msk_s1b_wfc\">\n <li class=\"li\">Containment relationships<ul class=\"ul\" id=\"data-mapping__ul_nsk_s1b_wfc\">\n <li class=\"li\">OLT CI → contains Slot CI</li>\n <li class=\"li\">Slot CI → contains Interface Card CI</li>\n <li class=\"li\">Interface Card CI → contains Subslot CI</li>\n <li class=\"li\">Subslot CI → contains transceiver Interface Card CI</li>\n <li class=\"li\">ONU/ONT CI → contains Network Interface CIs</li>\n </ul></li>\n <li class=\"li\">Interface relationships:<ul class=\"ul\" id=\"data-mapping__ul_osk_s1b_wfc\">\n <li class=\"li\">Logical Connections -> terminated by Network Interfaces</li>\n <li class=\"li\">Network Interfaces -> members of Network Interfaces</li>\n </ul></li>\n <li class=\"li\">Logical path relationships:<ul class=\"ul\" id=\"data-mapping__ul_psk_s1b_wfc\">\n <li class=\"li\">VLAN path (parent) → consumes → PON path (child)</li>\n <li class=\"li\">Logical paths → terminate at → Network Interface CIs via Port A and Port Z</li>\n </ul></li>\n <li class=\"li\">Ownership: IP Address CI → owned by OLT device</li>\n </ul>\n </div>\n </section>\n <section class=\"section\" id=\"data-mapping__section_x3f_2db_wfc\"><h2 id=\"d5786e257\" class=\"title sectiontitle\">Supported models</h2>\n \n <div class=\"p\">\n <ol class=\"ol\" id=\"data-mapping__ol_txf_phy_yfc\">\n <li class=\"li\">Network equipment models (sn_ent_nw_equipment_model)<ul class=\"ul\" id=\"data-mapping__ul_hbl_nhy_yfc\">\n <li class=\"li\">The supported OLT is Nokia Lightspan MF-2, by default the model name is "Nokia MF-2"</li>\n <li class=\"li\">ONU/ONT models are manufacturer + ONU/ONT. the system property sn_sgc_altiplano.onu_ci_class defines if ONU or ONT will be used.</li>\n <li class=\"li\">If the model wasn’t found in the model table, a new model is created in the CI. and the CI will be created as "Network gear"</li>\n </ul></li>\n <li class=\"li\">Equipment holder models: (sn_ent_nw_holder_model)<ul class=\"ul\" id=\"data-mapping__ul_ibl_nhy_yfc\">\n <li class=\"li\">Slots models: "Traffic Slot", "FAN Slot", "Power Slot"</li>\n <li class=\"li\">Subslots models: "SFP Subslot"</li>\n <li class=\"li\">The used model name can be customized by the customer through the Altiplano extension point (sn_sgc_altiplano.AltiplanoCustomizedModels)</li>\n <li class=\"li\">If the model wasn’t found in the model table, a new model is created in the CI.</li>\n </ul></li>\n <li class=\"li\">Network card models (sn_ent_nw_card_model)<ul class=\"ul\" id=\"data-mapping__ul_jbl_nhy_yfc\">\n <li class=\"li\">Card models are found by the model name, manufacturer, and model number discovered from the Altiplano API</li>\n <li class=\"li\">If the model wasn’t found in the model table, a new model is created in the CI.</li>\n </ul></li>\n <li class=\"li\">Network Interface Models: (sn_ent_nw_interface_model).<ul class=\"ul\" id=\"data-mapping__ul_kbl_nhy_yfc\">\n <li class=\"li\">Ethernet ports models are found by the "port bandwidth" column in the Network Interface table (sn_ent_nw_interface_model). the port bandwidth of the port CI is located by the discovered port speed in the Bandwidth table\n (bandwidth)</li>\n <li class=\"li\">PON physical ports models: "PON Access Interface", "PON Network Interfaces"</li>\n <li class=\"li\">Logical ports models: "ENET Interface", "VLAN Interface", "LAG Interface", PON Logical Interface"</li>\n <li class=\"li\">If the model wasn’t found in the model table, the reference to the "Model ID" will remain empty.</li>\n </ul></li>\n <li class=\"li\">Logical network connection models (sn_ent_logical_nw_connection_model)<ul class=\"ul\" id=\"data-mapping__ul_lbl_nhy_yfc\">\n <li class=\"li\">PON Access Path</li>\n <li class=\"li\">VLAN Path</li>\n <li class=\"li\">If the model wasn’t found in the model table, the reference to the "Model ID" will remain empty.</li>\n </ul></li>\n </ol>\n <div class=\"note note note_note\"><span class=\"note__title\">Note:</span> \n <ul class=\"ul\" id=\"data-mapping__ul_mbl_nhy_yfc\">\n <li class=\"li\">If the connector cannot match a discovered equipment to an existing model in the product model table the CI is created as <code class=\"ph codeph\">Network Gear</code> by default.</li>\n <li class=\"li\">If demo data is installed, default models are created for OLT, ONU, ONT, Slots, Subslots, Cards, Network Interfaces, and Logical connections.</li>\n <li class=\"li\">Equipment and Equipment holder model names can be customized using an extension point</li>\n </ul>\n </div>\n </div>\n </section>\n <section class=\"section\" id=\"data-mapping__section_uq3_315_xfc\"><h2 id=\"d5786e361\" class=\"title sectiontitle\">Model transformation for slot and subslot CIs</h2>\n \n <p class=\"p\">During ingestion, specific discovered model names are mapped to predefined CMDB model identifiers to confirm consistent slot categorization. The transformation logic is embedded in the SGC data source script and applies to the Nokia\n Altiplano source.</p>\n <p class=\"p\">Slot components such as fan, power, and traffic slots are mapped to the <code class=\"ph codeph\">Slot</code> category in the CMDB. Subslot components such as SFP cages or synthetic subslots are mapped to the <code class=\"ph codeph\">Subslot</code> category in the\n CMDB.</p>\n <div class=\"table-wrap\"><table count-columns=\"4\" class=\"table\" id=\"data-mapping__table_utm_k15_xfc\"><caption><span class=\"table--title-label\">Table 2. </span><span class=\"title\">Example: Nokia Altiplano slot and sub slot model mappings</span></caption><colgroup><col/><col/><col/><col/></colgroup><thead class=\"thead\">\n <tr class=\"row\">\n <th class=\"entry\" id=\"data-mapping__table_utm_k15_xfc__entry__1\">Source</th>\n <th class=\"entry\" id=\"data-mapping__table_utm_k15_xfc__entry__2\">Discovered Model Name</th>\n <th class=\"entry\" id=\"data-mapping__table_utm_k15_xfc__entry__3\">Target CMDB Model ID</th>\n <th class=\"entry\" id=\"data-mapping__table_utm_k15_xfc__entry__4\">Model Category</th>\n </tr>\n </thead><tbody class=\"tbody\">\n <tr class=\"row\">\n <td class=\"entry\" headers=\"data-mapping__table_utm_k15_xfc__entry__1\">Altiplano</td>\n <td class=\"entry\" headers=\"data-mapping__table_utm_k15_xfc__entry__2\">slot-fan</td>\n <td class=\"entry\" headers=\"data-mapping__table_utm_k15_xfc__entry__3\">Fan Slot</td>\n <td class=\"entry\" headers=\"data-mapping__table_utm_k15_xfc__entry__4\">Slot</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry\" headers=\"data-mapping__table_utm_k15_xfc__entry__1\">Altiplano</td>\n <td class=\"entry\" headers=\"data-mapping__table_utm_k15_xfc__entry__2\">slot-lt</td>\n <td class=\"entry\" headers=\"data-mapping__table_utm_k15_xfc__entry__3\">Traffic Slot</td>\n <td class=\"entry\" headers=\"data-mapping__table_utm_k15_xfc__entry__4\">Slot</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry\" headers=\"data-mapping__table_utm_k15_xfc__entry__1\">Altiplano</td>\n <td class=\"entry\" headers=\"data-mapping__table_utm_k15_xfc__entry__2\">cage</td>\n <td class=\"entry\" headers=\"data-mapping__table_utm_k15_xfc__entry__3\">SFP Subslot</td>\n <td class=\"entry\" headers=\"data-mapping__table_utm_k15_xfc__entry__4\">Subslot</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry\" headers=\"data-mapping__table_utm_k15_xfc__entry__1\">Altiplano</td>\n <td class=\"entry\" headers=\"data-mapping__table_utm_k15_xfc__entry__2\">slot-nt</td>\n <td class=\"entry\" headers=\"data-mapping__table_utm_k15_xfc__entry__3\">Traffic Slot</td>\n <td class=\"entry\" headers=\"data-mapping__table_utm_k15_xfc__entry__4\">Slot</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry\" headers=\"data-mapping__table_utm_k15_xfc__entry__1\">Altiplano</td>\n <td class=\"entry\" headers=\"data-mapping__table_utm_k15_xfc__entry__2\">synthetic nt-slot</td>\n <td class=\"entry\" headers=\"data-mapping__table_utm_k15_xfc__entry__3\">SFP Subslot</td>\n <td class=\"entry\" headers=\"data-mapping__table_utm_k15_xfc__entry__4\">Subslot</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry\" headers=\"data-mapping__table_utm_k15_xfc__entry__1\">Altiplano</td>\n <td class=\"entry\" headers=\"data-mapping__table_utm_k15_xfc__entry__2\">slot-psu</td>\n <td class=\"entry\" headers=\"data-mapping__table_utm_k15_xfc__entry__3\">Power Slot</td>\n <td class=\"entry\" headers=\"data-mapping__table_utm_k15_xfc__entry__4\">Slot</td>\n </tr>\n </tbody></table></div>\n </section>\n <section class=\"section\" id=\"data-mapping__section_z2f_2db_wfc\"><h2 id=\"d5786e509\" class=\"title sectiontitle\">CI relationship structure</h2>\n \n <p class=\"p\">The following infographics describes the CI relationships.</p>\n <p class=\"p\"><img src=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/../images/ci-relationships.png?_LANG=enus\" class=\"image\" id=\"data-mapping__image_qty_qcb_wfc\" alt=\"CI relationships structure\"/><img src=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/../images/ci-relationship-diagram.png?_LANG=enus\" class=\"image\" id=\"data-mapping__image_f3n_tnt_xfc\" alt=\"CI relationship structure\"/></p>\n </section>\n <section class=\"section\" id=\"data-mapping__section_rpp_ycb_wfc\"><h2 id=\"d5786e530\" class=\"title sectiontitle\">Example: OLT to ONU Structure</h2>\n \n <div class=\"p\">The following structure enables end-to-end traceability from OLT through its hardware layers to the connected ONU and associated logical paths.<pre class=\"prettyprint language-plaintext\"><code class=\"pre codeblock language-plaintext\">OLT (cmdb_ci_optical_line_terminal)\n├── Slot\n│ ├── Interface Card (LT/NT)\n│ │ ├── Subslot\n│ │ │ └── Interface Card (Transceiver)\n│ │ │ └── Network Interface (PON port)\n├── Logical Connections (PON/VLAN) → Connected to →\n└── ONU/ONT (cmdb_ci_optical_network_terminal)\n └── Network Interface (ONT port)\n</code></pre></div>\n </section>\n </div>\n</article></main></body></article>",
"topic_language": "enus",
"views": 0,
"your_rating": null
} | # Mapping Nokia Altiplano CIs and Relationships in CMDB
Use the Service Graph Connector for Nokia Altiplano to map discovered physical and logical network resources to telecom-aligned Configuration Item (CI) classes in the CMDB. The connector supports consistent service modeling,
visibility into chassis-level components, and automation of logical and physical relationships.
To confirm accurate CI classification and insertion, the connector uses the Robust Transform Engine (RTE) and Identification and Reconciliation Engine (IRE).
The connector classifies and relates discovered CIs using telecom-specific models based on device type, function, and chassis structure. This helps maintain a clean and normalized CMDB across vendors. Discovered model names from Nokia
Altiplano are automatically transformed into ServiceNow standard model identifiers and categories for slot and subslot components.
## CI mapping and relationships
The following tables describe how Altiplano CIs are represented in the CMDB and how they relate to each other across physical and logical layers.
Table 1. CMDB CI Mapping and Relationships (Physical Layer)
| CI Type | CMDB Table | Description and Relationships |
| --- | --- | --- |
| OLT CI | `cmdb_ci_optical_line_terminal` | Represents the OLT device. Contains Slot CIs and Logical Network Interface CIs. |
| ONU/ONT CI | `cmdb_ci_optical_network_terminal` or `cmdb_ci_optical_network_unit` | Represents ONU or ONT devices. The class is determined by the system property `sn_sgc_altiplano.onu_ci_class`. Contains Network Interface CIs. |
| Slot CI | `cmdb_ci_container_slot` | Represents main chassis slots. Contained by OLT CIs. Contains Interface Card CIs (for example, LT/NT, PSU, fan). Model transformations are applied in the data source. For more information, see the above mentioned Model transformation for slot and subslot CIs table. |
| Subslot CI | `cmdb_ci_container_subslot` | Represents subcomponents within interface cards (for example, cages for SFPs). Contained by LT/NT cards. Contains transceiver card CIs. For more information, see the above mentioned Model transformation for slot and subslot CIs table. |
| Interface Card CI | `cmdb_ci_interface_card` | Represents LT/NT cards, transceivers, and control units. Can contain subslots and network interfaces. |
| Network Interface CI | `cmdb_ci_ni_interface` | Represents both physical (for example, PON, Ethernet) and logical (for example, VLAN) ports. Contained by interface cards or ONU/ONT CIs. Logical ports are related to physical ports using Members::Member of. |
| Logical Connection CI | `cmdb_ci_ni_logical_path` | Represents logical paths such as PON or VLAN between OLT and ONU. Defined with Port A and Port Z attributes referencing terminating Network Interface CIs. VLAN paths consume PON paths. |
| IP Address CI | `cmdb_ci_ip_address` | Represents discovered IP addresses for OLTs. Owned by the corresponding OLT CI. |
## Key Relationship Examples
* Containment relationships
+ OLT CI → contains Slot CI
+ Slot CI → contains Interface Card CI
+ Interface Card CI → contains Subslot CI
+ Subslot CI → contains transceiver Interface Card CI
+ ONU/ONT CI → contains Network Interface CIs
* Interface relationships:
+ Logical Connections -> terminated by Network Interfaces
+ Network Interfaces -> members of Network Interfaces
* Logical path relationships:
+ VLAN path (parent) → consumes → PON path (child)
+ Logical paths → terminate at → Network Interface CIs via Port A and Port Z
* Ownership: IP Address CI → owned by OLT device
## Supported models
1. Network equipment models (sn\_ent\_nw\_equipment\_model)
* The supported OLT is Nokia Lightspan MF-2, by default the model name is "Nokia MF-2"
* ONU/ONT models are manufacturer + ONU/ONT. the system property sn\_sgc\_altiplano.onu\_ci\_class defines if ONU or ONT will be used.
* If the model wasn’t found in the model table, a new model is created in the CI. and the CI will be created as "Network gear"
2. Equipment holder models: (sn\_ent\_nw\_holder\_model)
* Slots models: "Traffic Slot", "FAN Slot", "Power Slot"
* Subslots models: "SFP Subslot"
* The used model name can be customized by the customer through the Altiplano extension point (sn\_sgc\_altiplano.AltiplanoCustomizedModels)
* If the model wasn’t found in the model table, a new model is created in the CI.
3. Network card models (sn\_ent\_nw\_card\_model)
* Card models are found by the model name, manufacturer, and model number discovered from the Altiplano API
* If the model wasn’t found in the model table, a new model is created in the CI.
4. Network Interface Models: (sn\_ent\_nw\_interface\_model).
* Ethernet ports models are found by the "port bandwidth" column in the Network Interface table (sn\_ent\_nw\_interface\_model). the port bandwidth of the port CI is located by the discovered port speed in the Bandwidth table
(bandwidth)
* PON physical ports models: "PON Access Interface", "PON Network Interfaces"
* Logical ports models: "ENET Interface", "VLAN Interface", "LAG Interface", PON Logical Interface"
* If the model wasn’t found in the model table, the reference to the "Model ID" will remain empty.
5. Logical network connection models (sn\_ent\_logical\_nw\_connection\_model)
* PON Access Path
* VLAN Path
* If the model wasn’t found in the model table, the reference to the "Model ID" will remain empty.
Note:
* If the connector cannot match a discovered equipment to an existing model in the product model table the CI is created as `Network Gear` by default.
* If demo data is installed, default models are created for OLT, ONU, ONT, Slots, Subslots, Cards, Network Interfaces, and Logical connections.
* Equipment and Equipment holder model names can be customized using an extension point
## Model transformation for slot and subslot CIs
During ingestion, specific discovered model names are mapped to predefined CMDB model identifiers to confirm consistent slot categorization. The transformation logic is embedded in the SGC data source script and applies to the Nokia
Altiplano source.
Slot components such as fan, power, and traffic slots are mapped to the `Slot` category in the CMDB. Subslot components such as SFP cages or synthetic subslots are mapped to the `Subslot` category in the
CMDB.
Table 2. Example: Nokia Altiplano slot and sub slot model mappings
| Source | Discovered Model Name | Target CMDB Model ID | Model Category |
| --- | --- | --- | --- |
| Altiplano | slot-fan | Fan Slot | Slot |
| Altiplano | slot-lt | Traffic Slot | Slot |
| Altiplano | cage | SFP Subslot | Subslot |
| Altiplano | slot-nt | Traffic Slot | Slot |
| Altiplano | synthetic nt-slot | SFP Subslot | Subslot |
| Altiplano | slot-psu | Power Slot | Slot |
## CI relationship structure
The following infographics describes the CI relationships.
## Example: OLT to ONU Structure
The following structure enables end-to-end traceability from OLT through its hardware layers to the connected ONU and associated logical paths.
```None
OLT (cmdb_ci_optical_line_terminal)
├── Slot
│ ├── Interface Card (LT/NT)
│ │ ├── Subslot
│ │ │ └── Interface Card (Transceiver)
│ │ │ └── Network Interface (PON port)
├── Logical Connections (PON/VLAN) → Connected to →
└── ONU/ONT (cmdb_ci_optical_network_terminal)
└── Network Interface (ONT port)
```
| ---
title: Mapping Nokia Altiplano CIs and Relationships in CMDB
description: Use the Service Graph Connector for Nokia Altiplano to map discovered
physical and logical network resources to telecom-aligned Configuration Item (CI)
classes in the CMDB. The connector supports consistent service modeling, visibility
into chassis-level components, and automation of logical and
keywords: []
breadcrumbs:
- Telecommunications Service Operations Management
- Configuring Telecommunications Service Operations Management
- Set up Telecom Visibility
- Configuring Nokia Altiplano service graph connector
---
# Mapping Nokia Altiplano CIs and Relationships in CMDB
Use the Service Graph Connector for Nokia Altiplano to map discovered physical and logical network resources to telecom-aligned Configuration Item (CI) classes in the CMDB. The connector supports consistent service modeling,
visibility into chassis-level components, and automation of logical and physical relationships.
To confirm accurate CI classification and insertion, the connector uses the Robust Transform Engine (RTE) and Identification and Reconciliation Engine (IRE).
The connector classifies and relates discovered CIs using telecom-specific models based on device type, function, and chassis structure. This helps maintain a clean and normalized CMDB across vendors. Discovered model names from Nokia
Altiplano are automatically transformed into ServiceNow standard model identifiers and categories for slot and subslot components.
## CI mapping and relationships
The following tables describe how Altiplano CIs are represented in the CMDB and how they relate to each other across physical and logical layers.
Table 1. CMDB CI Mapping and Relationships (Physical Layer)
| CI Type | CMDB Table | Description and Relationships |
| --- | --- | --- |
| OLT CI | `cmdb_ci_optical_line_terminal` | Represents the OLT device. Contains Slot CIs and Logical Network Interface CIs. |
| ONU/ONT CI | `cmdb_ci_optical_network_terminal` or `cmdb_ci_optical_network_unit` | Represents ONU or ONT devices. The class is determined by the system property `sn_sgc_altiplano.onu_ci_class`. Contains Network Interface CIs. |
| Slot CI | `cmdb_ci_container_slot` | Represents main chassis slots. Contained by OLT CIs. Contains Interface Card CIs (for example, LT/NT, PSU, fan). Model transformations are applied in the data source. For more information, see the above mentioned Model transformation for slot and subslot CIs table. |
| Subslot CI | `cmdb_ci_container_subslot` | Represents subcomponents within interface cards (for example, cages for SFPs). Contained by LT/NT cards. Contains transceiver card CIs. For more information, see the above mentioned Model transformation for slot and subslot CIs table. |
| Interface Card CI | `cmdb_ci_interface_card` | Represents LT/NT cards, transceivers, and control units. Can contain subslots and network interfaces. |
| Network Interface CI | `cmdb_ci_ni_interface` | Represents both physical (for example, PON, Ethernet) and logical (for example, VLAN) ports. Contained by interface cards or ONU/ONT CIs. Logical ports are related to physical ports using Members::Member of. |
| Logical Connection CI | `cmdb_ci_ni_logical_path` | Represents logical paths such as PON or VLAN between OLT and ONU. Defined with Port A and Port Z attributes referencing terminating Network Interface CIs. VLAN paths consume PON paths. |
| IP Address CI | `cmdb_ci_ip_address` | Represents discovered IP addresses for OLTs. Owned by the corresponding OLT CI. |
## Key Relationship Examples
* Containment relationships
+ OLT CI → contains Slot CI
+ Slot CI → contains Interface Card CI
+ Interface Card CI → contains Subslot CI
+ Subslot CI → contains transceiver Interface Card CI
+ ONU/ONT CI → contains Network Interface CIs
* Interface relationships:
+ Logical Connections -> terminated by Network Interfaces
+ Network Interfaces -> members of Network Interfaces
* Logical path relationships:
+ VLAN path (parent) → consumes → PON path (child)
+ Logical paths → terminate at → Network Interface CIs via Port A and Port Z
* Ownership: IP Address CI → owned by OLT device
## Supported models
1. Network equipment models (sn\_ent\_nw\_equipment\_model)
* The supported OLT is Nokia Lightspan MF-2, by default the model name is "Nokia MF-2"
* ONU/ONT models are manufacturer + ONU/ONT. the system property sn\_sgc\_altiplano.onu\_ci\_class defines if ONU or ONT will be used.
* If the model wasn’t found in the model table, a new model is created in the CI. and the CI will be created as "Network gear"
2. Equipment holder models: (sn\_ent\_nw\_holder\_model)
* Slots models: "Traffic Slot", "FAN Slot", "Power Slot"
* Subslots models: "SFP Subslot"
* The used model name can be customized by the customer through the Altiplano extension point (sn\_sgc\_altiplano.AltiplanoCustomizedModels)
* If the model wasn’t found in the model table, a new model is created in the CI.
3. Network card models (sn\_ent\_nw\_card\_model)
* Card models are found by the model name, manufacturer, and model number discovered from the Altiplano API
* If the model wasn’t found in the model table, a new model is created in the CI.
4. Network Interface Models: (sn\_ent\_nw\_interface\_model).
* Ethernet ports models are found by the "port bandwidth" column in the Network Interface table (sn\_ent\_nw\_interface\_model). the port bandwidth of the port CI is located by the discovered port speed in the Bandwidth table
(bandwidth)
* PON physical ports models: "PON Access Interface", "PON Network Interfaces"
* Logical ports models: "ENET Interface", "VLAN Interface", "LAG Interface", PON Logical Interface"
* If the model wasn’t found in the model table, the reference to the "Model ID" will remain empty.
5. Logical network connection models (sn\_ent\_logical\_nw\_connection\_model)
* PON Access Path
* VLAN Path
* If the model wasn’t found in the model table, the reference to the "Model ID" will remain empty.
Note:
* If the connector cannot match a discovered equipment to an existing model in the product model table the CI is created as `Network Gear` by default.
* If demo data is installed, default models are created for OLT, ONU, ONT, Slots, Subslots, Cards, Network Interfaces, and Logical connections.
* Equipment and Equipment holder model names can be customized using an extension point
## Model transformation for slot and subslot CIs
During ingestion, specific discovered model names are mapped to predefined CMDB model identifiers to confirm consistent slot categorization. The transformation logic is embedded in the SGC data source script and applies to the Nokia
Altiplano source.
Slot components such as fan, power, and traffic slots are mapped to the `Slot` category in the CMDB. Subslot components such as SFP cages or synthetic subslots are mapped to the `Subslot` category in the
CMDB.
Table 2. Example: Nokia Altiplano slot and sub slot model mappings
| Source | Discovered Model Name | Target CMDB Model ID | Model Category |
| --- | --- | --- | --- |
| Altiplano | slot-fan | Fan Slot | Slot |
| Altiplano | slot-lt | Traffic Slot | Slot |
| Altiplano | cage | SFP Subslot | Subslot |
| Altiplano | slot-nt | Traffic Slot | Slot |
| Altiplano | synthetic nt-slot | SFP Subslot | Subslot |
| Altiplano | slot-psu | Power Slot | Slot |
## CI relationship structure
The following infographics describes the CI relationships.
## Example: OLT to ONU Structure
The following structure enables end-to-end traceability from OLT through its hardware layers to the connected ONU and associated logical paths.
```None
OLT (cmdb_ci_optical_line_terminal)
├── Slot
│ ├── Interface Card (LT/NT)
│ │ ├── Subslot
│ │ │ └── Interface Card (Transceiver)
│ │ │ └── Network Interface (PON port)
├── Logical Connections (PON/VLAN) → Connected to →
└── ONU/ONT (cmdb_ci_optical_network_terminal)
└── Network Interface (ONT port)
```
|
https://www.servicenow.com/docs/en-US/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/discrepancy-identification-types-of-discrepancies.html | https://servicenow-be-prod.servicenow.com/api/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/discrepancy-identification-types-of-discrepancies.html | 2025-08-02 | daily | 0.5 | 268.xml | en-US | zurich-telecom-service-ops | product/tmt-telecom-service-operations-mgt/concept/discrepancy-identification-types-of-discrepancies.html | zurich | Discrepancy identification – types of discrepancies | The Telecom Discrepancy Identification and Reconciliation capability identifies and classifies mismatches between the network state (as discovered through TSOM Discovery or Service Graph Connectors) and the inventory data stored in the CMDB or TNI. | [] | [
"Telecommunications Service Operations Management",
"Exploring Telecommunications Service Operations Management",
"Telecom Visibility",
"Telecom Discrepancy Identification and Reconciliation"
] | <article class="hascomments" data-page="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/discrepancy-identification-types-of-discrepancies.html" id="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/discrepancy-identification-types-of-discrepancies.html"><body id="discrepancy-identification-types-of-discrepancies"><main role="main"><article role="article" class="dita" id="discrepancy-identification-types-of-discrepancies" aria-labelledby="title_discrepancy-identification-types-of-discrepancies">
<h1 class="title topictitle1" id="title_discrepancy-identification-types-of-discrepancies">Discrepancy identification – types of discrepancies</h1>
<div class="body conbody"><p class="shortdesc">The Telecom Discrepancy Identification and Reconciliation capability identifies and classifies mismatches between the network state (as discovered through TSOM Discovery or Service Graph Connectors) and the inventory data
stored in the CMDB or TNI.</p>
<p class="p">Discrepancy identification is powered by the CMDB Compliance Certification Audit, which:</p>
<ul class="ul" id="discrepancy-identification-types-of-discrepancies__ul_yfr_nww_tfc">
<li class="li">Runs on CI and relationship data.</li>
<li class="li">Compares discovered and inventoried records.</li>
<li class="li">Generates Follow-on tasks when mismatches are detected.</li>
</ul>
<section class="section" id="discrepancy-identification-types-of-discrepancies__section_xdx_4ww_tfc"><h2 id="d1040e57" class="title sectiontitle">Discrepancy types</h2>
<div class="p">The audit process identifies discrepancies by comparing discovered network data with the existing inventory in the CMDB/TNI. Discrepancies fall into two main categories:<dl class="dl">
<dt class="dt dlterm">Missing in network - entities existing in inventory but missing in network</dt>
<dd class="dd">Definition: A CI is detected by Discovery but is either missing from the CMDB/TNI or incorrectly represented. For example, Discovery detects Card05 installed in Slot04, but the CMDB still lists Card04, or worse, shows both
Card04 and Card05 in the same slot—violating cardinality or model constraints.<div class="p">Impact:<ul class="ul" id="discrepancy-identification-types-of-discrepancies__ul_g5h_d5c_5fc">
<li class="li">A discrepancy task is generated to highlight the data conflict.</li>
<li class="li">Optional remediation subflows may be triggered to reconcile the data by retiring outdated records or updating slot assignments.</li>
</ul></div></dd>
<dt class="dt dlterm">Mismatched configuration items (CIs) - entities that exist in inventory and network but differ in attribute values and hierarchical relationships</dt>
<dd class="dd">Definition: The CI exists in both Discovery and CMDB/TNI, but discrepancies exist in relationships, hierarchy, or attribute values. The following are the sub types:<ul class="ul" id="discrepancy-identification-types-of-discrepancies__ul_i5h_d5c_5fc">
<li class="li">Hierarchy Mismatches - Occur when the structural relationships between CIs (e.g., parent-child associations) are inconsistent. The following are the examples:<ul class="ul" id="discrepancy-identification-types-of-discrepancies__ul_j5h_d5c_5fc">
<li class="li">A chassis contains more child cards than allowed by the model definition.</li>
<li class="li">A card is incorrectly associated with a slot in the CMDB that does not align with Discovery data. The validation sources are:<ul class="ul" id="discrepancy-identification-types-of-discrepancies__ul_b43_djy_yfc">
<li class="li"><code class="ph codeph">cmdb_rel_ci</code> records for <code class="ph codeph">Contains::Contained by</code> relationships.</li>
<li class="li"><code class="ph codeph">sn_ni_core_network_model_relationship</code> table for enforcing model-specific constraints.</li>
</ul></li>
</ul></li>
<li class="li">Attribute Value Mismatches - Involve discrepancies in CI field-level properties. The common issues are:<ul class="ul" id="discrepancy-identification-types-of-discrepancies__ul_k5h_d5c_5fc">
<li class="li">Outdated or incorrect Discovery Dates.</li>
<li class="li">Inaccurate Model Configurations.</li>
<li class="li">Invalid Slot Assignments that breach model rules.</li>
</ul><div class="p">The impact is the affected records are marked as failed in audit reports. Follow-On Tasks may invoke context-specific remediation subflows to realign inventory data with the actual network state.<div class="note note note_note"><span class="note__title">Note:</span> For more
information, see <a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/task/configure-attribute-value-discrepancy-in-cmdb-360.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/configure-attribute-value-discrepancy-in-cmdb-360.html" class="xref" title="Configure attribute comparison settings in CMDB 360 to detect data inconsistencies across multiple discovery sources.">Configure attribute value discrepancy in CMDB 360</a>.</div></div></li>
</ul></dd>
</dl></div>
</section>
</div>
<nav role="navigation"></nav><nav role="navigation" class="tasksNavigation"></nav><nav role="navigation" class="related-links"><div class="col-md-4"><dt>Related tasks</dt><dd><ul><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/task/configure-telecom-reconciliation.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/configure-telecom-reconciliation.html" class="link" title="Activate the Telecom Discrepancy Identification and Reconciliation feature (part of the Telecom Visibility plugin) to ensure consistency between telecom network resources discovered in the live network and the data represented in the CMDB or Telecom Network Inventory (TNI). This feature helps detect and remediate mismatches automatically, supporting service accuracy and data integrity across your telecom environment.">Activate Telecom Discrepancy Identification and Reconciliation</a></li><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/task/run-audits.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/run-audits.html" class="link" title="The Telecom Discrepancy Audit validates the integrity of configuration items (CIs) and relationships across your telecom inventory using the CMDB Compliance framework.">Run Telecom Discrepancy audit</a></li></ul></dd></div></nav>
</article></main></body></article> | {
"attachments": {
"all_attachments": null,
"topic_attachments": []
},
"available_languages": [
"enus"
],
"breadcrumbs": [
{
"title": "Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html"
},
{
"title": "Exploring Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/exploring-tsom.html"
},
{
"title": "Telecom Visibility",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/tsom-visibility.html"
},
{
"title": "Telecom Discrepancy Identification and Reconciliation",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/exploring-telecom-reconciliation.html"
}
],
"breadcrumbs_html": "<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops\">Zurich Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html\">Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/exploring-tsom.html\">Exploring Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/tsom-visibility.html\">Telecom Visibility</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/exploring-telecom-reconciliation.html\">Telecom Discrepancy Identification and Reconciliation</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<span class=\"active\">Discrepancy identification – types of discrepancies</span>",
"bundle_id": "zurich-telecom-service-ops",
"bundle_key": 2733,
"bundle_landing_page": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html",
"bundle_subtitle": null,
"bundle_title": "Zurich Telecommunications Service Operations Management",
"canonical_link": null,
"dates": {
"Added on": "2025-08-02T00:48:08.794016Z",
"Created on": "2025-06-25T00:00:00Z",
"Initial upload": "2025-07-30T22:24:33.519043Z",
"Updated on": "2025-07-31T00:00:00Z"
},
"dislike_url": "https://servicenow-be-prod.servicenow.com/dislike/55686932",
"dislikes": 0,
"es_archived_content": false,
"is_in_fav": false,
"is_liked": null,
"is_watched": false,
"keywords": [
" zurich zurich"
],
"labels": [
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "zurich",
"navtitle": "Zurich",
"outputclasses": [],
"subjectHeadId": "versions",
"subjectheadNavtitle": "Versions",
"visibility": "show-facet"
},
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "tsom",
"navtitle": "Telecommunications Service Operations Management",
"outputclasses": [],
"subjectHeadId": "products",
"subjectheadNavtitle": "Products",
"visibility": "show-facet"
}
],
"labels_text": "Versions > Zurich; Products > CRM and Industry Products > Telecommunications Media and Technology Assurance > Telecommunications Service Operations Management",
"like_url": "https://servicenow-be-prod.servicenow.com/like/55686932",
"likes": 0,
"metadata": {
"AI Search": null,
"AI Search Assist": null,
"Application Insights": null,
"Capabilities": null,
"Code Signing": null,
"Contextual Search": null,
"DC.contributor": null,
"DC.coverage": null,
"DC.creator": "ServiceNow",
"DC.date.created": "2025-06-25T15:40:31+05:30",
"DC.date.modified": "2025-07-31",
"DC.format": "HTML5",
"DC.identifier": "discrepancy-identification-types-of-discrepancies",
"DC.language": null,
"DC.relation": "../task/configure-telecom-reconciliation.html",
"DC.rights.owner": "(C) Copyright 2025",
"DC.subject": null,
"DC.type": "concept",
"Data Discovery": null,
"Data Policy": null,
"Data Privacy": null,
"Discovery": null,
"External Content for AI Search": null,
"Field Administration": null,
"Field Normalization": null,
"Key Management Framework": null,
"Localization Framework": null,
"Now Platform": null,
"PlatSec": null,
"Platform": null,
"Platform Administration": null,
"Platform Performance": null,
"Platform Privacy": null,
"Proactive Triggers": null,
"Process Optimization": null,
"RN doc editing record number": null,
"Search Administration": null,
"Secrets Management": null,
"ServiceNow AI Platform": null,
"State Model": null,
"Subscription Management": null,
"Task Communications Management": null,
"Timeline Visualizations": null,
"User Administration": null,
"User Experience Analytics": null,
"Zing": null,
"ai-now-assist": null,
"app-name": null,
"app_route": null,
"azureapimanagemen": null,
"change-completed": null,
"change-item": null,
"change-request-id": null,
"change-request-reference": null,
"com.glide.embedded_help.category": null,
"component": null,
"copyright": "(C) Copyright 2025",
"crossroads": null,
"data": null,
"description": "The Telecom Discrepancy Identification and Reconciliation capability identifies and classifies mismatches between the network state (as discovered through TSOM Discovery or Service Graph Connectors) and the inventory data stored in the CMDB or TNI.",
"dominant_bundle": null,
"erp-canvas-video": null,
"fsm-mobile": null,
"fsm-route": null,
"fsm-sched-opt": null,
"fsm-wrk-order": null,
"genai-round-7": null,
"generator": "DITA-OT",
"glossPartOfSpeech": null,
"glossStatus": null,
"guided setup": null,
"guided tours": null,
"keywords": null,
"min-toc": null,
"mini": null,
"mini-to truec": null,
"mini-toc": "yes",
"mini_toc": null,
"minitoc": null,
"modification": null,
"now-assist-app-gen-video": null,
"order": null,
"page-type": null,
"page-type ": null,
"prodname": null,
"product": null,
"product_name": null,
"release": null,
"resourceID": null,
"roles": null,
"route_page": null,
"route_params_listId": null,
"route_params_table": null,
"route_params_type": null,
"route_type": null,
"setconfigurationproperties": null,
"topic": null,
"translation-type": "source",
"version": null,
"workflow": "Customer and Industry",
"workplace-srvc-delvry-ditamap": null
},
"page_id": "product/tmt-telecom-service-operations-mgt/concept/discrepancy-identification-types-of-discrepancies.html",
"page_key": 55686932,
"preprocessed_PDF": "https://downloads.docs.servicenow.com/pdf/enus/servicenow-zurich-telecom-service-ops-enus.pdf",
"rating": null,
"read_time_data": {
"char_count": 2601,
"img_count": 0,
"read_time": 2,
"video_links": [
""
],
"word_count": 356
},
"related_links": [
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "Activate the Telecom Discrepancy Identification and Reconciliation feature (part of the Telecom Visibility plugin) to ensure consistency between telecom network resources discovered in the live network and the data represented in the CMDB or Telecom Network Inventory (TNI). This feature helps detect and remediate mismatches automatically, supporting service accuracy and data integrity across your telecom environment.",
"title": "Activate Telecom Discrepancy Identification and Reconciliation",
"topic": "/product/tmt-telecom-service-operations-mgt/task/configure-telecom-reconciliation.html",
"type": "task",
"url": null
},
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "The Telecom Discrepancy Audit validates the integrity of configuration items (CIs) and relationships across your telecom inventory using the CMDB Compliance framework.",
"title": "Run Telecom Discrepancy audit",
"topic": "/product/tmt-telecom-service-operations-mgt/task/run-audits.html",
"type": "task",
"url": null
}
],
"search_title": null,
"title": "Discrepancy identification – types of discrepancies",
"topic_cluster": {
"clustered_by": {
"enabled": true,
"primary_key": "versions",
"primary_sort": "top-down",
"type": "subjecthead"
},
"clustered_labels": [
"versions"
],
"clustered_topics": [],
"clustering_title": "Zurich"
},
"topic_html": "<article class=\"hascomments\" data-page=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/discrepancy-identification-types-of-discrepancies.html\" id=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/discrepancy-identification-types-of-discrepancies.html\"><body id=\"discrepancy-identification-types-of-discrepancies\"><main role=\"main\"><article role=\"article\" class=\"dita\" id=\"discrepancy-identification-types-of-discrepancies\" aria-labelledby=\"title_discrepancy-identification-types-of-discrepancies\">\n <h1 class=\"title topictitle1\" id=\"title_discrepancy-identification-types-of-discrepancies\">Discrepancy identification – types of discrepancies</h1>\n \n \n <div class=\"body conbody\"><p class=\"shortdesc\">The Telecom Discrepancy Identification and Reconciliation capability identifies and classifies mismatches between the network state (as discovered through TSOM Discovery or Service Graph Connectors) and the inventory data\n stored in the CMDB or TNI.</p>\n <p class=\"p\">Discrepancy identification is powered by the CMDB Compliance Certification Audit, which:</p>\n <ul class=\"ul\" id=\"discrepancy-identification-types-of-discrepancies__ul_yfr_nww_tfc\">\n <li class=\"li\">Runs on CI and relationship data.</li>\n <li class=\"li\">Compares discovered and inventoried records.</li>\n <li class=\"li\">Generates Follow-on tasks when mismatches are detected.</li>\n </ul>\n <section class=\"section\" id=\"discrepancy-identification-types-of-discrepancies__section_xdx_4ww_tfc\"><h2 id=\"d1040e57\" class=\"title sectiontitle\">Discrepancy types</h2>\n \n <div class=\"p\">The audit process identifies discrepancies by comparing discovered network data with the existing inventory in the CMDB/TNI. Discrepancies fall into two main categories:<dl class=\"dl\">\n \n <dt class=\"dt dlterm\">Missing in network - entities existing in inventory but missing in network</dt>\n <dd class=\"dd\">Definition: A CI is detected by Discovery but is either missing from the CMDB/TNI or incorrectly represented. For example, Discovery detects Card05 installed in Slot04, but the CMDB still lists Card04, or worse, shows both\n Card04 and Card05 in the same slot—violating cardinality or model constraints.<div class=\"p\">Impact:<ul class=\"ul\" id=\"discrepancy-identification-types-of-discrepancies__ul_g5h_d5c_5fc\">\n <li class=\"li\">A discrepancy task is generated to highlight the data conflict.</li>\n <li class=\"li\">Optional remediation subflows may be triggered to reconcile the data by retiring outdated records or updating slot assignments.</li>\n </ul></div></dd>\n \n \n <dt class=\"dt dlterm\">Mismatched configuration items (CIs) - entities that exist in inventory and network but differ in attribute values and hierarchical relationships</dt>\n <dd class=\"dd\">Definition: The CI exists in both Discovery and CMDB/TNI, but discrepancies exist in relationships, hierarchy, or attribute values. The following are the sub types:<ul class=\"ul\" id=\"discrepancy-identification-types-of-discrepancies__ul_i5h_d5c_5fc\">\n <li class=\"li\">Hierarchy Mismatches - Occur when the structural relationships between CIs (e.g., parent-child associations) are inconsistent. The following are the examples:<ul class=\"ul\" id=\"discrepancy-identification-types-of-discrepancies__ul_j5h_d5c_5fc\">\n <li class=\"li\">A chassis contains more child cards than allowed by the model definition.</li>\n <li class=\"li\">A card is incorrectly associated with a slot in the CMDB that does not align with Discovery data. The validation sources are:<ul class=\"ul\" id=\"discrepancy-identification-types-of-discrepancies__ul_b43_djy_yfc\">\n <li class=\"li\"><code class=\"ph codeph\">cmdb_rel_ci</code> records for <code class=\"ph codeph\">Contains::Contained by</code> relationships.</li>\n <li class=\"li\"><code class=\"ph codeph\">sn_ni_core_network_model_relationship</code> table for enforcing model-specific constraints.</li>\n </ul></li>\n </ul></li>\n <li class=\"li\">Attribute Value Mismatches - Involve discrepancies in CI field-level properties. The common issues are:<ul class=\"ul\" id=\"discrepancy-identification-types-of-discrepancies__ul_k5h_d5c_5fc\">\n <li class=\"li\">Outdated or incorrect Discovery Dates.</li>\n <li class=\"li\">Inaccurate Model Configurations.</li>\n <li class=\"li\">Invalid Slot Assignments that breach model rules.</li>\n </ul><div class=\"p\">The impact is the affected records are marked as failed in audit reports. Follow-On Tasks may invoke context-specific remediation subflows to realign inventory data with the actual network state.<div class=\"note note note_note\"><span class=\"note__title\">Note:</span> For more\n information, see <a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/task/configure-attribute-value-discrepancy-in-cmdb-360.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/configure-attribute-value-discrepancy-in-cmdb-360.html\" class=\"xref\" title=\"Configure attribute comparison settings in CMDB 360 to detect data inconsistencies across multiple discovery sources.\">Configure attribute value discrepancy in CMDB 360</a>.</div></div></li>\n </ul></dd>\n \n </dl></div>\n </section>\n </div>\n <nav role=\"navigation\"></nav><nav role=\"navigation\" class=\"tasksNavigation\"></nav><nav role=\"navigation\" class=\"related-links\"><div class=\"col-md-4\"><dt>Related tasks</dt><dd><ul><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/task/configure-telecom-reconciliation.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/configure-telecom-reconciliation.html\" class=\"link\" title=\"Activate the Telecom Discrepancy Identification and Reconciliation feature (part of the Telecom Visibility plugin) to ensure consistency between telecom network resources discovered in the live network and the data represented in the CMDB or Telecom Network Inventory (TNI). This feature helps detect and remediate mismatches automatically, supporting service accuracy and data integrity across your telecom environment.\">Activate Telecom Discrepancy Identification and Reconciliation</a></li><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/task/run-audits.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/run-audits.html\" class=\"link\" title=\"The Telecom Discrepancy Audit validates the integrity of configuration items (CIs) and relationships across your telecom inventory using the CMDB Compliance framework.\">Run Telecom Discrepancy audit</a></li></ul></dd></div></nav>\n</article></main></body></article>",
"topic_language": "enus",
"views": 0,
"your_rating": null
} | # Discrepancy identification – types of discrepancies
The Telecom Discrepancy Identification and Reconciliation capability identifies and classifies mismatches between the network state (as discovered through TSOM Discovery or Service Graph Connectors) and the inventory data
stored in the CMDB or TNI.
Discrepancy identification is powered by the CMDB Compliance Certification Audit, which:
* Runs on CI and relationship data.
* Compares discovered and inventoried records.
* Generates Follow-on tasks when mismatches are detected.
## Discrepancy types
The audit process identifies discrepancies by comparing discovered network data with the existing inventory in the CMDB/TNI. Discrepancies fall into two main categories:
#### Missing in network - entities existing in inventory but missing in network
Definition: A CI is detected by Discovery but is either missing from the CMDB/TNI or incorrectly represented. For example, Discovery detects Card05 installed in Slot04, but the CMDB still lists Card04, or worse, shows both
Card04 and Card05 in the same slot—violating cardinality or model constraints.Impact:
* A discrepancy task is generated to highlight the data conflict.
* Optional remediation subflows may be triggered to reconcile the data by retiring outdated records or updating slot assignments.
#### Mismatched configuration items (CIs) - entities that exist in inventory and network but differ in attribute values and hierarchical relationships
Definition: The CI exists in both Discovery and CMDB/TNI, but discrepancies exist in relationships, hierarchy, or attribute values. The following are the sub types:
* Hierarchy Mismatches - Occur when the structural relationships between CIs (e.g., parent-child associations) are inconsistent. The following are the examples:
+ A chassis contains more child cards than allowed by the model definition.
+ A card is incorrectly associated with a slot in the CMDB that does not align with Discovery data. The validation sources are:
- `cmdb_rel_ci` records for `Contains::Contained by` relationships.
- `sn_ni_core_network_model_relationship` table for enforcing model-specific constraints.
* Attribute Value Mismatches - Involve discrepancies in CI field-level properties. The common issues are:
+ Outdated or incorrect Discovery Dates.
+ Inaccurate Model Configurations.
+ Invalid Slot Assignments that breach model rules.The impact is the affected records are marked as failed in audit reports. Follow-On Tasks may invoke context-specific remediation subflows to realign inventory data with the actual network state.Note: For more
information, see Configure attribute value discrepancy in CMDB 360.
| ---
title: "Discrepancy identification \u2013 types of discrepancies"
description: The Telecom Discrepancy Identification and Reconciliation capability
identifies and classifies mismatches between the network state (as discovered through
TSOM Discovery or Service Graph Connectors) and the inventory data stored in the
CMDB or TNI.
keywords: []
breadcrumbs:
- Telecommunications Service Operations Management
- Exploring Telecommunications Service Operations Management
- Telecom Visibility
- Telecom Discrepancy Identification and Reconciliation
---
# Discrepancy identification – types of discrepancies
The Telecom Discrepancy Identification and Reconciliation capability identifies and classifies mismatches between the network state (as discovered through TSOM Discovery or Service Graph Connectors) and the inventory data
stored in the CMDB or TNI.
Discrepancy identification is powered by the CMDB Compliance Certification Audit, which:
* Runs on CI and relationship data.
* Compares discovered and inventoried records.
* Generates Follow-on tasks when mismatches are detected.
## Discrepancy types
The audit process identifies discrepancies by comparing discovered network data with the existing inventory in the CMDB/TNI. Discrepancies fall into two main categories:
#### Missing in network - entities existing in inventory but missing in network
Definition: A CI is detected by Discovery but is either missing from the CMDB/TNI or incorrectly represented. For example, Discovery detects Card05 installed in Slot04, but the CMDB still lists Card04, or worse, shows both
Card04 and Card05 in the same slot—violating cardinality or model constraints.Impact:
* A discrepancy task is generated to highlight the data conflict.
* Optional remediation subflows may be triggered to reconcile the data by retiring outdated records or updating slot assignments.
#### Mismatched configuration items (CIs) - entities that exist in inventory and network but differ in attribute values and hierarchical relationships
Definition: The CI exists in both Discovery and CMDB/TNI, but discrepancies exist in relationships, hierarchy, or attribute values. The following are the sub types:
* Hierarchy Mismatches - Occur when the structural relationships between CIs (e.g., parent-child associations) are inconsistent. The following are the examples:
+ A chassis contains more child cards than allowed by the model definition.
+ A card is incorrectly associated with a slot in the CMDB that does not align with Discovery data. The validation sources are:
- `cmdb_rel_ci` records for `Contains::Contained by` relationships.
- `sn_ni_core_network_model_relationship` table for enforcing model-specific constraints.
* Attribute Value Mismatches - Involve discrepancies in CI field-level properties. The common issues are:
+ Outdated or incorrect Discovery Dates.
+ Inaccurate Model Configurations.
+ Invalid Slot Assignments that breach model rules.The impact is the affected records are marked as failed in audit reports. Follow-On Tasks may invoke context-specific remediation subflows to realign inventory data with the actual network state.Note: For more
information, see Configure attribute value discrepancy in CMDB 360.
|
https://www.servicenow.com/docs/en-US/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/exploring-telecom-discovery.html | https://servicenow-be-prod.servicenow.com/api/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/exploring-telecom-discovery.html | 2025-08-02 | daily | 0.5 | 268.xml | en-US | zurich-telecom-service-ops | product/tmt-telecom-service-operations-mgt/concept/exploring-telecom-discovery.html | zurich | Telecom Discovery | ServiceNow AI Platform Telecom Discovery helps you gain comprehensive visibility into your telecom network infrastructure by extending the capabilities of ITOM Visibility to support telecom-specific use cases. | [] | [
"Telecommunications Service Operations Management",
"Exploring Telecommunications Service Operations Management",
"Telecom Visibility"
] | <article class="hascomments" data-page="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/exploring-telecom-discovery.html" id="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/exploring-telecom-discovery.html"><body id="exploring-telecom-discovery"><main role="main"><article role="article" class="dita" id="exploring-telecom-discovery" aria-labelledby="title_exploring-telecom-discovery">
<h1 class="title topictitle1" id="title_exploring-telecom-discovery">Telecom Discovery</h1>
<div class="body conbody"><p class="shortdesc"><span class="ph">ServiceNow AI Platform</span> Telecom Discovery helps you gain comprehensive visibility into your telecom network infrastructure by extending the capabilities of ITOM Visibility to support telecom-specific use cases. </p>
<p class="p">Built for communication service providers (CSPs), this solution enables the discovery and mapping of network elements across multi-vendor environments using standardized protocols and integration with network management systems.</p>
<div class="p">By combining Telecom Discovery plugins with the power of Service Graph Connectors and Discovery Patterns, you can automatically populate and maintain accurate records of your telecom resources in the Configuration Management Database
(CMDB), providing a unified view of both IT and network infrastructure.<div class="note note note_note"><span class="note__title">Note:</span> Telecom Discovery is part of the TSOM Visibility subscription and aligns with the TM Forum Autonomous Network Operations (ANO) framework.</div></div>
<p class="p">With Telecom Discovery, you can:</p>
<ul class="ul" id="exploring-telecom-discovery__ul_r1x_pjm_5fc">
<li class="li">Discover physical and logical telecom network resources across domains and vendors.</li>
<li class="li">Integrate with Element Management Systems (EMS), Network Management Systems (NMS), and SDN Controllers.</li>
<li class="li">Automatically populate and update CMDB/TNI records based on real-time network data.</li>
<li class="li">Discover standalone xNFs using SNMP and Command-Line Interface (CLI).</li>
<li class="li">Enrich CMDB data using Service Graph Connectors and specialized discovery patterns.</li>
<li class="li">Identify discrepancies between discovered network data and inventory records.</li>
<li class="li">Support automation use cases through consistent and accurate infrastructure visibility.</li>
</ul>
<section class="section" id="exploring-telecom-discovery__section_s4d_dny_5fc"><h2 id="d11440e80" class="title sectiontitle">Telecom Discovery architecture</h2>
<p class="p"><img src="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/../images/exploring-telecom-discovery.png?_LANG=enus" class="image" id="exploring-telecom-discovery__image_m23_yn3_b2c" alt="telecom network."/></p>
</section>
<section class="section" id="exploring-telecom-discovery__section_nhq_rkm_5fc"><h2 id="d11440e94" class="title sectiontitle">Integration with ITOM Visibility</h2>
<p class="p">Telecom Discovery is designed to complement existing ITOM Visibility features. You can:</p>
<ul class="ul" id="exploring-telecom-discovery__ul_ykr_skm_5fc">
<li class="li">Leverage Horizontal Discovery and ITOM capabilities alongside TSOM plugins.</li>
<li class="li">Maintain consistent discovery practices for IT and telecom resources.</li>
<li class="li">Use the same CMDB data model to manage cross-domain service visibility.</li>
</ul>
<p class="p">This integration confirms unified asset management, faster issue resolution, and streamlined operations across both IT and network domains.</p>
</section>
<section class="section" id="exploring-telecom-discovery__section_xnn_tkm_5fc"><h2 id="d11440e118" class="title sectiontitle">Customization with low-code/no-code tools</h2>
<p class="p">Provides intuitive design tools to extend discovery logic without writing code. You can:</p>
<ul class="ul" id="exploring-telecom-discovery__ul_gxs_5km_5fc">
<li class="li">Build or modify custom Service Graph Connectors.</li>
<li class="li">Extend Telecommunications Discovery Patterns to match vendor-specific requirements.</li>
<li class="li">Accelerate onboarding of new device types and network domains.</li>
</ul>
<p class="p">This approach enables CSPs to stay agile and reduce time to value when expanding their discovery footprint.</p>
</section>
<section class="section" id="exploring-telecom-discovery__section_bxv_vjg_zdc"><h2 id="d11440e142" class="title sectiontitle">Key components</h2>
<div class="p">
<ul class="ul" id="exploring-telecom-discovery__ul_qn5_2lm_5fc">
<li class="li">Telecommunication Discovery Patterns(sn_tsom_patterns): Provides patterns for SNMP-based discovery of standalone routers, switches, and xNFs. Includes Cisco and Juniper-specific discovery logic.</li>
<li class="li">Service Graph Connector for Nokia Altiplano(sn_sgc_altiplano_connector): Enables data collection from the Nokia Altiplano Access SDN Controller via REST APIs.</li>
<li class="li">Telecom Core(sn_tsom_core): Delivers foundational capabilities such as discrepancy identification, remediation logic, and shared telecom discovery features.</li>
</ul>
</div>
</section>
</div>
</article></main></body></article> | {
"attachments": {
"all_attachments": null,
"topic_attachments": []
},
"available_languages": [
"enus"
],
"breadcrumbs": [
{
"title": "Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html"
},
{
"title": "Exploring Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/exploring-tsom.html"
},
{
"title": "Telecom Visibility",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/tsom-visibility.html"
}
],
"breadcrumbs_html": "<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops\">Zurich Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html\">Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/exploring-tsom.html\">Exploring Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/tsom-visibility.html\">Telecom Visibility</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<span class=\"active\">Telecom Discovery</span>",
"bundle_id": "zurich-telecom-service-ops",
"bundle_key": 2733,
"bundle_landing_page": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html",
"bundle_subtitle": null,
"bundle_title": "Zurich Telecommunications Service Operations Management",
"canonical_link": null,
"dates": {
"Added on": "2025-08-02T00:48:08.794016Z",
"Created on": "2024-12-06T00:00:00Z",
"Initial upload": "2025-07-30T22:24:33.519043Z",
"Updated on": "2025-07-31T00:00:00Z"
},
"dislike_url": "https://servicenow-be-prod.servicenow.com/dislike/55686933",
"dislikes": 0,
"es_archived_content": false,
"is_in_fav": false,
"is_liked": null,
"is_watched": false,
"keywords": [
" zurich zurich"
],
"labels": [
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "zurich",
"navtitle": "Zurich",
"outputclasses": [],
"subjectHeadId": "versions",
"subjectheadNavtitle": "Versions",
"visibility": "show-facet"
},
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "tsom",
"navtitle": "Telecommunications Service Operations Management",
"outputclasses": [],
"subjectHeadId": "products",
"subjectheadNavtitle": "Products",
"visibility": "show-facet"
}
],
"labels_text": "Versions > Zurich; Products > CRM and Industry Products > Telecommunications Media and Technology Assurance > Telecommunications Service Operations Management",
"like_url": "https://servicenow-be-prod.servicenow.com/like/55686933",
"likes": 0,
"metadata": {
"AI Search": null,
"AI Search Assist": null,
"Application Insights": null,
"Capabilities": null,
"Code Signing": null,
"Contextual Search": null,
"DC.contributor": null,
"DC.coverage": null,
"DC.creator": "ServiceNow",
"DC.date.created": "2024-12-06T10:32:00+05:30",
"DC.date.modified": "2025-07-31",
"DC.format": "HTML5",
"DC.identifier": "exploring-telecom-discovery",
"DC.language": null,
"DC.relation": null,
"DC.rights.owner": "(C) Copyright 2025",
"DC.subject": null,
"DC.type": "concept",
"Data Discovery": null,
"Data Policy": null,
"Data Privacy": null,
"Discovery": null,
"External Content for AI Search": null,
"Field Administration": null,
"Field Normalization": null,
"Key Management Framework": null,
"Localization Framework": null,
"Now Platform": null,
"PlatSec": null,
"Platform": null,
"Platform Administration": null,
"Platform Performance": null,
"Platform Privacy": null,
"Proactive Triggers": null,
"Process Optimization": null,
"RN doc editing record number": null,
"Search Administration": null,
"Secrets Management": null,
"ServiceNow AI Platform": null,
"State Model": null,
"Subscription Management": null,
"Task Communications Management": null,
"Timeline Visualizations": null,
"User Administration": null,
"User Experience Analytics": null,
"Zing": null,
"ai-now-assist": null,
"app-name": null,
"app_route": null,
"azureapimanagemen": null,
"change-completed": null,
"change-item": null,
"change-request-id": null,
"change-request-reference": null,
"com.glide.embedded_help.category": null,
"component": null,
"copyright": "(C) Copyright 2025",
"crossroads": null,
"data": null,
"description": "ServiceNow AI Platform Telecom Discovery helps you gain comprehensive visibility into your telecom network infrastructure by extending the capabilities of ITOM Visibility to support telecom-specific use cases.",
"dominant_bundle": null,
"erp-canvas-video": null,
"fsm-mobile": null,
"fsm-route": null,
"fsm-sched-opt": null,
"fsm-wrk-order": null,
"genai-round-7": null,
"generator": "DITA-OT",
"glossPartOfSpeech": null,
"glossStatus": null,
"guided setup": null,
"guided tours": null,
"keywords": null,
"min-toc": null,
"mini": null,
"mini-to truec": null,
"mini-toc": "yes",
"mini_toc": null,
"minitoc": null,
"modification": null,
"now-assist-app-gen-video": null,
"order": null,
"page-type": null,
"page-type ": null,
"prodname": null,
"product": null,
"product_name": null,
"release": null,
"resourceID": null,
"roles": null,
"route_page": null,
"route_params_listId": null,
"route_params_table": null,
"route_params_type": null,
"route_type": null,
"setconfigurationproperties": null,
"topic": null,
"translation-type": "source",
"version": null,
"workflow": "Customer and Industry",
"workplace-srvc-delvry-ditamap": null
},
"page_id": "product/tmt-telecom-service-operations-mgt/concept/exploring-telecom-discovery.html",
"page_key": 55686933,
"preprocessed_PDF": "https://downloads.docs.servicenow.com/pdf/enus/servicenow-zurich-telecom-service-ops-enus.pdf",
"rating": null,
"read_time_data": {
"char_count": 2990,
"img_count": 1,
"read_time": 2,
"video_links": [
""
],
"word_count": 379
},
"related_links": [],
"search_title": null,
"title": "Telecom Discovery",
"topic_cluster": {
"clustered_by": {
"enabled": true,
"primary_key": "versions",
"primary_sort": "top-down",
"type": "subjecthead"
},
"clustered_labels": [
"versions"
],
"clustered_topics": [
{
"bundle_id": "yokohama-telecom-service-ops",
"clustering_title": "Yokohama",
"es_archived_content": false,
"page_id": "product/tmt-telecom-service-operations-mgt/concept/exploring-telecom-discovery.html"
}
],
"clustering_title": "Zurich"
},
"topic_html": "<article class=\"hascomments\" data-page=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/exploring-telecom-discovery.html\" id=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/exploring-telecom-discovery.html\"><body id=\"exploring-telecom-discovery\"><main role=\"main\"><article role=\"article\" class=\"dita\" id=\"exploring-telecom-discovery\" aria-labelledby=\"title_exploring-telecom-discovery\">\n <h1 class=\"title topictitle1\" id=\"title_exploring-telecom-discovery\">Telecom Discovery</h1>\n \n \n <div class=\"body conbody\"><p class=\"shortdesc\"><span class=\"ph\">ServiceNow AI Platform</span> Telecom Discovery helps you gain comprehensive visibility into your telecom network infrastructure by extending the capabilities of ITOM Visibility to support telecom-specific use cases. </p>\n <p class=\"p\">Built for communication service providers (CSPs), this solution enables the discovery and mapping of network elements across multi-vendor environments using standardized protocols and integration with network management systems.</p>\n <div class=\"p\">By combining Telecom Discovery plugins with the power of Service Graph Connectors and Discovery Patterns, you can automatically populate and maintain accurate records of your telecom resources in the Configuration Management Database\n (CMDB), providing a unified view of both IT and network infrastructure.<div class=\"note note note_note\"><span class=\"note__title\">Note:</span> Telecom Discovery is part of the TSOM Visibility subscription and aligns with the TM Forum Autonomous Network Operations (ANO) framework.</div></div>\n <p class=\"p\">With Telecom Discovery, you can:</p>\n <ul class=\"ul\" id=\"exploring-telecom-discovery__ul_r1x_pjm_5fc\">\n <li class=\"li\">Discover physical and logical telecom network resources across domains and vendors.</li>\n <li class=\"li\">Integrate with Element Management Systems (EMS), Network Management Systems (NMS), and SDN Controllers.</li>\n <li class=\"li\">Automatically populate and update CMDB/TNI records based on real-time network data.</li>\n <li class=\"li\">Discover standalone xNFs using SNMP and Command-Line Interface (CLI).</li>\n <li class=\"li\">Enrich CMDB data using Service Graph Connectors and specialized discovery patterns.</li>\n <li class=\"li\">Identify discrepancies between discovered network data and inventory records.</li>\n <li class=\"li\">Support automation use cases through consistent and accurate infrastructure visibility.</li>\n </ul>\n <section class=\"section\" id=\"exploring-telecom-discovery__section_s4d_dny_5fc\"><h2 id=\"d11440e80\" class=\"title sectiontitle\">Telecom Discovery architecture</h2>\n \n <p class=\"p\"><img src=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/../images/exploring-telecom-discovery.png?_LANG=enus\" class=\"image\" id=\"exploring-telecom-discovery__image_m23_yn3_b2c\" alt=\"telecom network.\"/></p>\n </section>\n <section class=\"section\" id=\"exploring-telecom-discovery__section_nhq_rkm_5fc\"><h2 id=\"d11440e94\" class=\"title sectiontitle\">Integration with ITOM Visibility</h2>\n \n <p class=\"p\">Telecom Discovery is designed to complement existing ITOM Visibility features. You can:</p>\n <ul class=\"ul\" id=\"exploring-telecom-discovery__ul_ykr_skm_5fc\">\n <li class=\"li\">Leverage Horizontal Discovery and ITOM capabilities alongside TSOM plugins.</li>\n <li class=\"li\">Maintain consistent discovery practices for IT and telecom resources.</li>\n <li class=\"li\">Use the same CMDB data model to manage cross-domain service visibility.</li>\n </ul>\n <p class=\"p\">This integration confirms unified asset management, faster issue resolution, and streamlined operations across both IT and network domains.</p>\n </section>\n <section class=\"section\" id=\"exploring-telecom-discovery__section_xnn_tkm_5fc\"><h2 id=\"d11440e118\" class=\"title sectiontitle\">Customization with low-code/no-code tools</h2>\n \n <p class=\"p\">Provides intuitive design tools to extend discovery logic without writing code. You can:</p>\n <ul class=\"ul\" id=\"exploring-telecom-discovery__ul_gxs_5km_5fc\">\n <li class=\"li\">Build or modify custom Service Graph Connectors.</li>\n <li class=\"li\">Extend Telecommunications Discovery Patterns to match vendor-specific requirements.</li>\n <li class=\"li\">Accelerate onboarding of new device types and network domains.</li>\n </ul>\n <p class=\"p\">This approach enables CSPs to stay agile and reduce time to value when expanding their discovery footprint.</p>\n </section>\n <section class=\"section\" id=\"exploring-telecom-discovery__section_bxv_vjg_zdc\"><h2 id=\"d11440e142\" class=\"title sectiontitle\">Key components</h2>\n \n <div class=\"p\">\n <ul class=\"ul\" id=\"exploring-telecom-discovery__ul_qn5_2lm_5fc\">\n <li class=\"li\">Telecommunication Discovery Patterns(sn_tsom_patterns): Provides patterns for SNMP-based discovery of standalone routers, switches, and xNFs. Includes Cisco and Juniper-specific discovery logic.</li>\n <li class=\"li\">Service Graph Connector for Nokia Altiplano(sn_sgc_altiplano_connector): Enables data collection from the Nokia Altiplano Access SDN Controller via REST APIs.</li>\n <li class=\"li\">Telecom Core(sn_tsom_core): Delivers foundational capabilities such as discrepancy identification, remediation logic, and shared telecom discovery features.</li>\n </ul>\n </div>\n </section>\n </div>\n</article></main></body></article>",
"topic_language": "enus",
"views": 0,
"your_rating": null
} | # Telecom Discovery
ServiceNow AI Platform Telecom Discovery helps you gain comprehensive visibility into your telecom network infrastructure by extending the capabilities of ITOM Visibility to support telecom-specific use cases.
Built for communication service providers (CSPs), this solution enables the discovery and mapping of network elements across multi-vendor environments using standardized protocols and integration with network management systems.
By combining Telecom Discovery plugins with the power of Service Graph Connectors and Discovery Patterns, you can automatically populate and maintain accurate records of your telecom resources in the Configuration Management Database
(CMDB), providing a unified view of both IT and network infrastructure.Note: Telecom Discovery is part of the TSOM Visibility subscription and aligns with the TM Forum Autonomous Network Operations (ANO) framework.
With Telecom Discovery, you can:
* Discover physical and logical telecom network resources across domains and vendors.
* Integrate with Element Management Systems (EMS), Network Management Systems (NMS), and SDN Controllers.
* Automatically populate and update CMDB/TNI records based on real-time network data.
* Discover standalone xNFs using SNMP and Command-Line Interface (CLI).
* Enrich CMDB data using Service Graph Connectors and specialized discovery patterns.
* Identify discrepancies between discovered network data and inventory records.
* Support automation use cases through consistent and accurate infrastructure visibility.
## Telecom Discovery architecture
## Integration with ITOM Visibility
Telecom Discovery is designed to complement existing ITOM Visibility features. You can:
* Leverage Horizontal Discovery and ITOM capabilities alongside TSOM plugins.
* Maintain consistent discovery practices for IT and telecom resources.
* Use the same CMDB data model to manage cross-domain service visibility.
This integration confirms unified asset management, faster issue resolution, and streamlined operations across both IT and network domains.
## Customization with low-code/no-code tools
Provides intuitive design tools to extend discovery logic without writing code. You can:
* Build or modify custom Service Graph Connectors.
* Extend Telecommunications Discovery Patterns to match vendor-specific requirements.
* Accelerate onboarding of new device types and network domains.
This approach enables CSPs to stay agile and reduce time to value when expanding their discovery footprint.
## Key components
* Telecommunication Discovery Patterns(sn\_tsom\_patterns): Provides patterns for SNMP-based discovery of standalone routers, switches, and xNFs. Includes Cisco and Juniper-specific discovery logic.
* Service Graph Connector for Nokia Altiplano(sn\_sgc\_altiplano\_connector): Enables data collection from the Nokia Altiplano Access SDN Controller via REST APIs.
* Telecom Core(sn\_tsom\_core): Delivers foundational capabilities such as discrepancy identification, remediation logic, and shared telecom discovery features.
| ---
title: Telecom Discovery
description: ServiceNow AI Platform Telecom Discovery helps you gain comprehensive
visibility into your telecom network infrastructure by extending the capabilities
of ITOM Visibility to support telecom-specific use cases.
keywords: []
breadcrumbs:
- Telecommunications Service Operations Management
- Exploring Telecommunications Service Operations Management
- Telecom Visibility
---
# Telecom Discovery
ServiceNow AI Platform Telecom Discovery helps you gain comprehensive visibility into your telecom network infrastructure by extending the capabilities of ITOM Visibility to support telecom-specific use cases.
Built for communication service providers (CSPs), this solution enables the discovery and mapping of network elements across multi-vendor environments using standardized protocols and integration with network management systems.
By combining Telecom Discovery plugins with the power of Service Graph Connectors and Discovery Patterns, you can automatically populate and maintain accurate records of your telecom resources in the Configuration Management Database
(CMDB), providing a unified view of both IT and network infrastructure.Note: Telecom Discovery is part of the TSOM Visibility subscription and aligns with the TM Forum Autonomous Network Operations (ANO) framework.
With Telecom Discovery, you can:
* Discover physical and logical telecom network resources across domains and vendors.
* Integrate with Element Management Systems (EMS), Network Management Systems (NMS), and SDN Controllers.
* Automatically populate and update CMDB/TNI records based on real-time network data.
* Discover standalone xNFs using SNMP and Command-Line Interface (CLI).
* Enrich CMDB data using Service Graph Connectors and specialized discovery patterns.
* Identify discrepancies between discovered network data and inventory records.
* Support automation use cases through consistent and accurate infrastructure visibility.
## Telecom Discovery architecture
## Integration with ITOM Visibility
Telecom Discovery is designed to complement existing ITOM Visibility features. You can:
* Leverage Horizontal Discovery and ITOM capabilities alongside TSOM plugins.
* Maintain consistent discovery practices for IT and telecom resources.
* Use the same CMDB data model to manage cross-domain service visibility.
This integration confirms unified asset management, faster issue resolution, and streamlined operations across both IT and network domains.
## Customization with low-code/no-code tools
Provides intuitive design tools to extend discovery logic without writing code. You can:
* Build or modify custom Service Graph Connectors.
* Extend Telecommunications Discovery Patterns to match vendor-specific requirements.
* Accelerate onboarding of new device types and network domains.
This approach enables CSPs to stay agile and reduce time to value when expanding their discovery footprint.
## Key components
* Telecommunication Discovery Patterns(sn\_tsom\_patterns): Provides patterns for SNMP-based discovery of standalone routers, switches, and xNFs. Includes Cisco and Juniper-specific discovery logic.
* Service Graph Connector for Nokia Altiplano(sn\_sgc\_altiplano\_connector): Enables data collection from the Nokia Altiplano Access SDN Controller via REST APIs.
* Telecom Core(sn\_tsom\_core): Delivers foundational capabilities such as discrepancy identification, remediation logic, and shared telecom discovery features.
|
https://www.servicenow.com/docs/en-US/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/exploring-telecom-reconciliation.html | https://servicenow-be-prod.servicenow.com/api/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/exploring-telecom-reconciliation.html | 2025-08-02 | daily | 0.5 | 268.xml | en-US | zurich-telecom-service-ops | product/tmt-telecom-service-operations-mgt/concept/exploring-telecom-reconciliation.html | zurich | Telecom Discrepancy Identification and Reconciliation | Use the Telecom Discrepancy Identification and Reconciliation capability to keep your CMDB or Telecommunications Network Inventory (TNI) in sync with your live telecom network. By continuously auditing and comparing discovered data with inventory records, this solution helps you detect, classify, | [] | [
"Telecommunications Service Operations Management",
"Exploring Telecommunications Service Operations Management",
"Telecom Visibility"
] | <article class="hascomments" data-page="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/exploring-telecom-reconciliation.html" id="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/exploring-telecom-reconciliation.html"><body id="exploring-telecom-reconciliation"><main role="main"><article role="article" class="dita" id="exploring-telecom-reconciliation" aria-labelledby="title_exploring-telecom-reconciliation">
<h1 class="title topictitle1" id="title_exploring-telecom-reconciliation">Telecom Discrepancy Identification and Reconciliation</h1>
<div class="body conbody"><p class="shortdesc">Use the Telecom Discrepancy Identification and Reconciliation capability to keep your CMDB or Telecommunications Network Inventory (TNI) in sync with your live telecom network. By continuously auditing and comparing discovered
data with inventory records, this solution helps you detect, classify, and automatically remediate inconsistencies before they impact service quality, assurance, or fulfillment processes.</p>
<p class="p">Telecom Discrepancy Identification and Reconciliation is a telecom-specific capability included with the TSOM Visibility plugin. It helps confirm the integrity of your network inventory by identifying mismatches between real-time
network data (from Discovery or external systems) and inventory records stored in the CMDB or TNI.</p>
<p class="p">This solution uses:</p>
<ul class="ul" id="exploring-telecom-reconciliation__ul_bmg_lmw_tfc">
<li class="li">CMDB Compliance Certification audits to detect anomalies.</li>
<li class="li">Follow-on tasks to log and track issues.</li>
<li class="li">Automated remediation subflows to resolve discrepancies.</li>
</ul>
<div class="note note note_note"><span class="note__title">Note:</span> Keeping inventory accurate enables automation, reduces service errors, and supports regulatory compliance. It is also a foundational component of TM Forum’s Autonomous Network Operations (ANO) framework.</div>
<section class="section" id="exploring-telecom-reconciliation__section_yg1_x2c_b2c"><h2 id="d12206e63" class="title sectiontitle">Telecom Discrepancy Identification & Reconciliation architecture</h2>
<p class="p"><img src="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/../images/telecom-discrepancy-identification-reconciliation.png?_LANG=enus" class="image" id="exploring-telecom-reconciliation__image_x2k_4nj_b2c" alt="Telecom discrepancy identification and reconciliation framework."/></p>
</section>
<section class="section" id="exploring-telecom-reconciliation__section_t5b_tmw_tfc"><h2 id="d12206e77" class="title sectiontitle">Key features</h2>
<div class="p">
<div class="table-wrap"><table count-columns="2" class="table" id="exploring-telecom-reconciliation__table_scd_5mw_tfc"><caption><span class="table--title-label">Table 1. </span><span class="title">Key features of Telecom Discrepancy Identification and Reconciliation</span></caption><colgroup><col/><col/></colgroup><thead class="thead">
<tr class="row">
<th class="entry" id="exploring-telecom-reconciliation__table_scd_5mw_tfc__entry__1">Feature</th>
<th class="entry" id="exploring-telecom-reconciliation__table_scd_5mw_tfc__entry__2">Description</th>
</tr>
</thead><tbody class="tbody">
<tr class="row">
<td class="entry" headers="exploring-telecom-reconciliation__table_scd_5mw_tfc__entry__1">Continuous audit checks</td>
<td class="entry" headers="exploring-telecom-reconciliation__table_scd_5mw_tfc__entry__2">Compares discovered network data with inventory records using Certification Audits.</td>
</tr>
<tr class="row">
<td class="entry" headers="exploring-telecom-reconciliation__table_scd_5mw_tfc__entry__1">Discrepancy detection</td>
<td class="entry" headers="exploring-telecom-reconciliation__table_scd_5mw_tfc__entry__2">Identifies CIs that are missing, misconfigured, or misaligned in terms of hierarchy or attribute values.</td>
</tr>
<tr class="row">
<td class="entry" headers="exploring-telecom-reconciliation__table_scd_5mw_tfc__entry__1">Follow-On task generation</td>
<td class="entry" headers="exploring-telecom-reconciliation__table_scd_5mw_tfc__entry__2">Automatically creates tasks for each discrepancy to enable tracking and remediation.</td>
</tr>
<tr class="row">
<td class="entry" headers="exploring-telecom-reconciliation__table_scd_5mw_tfc__entry__1">Automated remediation</td>
<td class="entry" headers="exploring-telecom-reconciliation__table_scd_5mw_tfc__entry__2">Uses Flow Designer subflows to resolve issues such as outdated CIs, invalid relationships, and missing discovery data.</td>
</tr>
</tbody></table></div>
</div>
</section>
<section class="section" id="exploring-telecom-reconciliation__id_yyy_qrj_yfc"><h2 id="d12206e150" class="title sectiontitle">How Telecom Discrepancy Identification & Reconciliation works</h2>
<p class="p">Once the discovery process is complete, the CMDB Compliance framework identifies mismatches between discovered data and inventory records using scheduled or on-demand compliance audits.</p>
<ul class="ul" id="exploring-telecom-reconciliation__ul_irz_qrj_yfc">
<li class="li">Compliance Audits: Compare discovered network data with CMDB inventory records to detect inconsistencies.</li>
<li class="li">Follow-On Tasks: Automatically generated for each failed audit. These tasks document and categorize the identified discrepancies.</li>
<li class="li">Remediation Subflows: Launched from Follow-On Tasks to resolve discrepancies by updating, decommissioning, or realigning Configuration Items (CIs).</li>
</ul>
<div class="note note note_note"><span class="note__title">Note:</span> For more information, see <a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/concept/discrepancy-identification-types-of-discrepancies.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/discrepancy-identification-types-of-discrepancies.html" class="xref" title="The Telecom Discrepancy Identification and Reconciliation capability identifies and classifies mismatches between the network state (as discovered through TSOM Discovery or Service Graph Connectors) and the inventory data stored in the CMDB or TNI.">Discrepancy identification – types of discrepancies</a>.</div>
</section>
<section class="section" id="exploring-telecom-reconciliation__section_qt1_nmc_b2c"><h2 id="d12206e181" class="title sectiontitle">CMDB Compliance and Telecom Discrepancy Identification & Reconciliation</h2>
<div class="p">CMDB Compliance is a toolset that enables administrators to certify CMDB data for accuracy and identify discrepancies detected during compliance audits. It can also automatically generate and assign Follow-on Tasks for failed audit
records, which serve as tasks to trigger an appropriate remediation subflow to correct discrepancies. CMDB Compliance Audits form the foundation of our Telecom Discrepancy Identification & Reconciliation.<ul class="ul" id="exploring-telecom-reconciliation__ul_g2q_5mc_b2c">
<li class="li">CMDB Compliance runs audits as a post-processing rule, identifying anomalies (discrepancies) in the CMDB.</li>
<li class="li">CMDB Compliance creates a Follow-On Task for each Audit Record in a failed state (the failed state is the result of an audit finding an anomaly or discrepancy in the CMDB). A remediation flow can be designed and triggered for each
Follow-On Task to address and resolve the discrepancy.</li>
</ul></div>
<p class="p">The logic for Telecom Discrepancy Identification & Reconciliation, as well as the example remediation subflows, are automatically with the TSOM Visibility plugin. For more information on the general CMDB Compliance toolset, see <a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/concept//csh" href="https://servicenow-be-prod.servicenow.com/csh?topicname=c_Compliance&version=zurich&pubname=zurich-servicenow-platform" class="xref">CMDB Compliance</a>.</p>
</section>
<section class="section" id="exploring-telecom-reconciliation__section_mpg_vvc_b2c"><h2 id="d12206e205" class="title sectiontitle">Discrepancy Identification Scenarios (using Compliance Audits)</h2>
<div class="p">Discrepancy identification in TSOM Visibility relies on using CMDB Compliance (Certification Audits) and has extended it by adding specific logic that uses model relationships and information to identify mismatches. To support
remediation, the system generates specific reconciliation task types for each issue found, such as:<ul class="ul" id="exploring-telecom-reconciliation__ul_zrg_jgl_wfc">
<li class="li">Slots occupied discrepancy</li>
<li class="li">Most recent discovery date not set</li>
<li class="li">Most recent discovery date not within configured threshold</li>
<li class="li">Model relationships not defined</li>
<li class="li">CI model not found</li>
<li class="li">Incorrect number of relationships</li>
<li class="li">Reference to Logical Interface not found</li>
</ul></div>
<div class="p">You can use the following audits to identify the discrepancies in the discovered physical and logical entities<ul class="ul" id="exploring-telecom-reconciliation__ul_hkf_h2b_yfc">
<li class="li">Telecom Discrepancy Audit</li>
<li class="li">Telecom Logical Connections Discrepancy Audit</li>
<li class="li">Telecom Network Topology Discrepancy Audit</li>
</ul><div class="note note note_note"><span class="note__title">Note:</span> For more information on the general compliance audits, see <a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/concept//csh" href="https://servicenow-be-prod.servicenow.com/csh?topicname=c_CertificationAudits&version=zurich&pubname=zurich-servicenow-platform" class="xref">Certification audits</a>.</div></div>
</section>
<section class="section" id="exploring-telecom-reconciliation__section_tz1_m1d_b2c"><h2 id="d12206e258" class="title sectiontitle">Automation and UI Integration</h2>
<div class="p">
<ul class="ul" id="exploring-telecom-reconciliation__ul_cxp_fww_tfc">
<li class="li">Every failed audit automatically creates a Follow-On Task.</li>
<li class="li">Tasks can trigger prebuilt or custom subflows using Flow Designer.</li>
<li class="li">Manual remediation can be initiated using a "Remediate" UI action button in the task form.</li>
<li class="li">Remediation steps are recorded in work notes for visibility and auditing.</li>
</ul>
<div class="note note note_note"><span class="note__title">Note:</span> For more information on how to build a subflow, see <a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/concept//csh" href="https://servicenow-be-prod.servicenow.com/csh?topicname=subflows&version=zurich&pubname=zurich-build-workflows" class="xref">Building subflows</a>.</div>
</div>
</section>
<section class="section" id="exploring-telecom-reconciliation__section_mhf_5wc_b2c"><h2 id="d12206e289" class="title sectiontitle">Follow-On Task types created for failed Audit Result Records</h2>
<div class="p">The following discrepancy types (Audit Results) can be found for Parent CI and child CIs for each relationship record in the CI Relationship table (cmdb_rel_ci) that matches the conditions, and the following Follow-On Tasks can be
created for each of the failed Audit Results:<ol class="ol" id="exploring-telecom-reconciliation__ol_c5l_rzc_b2c">
<li class="li">The most recent discovery date not set- generated in case the Most recent discovery date field in CI is missing.</li>
<li class="li">The most recent discovery date not within configured threshold- generated in case the difference in the Most recent discovery date field value between a Parent CI and child CI is more than 2.5 days. For example, By default, it is
set to 2.5 days in the sn_tsom_core.discovered_date.diff.threshold.in.days system property and can be changed.</li>
<li class="li">CI model not found–(the ‘Model ID’ field isn’t set or data is invalid). Generated in case a corresponding CI model isn’t found. If a CI model isn’t found, the next validations (4-6) are irrelevant because they rely on CI models. In
case a CI model is found, the audit will continue to the next validations (4-6).</li>
<li class="li">Slots occupied discrepancy-Generated in case a card occupies an incorrect number of Slots.</li>
<li class="li">Model relationships not defined-relevant only if TNI is installed. Generated if the audit is unable to find a relationship between Parent and child CI models in the Network Model Relationships table.</li>
<li class="li">Incorrect number of relationships - relevant only if TNI is installed. Generated if the audit finds that the number of discovered child CI records exceeds the maximum number of its corresponding Parent CI record in the model
relationship Count field in the Network Model Relationship table.</li>
<li class="li">Incorrect number of relationships - generated during the Logical Connection Discrepancy Audit when a logical interface is associated with more than one logical connection, violating the expected one-to-one mapping.</li>
<li class="li">Incorrect number of relationships - generated during the Network Topology Discrepancy Audit when a network topology record does not meet the required relationship criteria. Specifically:<ul class="ul" id="exploring-telecom-reconciliation__ul_szb_bjb_yfc">
<li class="li">The record must have at least one "Contains:Contained By" relationship with an equipment CI.</li>
<li class="li">The record must also have at least one "Members:Member Of" relationship with a logical connection CI.</li>
</ul></li>
<li class="li">Reference to Logical Interface not found - generated during the Logical Connection Discrepancy Audit when a logical connection is missing one of the end points (Port A or Port z, or both).</li>
</ol></div>
</section>
<section class="section" id="exploring-telecom-reconciliation__section_j44_vlj_wfc"><h2 id="d12206e337" class="title sectiontitle">Telecom Reconciliation</h2>
<div class="p">Automate reconciliation of network inventory discrepancies and enhance operational efficiency. Telecom Reconciliation helps to:<ul class="ul" id="exploring-telecom-reconciliation__ul_ygg_5mj_wfc">
<li class="li">Identify and resolve discrepancies between live network inventory and CMDB inventory to ensure alignment and boost productivity</li>
<li class="li">Empower users with auto generated discrepancy reports detailing the type of discrepancy</li>
<li class="li">Provide users with recommended corrective actions and the flexibility and control to choose between manual or automated methods to resolve discrepancies </li>
<li class="li">Improve operations by automatically aligning the operational status of network resources with the same status in the inventory CMDB</li>
</ul></div>
</section>
</div>
<nav role="navigation"></nav><nav role="navigation" class="tasksNavigation"></nav><nav role="navigation" class="related-links"><div class="col-md-4"><dt>Related tasks</dt><dd><ul><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/task/configure-telecom-reconciliation.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/configure-telecom-reconciliation.html" class="link" title="Activate the Telecom Discrepancy Identification and Reconciliation feature (part of the Telecom Visibility plugin) to ensure consistency between telecom network resources discovered in the live network and the data represented in the CMDB or Telecom Network Inventory (TNI). This feature helps detect and remediate mismatches automatically, supporting service accuracy and data integrity across your telecom environment.">Activate Telecom Discrepancy Identification and Reconciliation</a></li><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/task/run-audits.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/run-audits.html" class="link" title="The Telecom Discrepancy Audit validates the integrity of configuration items (CIs) and relationships across your telecom inventory using the CMDB Compliance framework.">Run Telecom Discrepancy audit</a></li></ul></dd></div><div class="col-md-4"><dt>Related concepts</dt><dd><ul><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/concept/discrepancy-identification-types-of-discrepancies.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/discrepancy-identification-types-of-discrepancies.html" class="link" title="The Telecom Discrepancy Identification and Reconciliation capability identifies and classifies mismatches between the network state (as discovered through TSOM Discovery or Service Graph Connectors) and the inventory data stored in the CMDB or TNI.">Discrepancy identification – types of discrepancies</a></li><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/concept/system-properties-affecting-telecom-discrepancy-identification-reconciliation.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/system-properties-affecting-telecom-discrepancy-identification-reconciliation.html" class="link" title="The system properties are part of the TSOM Visibility plugin (sn_tsom_core) and control the Telecom Discrepancy Identification & Reconciliation log (TSOM CMDB Audit). The TSOM Visibility plugin serves as an enabler for the TSOM Visibility applications, containing logic that is shared across the Telecom Discovery and Telecom Discrepancy Identification & Reconciliation solution.">System components installed with Telecom Discrepancy Identification & Reconciliation</a></li></ul></dd></div></nav>
</article></main></body></article> | {
"attachments": {
"all_attachments": null,
"topic_attachments": []
},
"available_languages": [
"enus"
],
"breadcrumbs": [
{
"title": "Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html"
},
{
"title": "Exploring Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/exploring-tsom.html"
},
{
"title": "Telecom Visibility",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/tsom-visibility.html"
}
],
"breadcrumbs_html": "<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops\">Zurich Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html\">Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/exploring-tsom.html\">Exploring Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/tsom-visibility.html\">Telecom Visibility</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<span class=\"active\">Telecom Discrepancy Identification and Reconciliation</span>",
"bundle_id": "zurich-telecom-service-ops",
"bundle_key": 2733,
"bundle_landing_page": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html",
"bundle_subtitle": null,
"bundle_title": "Zurich Telecommunications Service Operations Management",
"canonical_link": null,
"dates": {
"Added on": "2025-08-02T00:48:08.794016Z",
"Created on": "2024-12-06T00:00:00Z",
"Initial upload": "2025-07-30T22:24:33.519043Z",
"Updated on": "2025-07-31T00:00:00Z"
},
"dislike_url": "https://servicenow-be-prod.servicenow.com/dislike/55686934",
"dislikes": 0,
"es_archived_content": false,
"is_in_fav": false,
"is_liked": null,
"is_watched": false,
"keywords": [
" zurich zurich"
],
"labels": [
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "zurich",
"navtitle": "Zurich",
"outputclasses": [],
"subjectHeadId": "versions",
"subjectheadNavtitle": "Versions",
"visibility": "show-facet"
},
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "tsom",
"navtitle": "Telecommunications Service Operations Management",
"outputclasses": [],
"subjectHeadId": "products",
"subjectheadNavtitle": "Products",
"visibility": "show-facet"
}
],
"labels_text": "Versions > Zurich; Products > CRM and Industry Products > Telecommunications Media and Technology Assurance > Telecommunications Service Operations Management",
"like_url": "https://servicenow-be-prod.servicenow.com/like/55686934",
"likes": 0,
"metadata": {
"AI Search": null,
"AI Search Assist": null,
"Application Insights": null,
"Capabilities": null,
"Code Signing": null,
"Contextual Search": null,
"DC.contributor": null,
"DC.coverage": null,
"DC.creator": "ServiceNow",
"DC.date.created": "2024-12-06T11:58:14+05:30",
"DC.date.modified": "2025-07-31",
"DC.format": "HTML5",
"DC.identifier": "exploring-telecom-reconciliation",
"DC.language": null,
"DC.relation": "discrepancy-identification-types-of-discrepancies.html",
"DC.rights.owner": "(C) Copyright 2025",
"DC.subject": null,
"DC.type": "concept",
"Data Discovery": null,
"Data Policy": null,
"Data Privacy": null,
"Discovery": null,
"External Content for AI Search": null,
"Field Administration": null,
"Field Normalization": null,
"Key Management Framework": null,
"Localization Framework": null,
"Now Platform": null,
"PlatSec": null,
"Platform": null,
"Platform Administration": null,
"Platform Performance": null,
"Platform Privacy": null,
"Proactive Triggers": null,
"Process Optimization": null,
"RN doc editing record number": null,
"Search Administration": null,
"Secrets Management": null,
"ServiceNow AI Platform": null,
"State Model": null,
"Subscription Management": null,
"Task Communications Management": null,
"Timeline Visualizations": null,
"User Administration": null,
"User Experience Analytics": null,
"Zing": null,
"ai-now-assist": null,
"app-name": null,
"app_route": null,
"azureapimanagemen": null,
"change-completed": null,
"change-item": null,
"change-request-id": null,
"change-request-reference": null,
"com.glide.embedded_help.category": null,
"component": null,
"copyright": "(C) Copyright 2025",
"crossroads": null,
"data": null,
"description": "Use the Telecom Discrepancy Identification and Reconciliation capability to keep your CMDB or Telecommunications Network Inventory (TNI) in sync with your live telecom network. By continuously auditing and comparing discovered data with inventory records, this solution helps you detect, classify,",
"dominant_bundle": null,
"erp-canvas-video": null,
"fsm-mobile": null,
"fsm-route": null,
"fsm-sched-opt": null,
"fsm-wrk-order": null,
"genai-round-7": null,
"generator": "DITA-OT",
"glossPartOfSpeech": null,
"glossStatus": null,
"guided setup": null,
"guided tours": null,
"keywords": null,
"min-toc": null,
"mini": null,
"mini-to truec": null,
"mini-toc": "yes",
"mini_toc": null,
"minitoc": null,
"modification": null,
"now-assist-app-gen-video": null,
"order": null,
"page-type": null,
"page-type ": null,
"prodname": null,
"product": null,
"product_name": null,
"release": null,
"resourceID": null,
"roles": null,
"route_page": null,
"route_params_listId": null,
"route_params_table": null,
"route_params_type": null,
"route_type": null,
"setconfigurationproperties": null,
"topic": null,
"translation-type": "source",
"version": null,
"workflow": "Customer and Industry",
"workplace-srvc-delvry-ditamap": null
},
"page_id": "product/tmt-telecom-service-operations-mgt/concept/exploring-telecom-reconciliation.html",
"page_key": 55686934,
"preprocessed_PDF": "https://downloads.docs.servicenow.com/pdf/enus/servicenow-zurich-telecom-service-ops-enus.pdf",
"rating": null,
"read_time_data": {
"char_count": 8150,
"img_count": 1,
"read_time": 5,
"video_links": [
""
],
"word_count": 1147
},
"related_links": [
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "The Telecom Discrepancy Identification and Reconciliation capability identifies and classifies mismatches between the network state (as discovered through TSOM Discovery or Service Graph Connectors) and the inventory data stored in the CMDB or TNI.",
"title": "Discrepancy identification – types of discrepancies",
"topic": "/product/tmt-telecom-service-operations-mgt/concept/discrepancy-identification-types-of-discrepancies.html",
"type": "concept",
"url": null
},
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "Activate the Telecom Discrepancy Identification and Reconciliation feature (part of the Telecom Visibility plugin) to ensure consistency between telecom network resources discovered in the live network and the data represented in the CMDB or Telecom Network Inventory (TNI). This feature helps detect and remediate mismatches automatically, supporting service accuracy and data integrity across your telecom environment.",
"title": "Activate Telecom Discrepancy Identification and Reconciliation",
"topic": "/product/tmt-telecom-service-operations-mgt/task/configure-telecom-reconciliation.html",
"type": "task",
"url": null
},
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "The Telecom Discrepancy Audit validates the integrity of configuration items (CIs) and relationships across your telecom inventory using the CMDB Compliance framework.",
"title": "Run Telecom Discrepancy audit",
"topic": "/product/tmt-telecom-service-operations-mgt/task/run-audits.html",
"type": "task",
"url": null
},
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "The system properties are part of the TSOM Visibility plugin (sn_tsom_core) and control the Telecom Discrepancy Identification & Reconciliation log (TSOM CMDB Audit). The TSOM Visibility plugin serves as an enabler for the TSOM Visibility applications, containing logic that is shared across the Telecom Discovery and Telecom Discrepancy Identification & Reconciliation solution.",
"title": "System components installed with Telecom Discrepancy Identification & Reconciliation",
"topic": "/product/tmt-telecom-service-operations-mgt/concept/system-properties-affecting-telecom-discrepancy-identification-reconciliation.html",
"type": "concept",
"url": null
}
],
"search_title": null,
"title": "Telecom Discrepancy Identification and Reconciliation",
"topic_cluster": {
"clustered_by": {
"enabled": true,
"primary_key": "versions",
"primary_sort": "top-down",
"type": "subjecthead"
},
"clustered_labels": [
"versions"
],
"clustered_topics": [
{
"bundle_id": "yokohama-telecom-service-ops",
"clustering_title": "Yokohama",
"es_archived_content": false,
"page_id": "product/tmt-telecom-service-operations-mgt/concept/exploring-telecom-reconciliation.html"
}
],
"clustering_title": "Zurich"
},
"topic_html": "<article class=\"hascomments\" data-page=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/exploring-telecom-reconciliation.html\" id=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/exploring-telecom-reconciliation.html\"><body id=\"exploring-telecom-reconciliation\"><main role=\"main\"><article role=\"article\" class=\"dita\" id=\"exploring-telecom-reconciliation\" aria-labelledby=\"title_exploring-telecom-reconciliation\">\n <h1 class=\"title topictitle1\" id=\"title_exploring-telecom-reconciliation\">Telecom Discrepancy Identification and Reconciliation</h1>\n \n \n <div class=\"body conbody\"><p class=\"shortdesc\">Use the Telecom Discrepancy Identification and Reconciliation capability to keep your CMDB or Telecommunications Network Inventory (TNI) in sync with your live telecom network. By continuously auditing and comparing discovered\n data with inventory records, this solution helps you detect, classify, and automatically remediate inconsistencies before they impact service quality, assurance, or fulfillment processes.</p>\n <p class=\"p\">Telecom Discrepancy Identification and Reconciliation is a telecom-specific capability included with the TSOM Visibility plugin. It helps confirm the integrity of your network inventory by identifying mismatches between real-time\n network data (from Discovery or external systems) and inventory records stored in the CMDB or TNI.</p>\n <p class=\"p\">This solution uses:</p>\n <ul class=\"ul\" id=\"exploring-telecom-reconciliation__ul_bmg_lmw_tfc\">\n <li class=\"li\">CMDB Compliance Certification audits to detect anomalies.</li>\n <li class=\"li\">Follow-on tasks to log and track issues.</li>\n <li class=\"li\">Automated remediation subflows to resolve discrepancies.</li>\n </ul>\n <div class=\"note note note_note\"><span class=\"note__title\">Note:</span> Keeping inventory accurate enables automation, reduces service errors, and supports regulatory compliance. It is also a foundational component of TM Forum’s Autonomous Network Operations (ANO) framework.</div>\n <section class=\"section\" id=\"exploring-telecom-reconciliation__section_yg1_x2c_b2c\"><h2 id=\"d12206e63\" class=\"title sectiontitle\">Telecom Discrepancy Identification & Reconciliation architecture</h2>\n \n <p class=\"p\"><img src=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/../images/telecom-discrepancy-identification-reconciliation.png?_LANG=enus\" class=\"image\" id=\"exploring-telecom-reconciliation__image_x2k_4nj_b2c\" alt=\"Telecom discrepancy identification and reconciliation framework.\"/></p>\n </section>\n <section class=\"section\" id=\"exploring-telecom-reconciliation__section_t5b_tmw_tfc\"><h2 id=\"d12206e77\" class=\"title sectiontitle\">Key features</h2>\n \n <div class=\"p\">\n <div class=\"table-wrap\"><table count-columns=\"2\" class=\"table\" id=\"exploring-telecom-reconciliation__table_scd_5mw_tfc\"><caption><span class=\"table--title-label\">Table 1. </span><span class=\"title\">Key features of Telecom Discrepancy Identification and Reconciliation</span></caption><colgroup><col/><col/></colgroup><thead class=\"thead\">\n <tr class=\"row\">\n <th class=\"entry\" id=\"exploring-telecom-reconciliation__table_scd_5mw_tfc__entry__1\">Feature</th>\n <th class=\"entry\" id=\"exploring-telecom-reconciliation__table_scd_5mw_tfc__entry__2\">Description</th>\n </tr>\n </thead><tbody class=\"tbody\">\n <tr class=\"row\">\n <td class=\"entry\" headers=\"exploring-telecom-reconciliation__table_scd_5mw_tfc__entry__1\">Continuous audit checks</td>\n <td class=\"entry\" headers=\"exploring-telecom-reconciliation__table_scd_5mw_tfc__entry__2\">Compares discovered network data with inventory records using Certification Audits.</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry\" headers=\"exploring-telecom-reconciliation__table_scd_5mw_tfc__entry__1\">Discrepancy detection</td>\n <td class=\"entry\" headers=\"exploring-telecom-reconciliation__table_scd_5mw_tfc__entry__2\">Identifies CIs that are missing, misconfigured, or misaligned in terms of hierarchy or attribute values.</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry\" headers=\"exploring-telecom-reconciliation__table_scd_5mw_tfc__entry__1\">Follow-On task generation</td>\n <td class=\"entry\" headers=\"exploring-telecom-reconciliation__table_scd_5mw_tfc__entry__2\">Automatically creates tasks for each discrepancy to enable tracking and remediation.</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry\" headers=\"exploring-telecom-reconciliation__table_scd_5mw_tfc__entry__1\">Automated remediation</td>\n <td class=\"entry\" headers=\"exploring-telecom-reconciliation__table_scd_5mw_tfc__entry__2\">Uses Flow Designer subflows to resolve issues such as outdated CIs, invalid relationships, and missing discovery data.</td>\n </tr>\n </tbody></table></div>\n </div>\n </section>\n <section class=\"section\" id=\"exploring-telecom-reconciliation__id_yyy_qrj_yfc\"><h2 id=\"d12206e150\" class=\"title sectiontitle\">How Telecom Discrepancy Identification & Reconciliation works</h2>\n \n <p class=\"p\">Once the discovery process is complete, the CMDB Compliance framework identifies mismatches between discovered data and inventory records using scheduled or on-demand compliance audits.</p>\n <ul class=\"ul\" id=\"exploring-telecom-reconciliation__ul_irz_qrj_yfc\">\n <li class=\"li\">Compliance Audits: Compare discovered network data with CMDB inventory records to detect inconsistencies.</li>\n <li class=\"li\">Follow-On Tasks: Automatically generated for each failed audit. These tasks document and categorize the identified discrepancies.</li>\n <li class=\"li\">Remediation Subflows: Launched from Follow-On Tasks to resolve discrepancies by updating, decommissioning, or realigning Configuration Items (CIs).</li>\n </ul>\n <div class=\"note note note_note\"><span class=\"note__title\">Note:</span> For more information, see <a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept/discrepancy-identification-types-of-discrepancies.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/discrepancy-identification-types-of-discrepancies.html\" class=\"xref\" title=\"The Telecom Discrepancy Identification and Reconciliation capability identifies and classifies mismatches between the network state (as discovered through TSOM Discovery or Service Graph Connectors) and the inventory data stored in the CMDB or TNI.\">Discrepancy identification – types of discrepancies</a>.</div>\n </section>\n <section class=\"section\" id=\"exploring-telecom-reconciliation__section_qt1_nmc_b2c\"><h2 id=\"d12206e181\" class=\"title sectiontitle\">CMDB Compliance and Telecom Discrepancy Identification & Reconciliation</h2>\n \n <div class=\"p\">CMDB Compliance is a toolset that enables administrators to certify CMDB data for accuracy and identify discrepancies detected during compliance audits. It can also automatically generate and assign Follow-on Tasks for failed audit\n records, which serve as tasks to trigger an appropriate remediation subflow to correct discrepancies. CMDB Compliance Audits form the foundation of our Telecom Discrepancy Identification & Reconciliation.<ul class=\"ul\" id=\"exploring-telecom-reconciliation__ul_g2q_5mc_b2c\">\n <li class=\"li\">CMDB Compliance runs audits as a post-processing rule, identifying anomalies (discrepancies) in the CMDB.</li>\n <li class=\"li\">CMDB Compliance creates a Follow-On Task for each Audit Record in a failed state (the failed state is the result of an audit finding an anomaly or discrepancy in the CMDB). A remediation flow can be designed and triggered for each\n Follow-On Task to address and resolve the discrepancy.</li>\n </ul></div>\n <p class=\"p\">The logic for Telecom Discrepancy Identification & Reconciliation, as well as the example remediation subflows, are automatically with the TSOM Visibility plugin. For more information on the general CMDB Compliance toolset, see <a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept//csh\" href=\"https://servicenow-be-prod.servicenow.com/csh?topicname=c_Compliance&version=zurich&pubname=zurich-servicenow-platform\" class=\"xref\">CMDB Compliance</a>.</p>\n </section>\n <section class=\"section\" id=\"exploring-telecom-reconciliation__section_mpg_vvc_b2c\"><h2 id=\"d12206e205\" class=\"title sectiontitle\">Discrepancy Identification Scenarios (using Compliance Audits)</h2>\n \n <div class=\"p\">Discrepancy identification in TSOM Visibility relies on using CMDB Compliance (Certification Audits) and has extended it by adding specific logic that uses model relationships and information to identify mismatches. To support\n remediation, the system generates specific reconciliation task types for each issue found, such as:<ul class=\"ul\" id=\"exploring-telecom-reconciliation__ul_zrg_jgl_wfc\">\n <li class=\"li\">Slots occupied discrepancy</li>\n <li class=\"li\">Most recent discovery date not set</li>\n <li class=\"li\">Most recent discovery date not within configured threshold</li>\n <li class=\"li\">Model relationships not defined</li>\n <li class=\"li\">CI model not found</li>\n <li class=\"li\">Incorrect number of relationships</li>\n <li class=\"li\">Reference to Logical Interface not found</li>\n </ul></div>\n <div class=\"p\">You can use the following audits to identify the discrepancies in the discovered physical and logical entities<ul class=\"ul\" id=\"exploring-telecom-reconciliation__ul_hkf_h2b_yfc\">\n <li class=\"li\">Telecom Discrepancy Audit</li>\n <li class=\"li\">Telecom Logical Connections Discrepancy Audit</li>\n <li class=\"li\">Telecom Network Topology Discrepancy Audit</li>\n </ul><div class=\"note note note_note\"><span class=\"note__title\">Note:</span> For more information on the general compliance audits, see <a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept//csh\" href=\"https://servicenow-be-prod.servicenow.com/csh?topicname=c_CertificationAudits&version=zurich&pubname=zurich-servicenow-platform\" class=\"xref\">Certification audits</a>.</div></div>\n </section>\n <section class=\"section\" id=\"exploring-telecom-reconciliation__section_tz1_m1d_b2c\"><h2 id=\"d12206e258\" class=\"title sectiontitle\">Automation and UI Integration</h2>\n \n <div class=\"p\">\n <ul class=\"ul\" id=\"exploring-telecom-reconciliation__ul_cxp_fww_tfc\">\n <li class=\"li\">Every failed audit automatically creates a Follow-On Task.</li>\n <li class=\"li\">Tasks can trigger prebuilt or custom subflows using Flow Designer.</li>\n <li class=\"li\">Manual remediation can be initiated using a "Remediate" UI action button in the task form.</li>\n <li class=\"li\">Remediation steps are recorded in work notes for visibility and auditing.</li>\n </ul>\n <div class=\"note note note_note\"><span class=\"note__title\">Note:</span> For more information on how to build a subflow, see <a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept//csh\" href=\"https://servicenow-be-prod.servicenow.com/csh?topicname=subflows&version=zurich&pubname=zurich-build-workflows\" class=\"xref\">Building subflows</a>.</div>\n </div>\n </section>\n <section class=\"section\" id=\"exploring-telecom-reconciliation__section_mhf_5wc_b2c\"><h2 id=\"d12206e289\" class=\"title sectiontitle\">Follow-On Task types created for failed Audit Result Records</h2>\n \n <div class=\"p\">The following discrepancy types (Audit Results) can be found for Parent CI and child CIs for each relationship record in the CI Relationship table (cmdb_rel_ci) that matches the conditions, and the following Follow-On Tasks can be\n created for each of the failed Audit Results:<ol class=\"ol\" id=\"exploring-telecom-reconciliation__ol_c5l_rzc_b2c\">\n <li class=\"li\">The most recent discovery date not set- generated in case the Most recent discovery date field in CI is missing.</li>\n <li class=\"li\">The most recent discovery date not within configured threshold- generated in case the difference in the Most recent discovery date field value between a Parent CI and child CI is more than 2.5 days. For example, By default, it is\n set to 2.5 days in the sn_tsom_core.discovered_date.diff.threshold.in.days system property and can be changed.</li>\n <li class=\"li\">CI model not found–(the ‘Model ID’ field isn’t set or data is invalid). Generated in case a corresponding CI model isn’t found. If a CI model isn’t found, the next validations (4-6) are irrelevant because they rely on CI models. In\n case a CI model is found, the audit will continue to the next validations (4-6).</li>\n <li class=\"li\">Slots occupied discrepancy-Generated in case a card occupies an incorrect number of Slots.</li>\n <li class=\"li\">Model relationships not defined-relevant only if TNI is installed. Generated if the audit is unable to find a relationship between Parent and child CI models in the Network Model Relationships table.</li>\n <li class=\"li\">Incorrect number of relationships - relevant only if TNI is installed. Generated if the audit finds that the number of discovered child CI records exceeds the maximum number of its corresponding Parent CI record in the model\n relationship Count field in the Network Model Relationship table.</li>\n <li class=\"li\">Incorrect number of relationships - generated during the Logical Connection Discrepancy Audit when a logical interface is associated with more than one logical connection, violating the expected one-to-one mapping.</li>\n <li class=\"li\">Incorrect number of relationships - generated during the Network Topology Discrepancy Audit when a network topology record does not meet the required relationship criteria. Specifically:<ul class=\"ul\" id=\"exploring-telecom-reconciliation__ul_szb_bjb_yfc\">\n <li class=\"li\">The record must have at least one "Contains:Contained By" relationship with an equipment CI.</li>\n <li class=\"li\">The record must also have at least one "Members:Member Of" relationship with a logical connection CI.</li>\n </ul></li>\n <li class=\"li\">Reference to Logical Interface not found - generated during the Logical Connection Discrepancy Audit when a logical connection is missing one of the end points (Port A or Port z, or both).</li>\n </ol></div>\n </section>\n <section class=\"section\" id=\"exploring-telecom-reconciliation__section_j44_vlj_wfc\"><h2 id=\"d12206e337\" class=\"title sectiontitle\">Telecom Reconciliation</h2>\n \n <div class=\"p\">Automate reconciliation of network inventory discrepancies and enhance operational efficiency. Telecom Reconciliation helps to:<ul class=\"ul\" id=\"exploring-telecom-reconciliation__ul_ygg_5mj_wfc\">\n <li class=\"li\">Identify and resolve discrepancies between live network inventory and CMDB inventory to ensure alignment and boost productivity</li>\n <li class=\"li\">Empower users with auto generated discrepancy reports detailing the type of discrepancy</li>\n <li class=\"li\">Provide users with recommended corrective actions and the flexibility and control to choose between manual or automated methods to resolve discrepancies </li>\n <li class=\"li\">Improve operations by automatically aligning the operational status of network resources with the same status in the inventory CMDB</li>\n </ul></div>\n </section>\n </div>\n <nav role=\"navigation\"></nav><nav role=\"navigation\" class=\"tasksNavigation\"></nav><nav role=\"navigation\" class=\"related-links\"><div class=\"col-md-4\"><dt>Related tasks</dt><dd><ul><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/task/configure-telecom-reconciliation.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/configure-telecom-reconciliation.html\" class=\"link\" title=\"Activate the Telecom Discrepancy Identification and Reconciliation feature (part of the Telecom Visibility plugin) to ensure consistency between telecom network resources discovered in the live network and the data represented in the CMDB or Telecom Network Inventory (TNI). This feature helps detect and remediate mismatches automatically, supporting service accuracy and data integrity across your telecom environment.\">Activate Telecom Discrepancy Identification and Reconciliation</a></li><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/task/run-audits.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/run-audits.html\" class=\"link\" title=\"The Telecom Discrepancy Audit validates the integrity of configuration items (CIs) and relationships across your telecom inventory using the CMDB Compliance framework.\">Run Telecom Discrepancy audit</a></li></ul></dd></div><div class=\"col-md-4\"><dt>Related concepts</dt><dd><ul><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept/discrepancy-identification-types-of-discrepancies.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/discrepancy-identification-types-of-discrepancies.html\" class=\"link\" title=\"The Telecom Discrepancy Identification and Reconciliation capability identifies and classifies mismatches between the network state (as discovered through TSOM Discovery or Service Graph Connectors) and the inventory data stored in the CMDB or TNI.\">Discrepancy identification – types of discrepancies</a></li><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept/system-properties-affecting-telecom-discrepancy-identification-reconciliation.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/system-properties-affecting-telecom-discrepancy-identification-reconciliation.html\" class=\"link\" title=\"The system properties are part of the TSOM Visibility plugin (sn_tsom_core) and control the Telecom Discrepancy Identification & Reconciliation log (TSOM CMDB Audit). The TSOM Visibility plugin serves as an enabler for the TSOM Visibility applications, containing logic that is shared across the Telecom Discovery and Telecom Discrepancy Identification & Reconciliation solution.\">System components installed with Telecom Discrepancy Identification & Reconciliation</a></li></ul></dd></div></nav>\n</article></main></body></article>",
"topic_language": "enus",
"views": 0,
"your_rating": null
} | # Telecom Discrepancy Identification and Reconciliation
Use the Telecom Discrepancy Identification and Reconciliation capability to keep your CMDB or Telecommunications Network Inventory (TNI) in sync with your live telecom network. By continuously auditing and comparing discovered
data with inventory records, this solution helps you detect, classify, and automatically remediate inconsistencies before they impact service quality, assurance, or fulfillment processes.
Telecom Discrepancy Identification and Reconciliation is a telecom-specific capability included with the TSOM Visibility plugin. It helps confirm the integrity of your network inventory by identifying mismatches between real-time
network data (from Discovery or external systems) and inventory records stored in the CMDB or TNI.
This solution uses:
* CMDB Compliance Certification audits to detect anomalies.
* Follow-on tasks to log and track issues.
* Automated remediation subflows to resolve discrepancies.
Note: Keeping inventory accurate enables automation, reduces service errors, and supports regulatory compliance. It is also a foundational component of TM Forum’s Autonomous Network Operations (ANO) framework.
## Telecom Discrepancy Identification & Reconciliation architecture
## Key features
Table 1. Key features of Telecom Discrepancy Identification and Reconciliation
| Feature | Description |
| --- | --- |
| Continuous audit checks | Compares discovered network data with inventory records using Certification Audits. |
| Discrepancy detection | Identifies CIs that are missing, misconfigured, or misaligned in terms of hierarchy or attribute values. |
| Follow-On task generation | Automatically creates tasks for each discrepancy to enable tracking and remediation. |
| Automated remediation | Uses Flow Designer subflows to resolve issues such as outdated CIs, invalid relationships, and missing discovery data. |
## How Telecom Discrepancy Identification & Reconciliation works
Once the discovery process is complete, the CMDB Compliance framework identifies mismatches between discovered data and inventory records using scheduled or on-demand compliance audits.
* Compliance Audits: Compare discovered network data with CMDB inventory records to detect inconsistencies.
* Follow-On Tasks: Automatically generated for each failed audit. These tasks document and categorize the identified discrepancies.
* Remediation Subflows: Launched from Follow-On Tasks to resolve discrepancies by updating, decommissioning, or realigning Configuration Items (CIs).
Note: For more information, see Discrepancy identification – types of discrepancies.
## CMDB Compliance and Telecom Discrepancy Identification & Reconciliation
CMDB Compliance is a toolset that enables administrators to certify CMDB data for accuracy and identify discrepancies detected during compliance audits. It can also automatically generate and assign Follow-on Tasks for failed audit
records, which serve as tasks to trigger an appropriate remediation subflow to correct discrepancies. CMDB Compliance Audits form the foundation of our Telecom Discrepancy Identification & Reconciliation.
* CMDB Compliance runs audits as a post-processing rule, identifying anomalies (discrepancies) in the CMDB.
* CMDB Compliance creates a Follow-On Task for each Audit Record in a failed state (the failed state is the result of an audit finding an anomaly or discrepancy in the CMDB). A remediation flow can be designed and triggered for each
Follow-On Task to address and resolve the discrepancy.
The logic for Telecom Discrepancy Identification & Reconciliation, as well as the example remediation subflows, are automatically with the TSOM Visibility plugin. For more information on the general CMDB Compliance toolset, see CMDB Compliance.
## Discrepancy Identification Scenarios (using Compliance Audits)
Discrepancy identification in TSOM Visibility relies on using CMDB Compliance (Certification Audits) and has extended it by adding specific logic that uses model relationships and information to identify mismatches. To support
remediation, the system generates specific reconciliation task types for each issue found, such as:
* Slots occupied discrepancy
* Most recent discovery date not set
* Most recent discovery date not within configured threshold
* Model relationships not defined
* CI model not found
* Incorrect number of relationships
* Reference to Logical Interface not found
You can use the following audits to identify the discrepancies in the discovered physical and logical entities
* Telecom Discrepancy Audit
* Telecom Logical Connections Discrepancy Audit
* Telecom Network Topology Discrepancy Audit
Note: For more information on the general compliance audits, see Certification audits.
## Automation and UI Integration
* Every failed audit automatically creates a Follow-On Task.
* Tasks can trigger prebuilt or custom subflows using Flow Designer.
* Manual remediation can be initiated using a "Remediate" UI action button in the task form.
* Remediation steps are recorded in work notes for visibility and auditing.
Note: For more information on how to build a subflow, see Building subflows.
## Follow-On Task types created for failed Audit Result Records
The following discrepancy types (Audit Results) can be found for Parent CI and child CIs for each relationship record in the CI Relationship table (cmdb\_rel\_ci) that matches the conditions, and the following Follow-On Tasks can be
created for each of the failed Audit Results:
1. The most recent discovery date not set- generated in case the Most recent discovery date field in CI is missing.
2. The most recent discovery date not within configured threshold- generated in case the difference in the Most recent discovery date field value between a Parent CI and child CI is more than 2.5 days. For example, By default, it is
set to 2.5 days in the sn\_tsom\_core.discovered\_date.diff.threshold.in.days system property and can be changed.
3. CI model not found–(the ‘Model ID’ field isn’t set or data is invalid). Generated in case a corresponding CI model isn’t found. If a CI model isn’t found, the next validations (4-6) are irrelevant because they rely on CI models. In
case a CI model is found, the audit will continue to the next validations (4-6).
4. Slots occupied discrepancy-Generated in case a card occupies an incorrect number of Slots.
5. Model relationships not defined-relevant only if TNI is installed. Generated if the audit is unable to find a relationship between Parent and child CI models in the Network Model Relationships table.
6. Incorrect number of relationships - relevant only if TNI is installed. Generated if the audit finds that the number of discovered child CI records exceeds the maximum number of its corresponding Parent CI record in the model
relationship Count field in the Network Model Relationship table.
7. Incorrect number of relationships - generated during the Logical Connection Discrepancy Audit when a logical interface is associated with more than one logical connection, violating the expected one-to-one mapping.
8. Incorrect number of relationships - generated during the Network Topology Discrepancy Audit when a network topology record does not meet the required relationship criteria. Specifically:
* The record must have at least one "Contains:Contained By" relationship with an equipment CI.
* The record must also have at least one "Members:Member Of" relationship with a logical connection CI.
9. Reference to Logical Interface not found - generated during the Logical Connection Discrepancy Audit when a logical connection is missing one of the end points (Port A or Port z, or both).
## Telecom Reconciliation
Automate reconciliation of network inventory discrepancies and enhance operational efficiency. Telecom Reconciliation helps to:
* Identify and resolve discrepancies between live network inventory and CMDB inventory to ensure alignment and boost productivity
* Empower users with auto generated discrepancy reports detailing the type of discrepancy
* Provide users with recommended corrective actions and the flexibility and control to choose between manual or automated methods to resolve discrepancies
* Improve operations by automatically aligning the operational status of network resources with the same status in the inventory CMDB
| ---
title: Telecom Discrepancy Identification and Reconciliation
description: Use the Telecom Discrepancy Identification and Reconciliation capability
to keep your CMDB or Telecommunications Network Inventory (TNI) in sync with your
live telecom network. By continuously auditing and comparing discovered data with
inventory records, this solution helps you detect, classify,
keywords: []
breadcrumbs:
- Telecommunications Service Operations Management
- Exploring Telecommunications Service Operations Management
- Telecom Visibility
---
# Telecom Discrepancy Identification and Reconciliation
Use the Telecom Discrepancy Identification and Reconciliation capability to keep your CMDB or Telecommunications Network Inventory (TNI) in sync with your live telecom network. By continuously auditing and comparing discovered
data with inventory records, this solution helps you detect, classify, and automatically remediate inconsistencies before they impact service quality, assurance, or fulfillment processes.
Telecom Discrepancy Identification and Reconciliation is a telecom-specific capability included with the TSOM Visibility plugin. It helps confirm the integrity of your network inventory by identifying mismatches between real-time
network data (from Discovery or external systems) and inventory records stored in the CMDB or TNI.
This solution uses:
* CMDB Compliance Certification audits to detect anomalies.
* Follow-on tasks to log and track issues.
* Automated remediation subflows to resolve discrepancies.
Note: Keeping inventory accurate enables automation, reduces service errors, and supports regulatory compliance. It is also a foundational component of TM Forum’s Autonomous Network Operations (ANO) framework.
## Telecom Discrepancy Identification & Reconciliation architecture
## Key features
Table 1. Key features of Telecom Discrepancy Identification and Reconciliation
| Feature | Description |
| --- | --- |
| Continuous audit checks | Compares discovered network data with inventory records using Certification Audits. |
| Discrepancy detection | Identifies CIs that are missing, misconfigured, or misaligned in terms of hierarchy or attribute values. |
| Follow-On task generation | Automatically creates tasks for each discrepancy to enable tracking and remediation. |
| Automated remediation | Uses Flow Designer subflows to resolve issues such as outdated CIs, invalid relationships, and missing discovery data. |
## How Telecom Discrepancy Identification & Reconciliation works
Once the discovery process is complete, the CMDB Compliance framework identifies mismatches between discovered data and inventory records using scheduled or on-demand compliance audits.
* Compliance Audits: Compare discovered network data with CMDB inventory records to detect inconsistencies.
* Follow-On Tasks: Automatically generated for each failed audit. These tasks document and categorize the identified discrepancies.
* Remediation Subflows: Launched from Follow-On Tasks to resolve discrepancies by updating, decommissioning, or realigning Configuration Items (CIs).
Note: For more information, see Discrepancy identification – types of discrepancies.
## CMDB Compliance and Telecom Discrepancy Identification & Reconciliation
CMDB Compliance is a toolset that enables administrators to certify CMDB data for accuracy and identify discrepancies detected during compliance audits. It can also automatically generate and assign Follow-on Tasks for failed audit
records, which serve as tasks to trigger an appropriate remediation subflow to correct discrepancies. CMDB Compliance Audits form the foundation of our Telecom Discrepancy Identification & Reconciliation.
* CMDB Compliance runs audits as a post-processing rule, identifying anomalies (discrepancies) in the CMDB.
* CMDB Compliance creates a Follow-On Task for each Audit Record in a failed state (the failed state is the result of an audit finding an anomaly or discrepancy in the CMDB). A remediation flow can be designed and triggered for each
Follow-On Task to address and resolve the discrepancy.
The logic for Telecom Discrepancy Identification & Reconciliation, as well as the example remediation subflows, are automatically with the TSOM Visibility plugin. For more information on the general CMDB Compliance toolset, see CMDB Compliance.
## Discrepancy Identification Scenarios (using Compliance Audits)
Discrepancy identification in TSOM Visibility relies on using CMDB Compliance (Certification Audits) and has extended it by adding specific logic that uses model relationships and information to identify mismatches. To support
remediation, the system generates specific reconciliation task types for each issue found, such as:
* Slots occupied discrepancy
* Most recent discovery date not set
* Most recent discovery date not within configured threshold
* Model relationships not defined
* CI model not found
* Incorrect number of relationships
* Reference to Logical Interface not found
You can use the following audits to identify the discrepancies in the discovered physical and logical entities
* Telecom Discrepancy Audit
* Telecom Logical Connections Discrepancy Audit
* Telecom Network Topology Discrepancy Audit
Note: For more information on the general compliance audits, see Certification audits.
## Automation and UI Integration
* Every failed audit automatically creates a Follow-On Task.
* Tasks can trigger prebuilt or custom subflows using Flow Designer.
* Manual remediation can be initiated using a "Remediate" UI action button in the task form.
* Remediation steps are recorded in work notes for visibility and auditing.
Note: For more information on how to build a subflow, see Building subflows.
## Follow-On Task types created for failed Audit Result Records
The following discrepancy types (Audit Results) can be found for Parent CI and child CIs for each relationship record in the CI Relationship table (cmdb\_rel\_ci) that matches the conditions, and the following Follow-On Tasks can be
created for each of the failed Audit Results:
1. The most recent discovery date not set- generated in case the Most recent discovery date field in CI is missing.
2. The most recent discovery date not within configured threshold- generated in case the difference in the Most recent discovery date field value between a Parent CI and child CI is more than 2.5 days. For example, By default, it is
set to 2.5 days in the sn\_tsom\_core.discovered\_date.diff.threshold.in.days system property and can be changed.
3. CI model not found–(the ‘Model ID’ field isn’t set or data is invalid). Generated in case a corresponding CI model isn’t found. If a CI model isn’t found, the next validations (4-6) are irrelevant because they rely on CI models. In
case a CI model is found, the audit will continue to the next validations (4-6).
4. Slots occupied discrepancy-Generated in case a card occupies an incorrect number of Slots.
5. Model relationships not defined-relevant only if TNI is installed. Generated if the audit is unable to find a relationship between Parent and child CI models in the Network Model Relationships table.
6. Incorrect number of relationships - relevant only if TNI is installed. Generated if the audit finds that the number of discovered child CI records exceeds the maximum number of its corresponding Parent CI record in the model
relationship Count field in the Network Model Relationship table.
7. Incorrect number of relationships - generated during the Logical Connection Discrepancy Audit when a logical interface is associated with more than one logical connection, violating the expected one-to-one mapping.
8. Incorrect number of relationships - generated during the Network Topology Discrepancy Audit when a network topology record does not meet the required relationship criteria. Specifically:
* The record must have at least one "Contains:Contained By" relationship with an equipment CI.
* The record must also have at least one "Members:Member Of" relationship with a logical connection CI.
9. Reference to Logical Interface not found - generated during the Logical Connection Discrepancy Audit when a logical connection is missing one of the end points (Port A or Port z, or both).
## Telecom Reconciliation
Automate reconciliation of network inventory discrepancies and enhance operational efficiency. Telecom Reconciliation helps to:
* Identify and resolve discrepancies between live network inventory and CMDB inventory to ensure alignment and boost productivity
* Empower users with auto generated discrepancy reports detailing the type of discrepancy
* Provide users with recommended corrective actions and the flexibility and control to choose between manual or automated methods to resolve discrepancies
* Improve operations by automatically aligning the operational status of network resources with the same status in the inventory CMDB
|
https://www.servicenow.com/docs/en-US/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/exploring-the-telco-generic-schema-etl-framework.html | https://servicenow-be-prod.servicenow.com/api/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/exploring-the-telco-generic-schema-etl-framework.html | 2025-08-02 | daily | 0.5 | 268.xml | en-US | zurich-telecom-service-ops | product/tmt-telecom-service-operations-mgt/concept/exploring-the-telco-generic-schema-etl-framework.html | zurich | Telecom Discovery Builder framework | The Telecom Discovery Builder framework ETL (Extract, Transform, Load) is a reusable and schema-aligned component delivered with the Telecom Service Operations Management (TSOM) Core application. It provides a consistent and extensible method for ingesting telecom inventory data into the ServiceNow | [] | [
"Telecommunications Service Operations Management",
"Exploring Telecommunications Service Operations Management",
"Telecom Visibility",
"Telecom Discovery"
] | <article class="hascomments" data-page="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/exploring-the-telco-generic-schema-etl-framework.html" id="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/exploring-the-telco-generic-schema-etl-framework.html"><body id="exploring-the-telco-generic-schema-etl-framework"><main role="main"><article role="article" class="dita" id="exploring-the-telco-generic-schema-etl-framework" aria-labelledby="title_exploring-the-telco-generic-schema-etl-framework">
<h1 class="title topictitle1" id="title_exploring-the-telco-generic-schema-etl-framework">Telecom Discovery Builder framework</h1>
<div class="body conbody"><p class="shortdesc">The Telecom Discovery Builder framework ETL (Extract, Transform, Load) is a reusable and schema-aligned component delivered with the Telecom Service Operations Management (TSOM) Core application. It provides a consistent and
extensible method for ingesting telecom inventory data into the ServiceNow Configuration Management Database (CMDB) across multiple Service Graph Connectors (SGCs).</p>
<p class="p">The Telecom Discovery Builder framework ETL serves as a baseline data ingestion utility designed to handle telecom-specific configuration item (CI) data. It enables connector development teams to avoid building ETLs from scratch by
offering a standardized transform logic that can be duplicated and customized for each connector.</p>
<p class="p">Once the TSOM Core plugin is activated, the generic ETL is auto-provisioned and becomes available in the IntegrationHub ETL Studio, ready to be reused and adapted to connector-specific needs.</p>
<section class="section" id="exploring-the-telco-generic-schema-etl-framework__section_rmr_xgy_dfc"><h2 id="d2529e48" class="title sectiontitle">Why and when to use the Telecom Discovery Builder framework</h2>
<p class="p">Building ETL logic or transform maps from scratch for each new telecom connector can be time-consuming, error-prone, and inconsistent. The Telecom Discovery Builder framework streamlines the process by providing a standardized,
reusable foundation that ensures consistency across implementations.</p>
<p class="p">Use the Telecom Discovery Builder framework when you want to:</p>
<ul class="ul" id="exploring-the-telco-generic-schema-etl-framework__ul_c5x_zgy_dfc">
<li class="li">Deploy a new Service Graph Connector in a telecom environment and want to avoid building the ETL from scratch.</li>
<li class="li">Maintain schema-aligned consistency across multiple connectors and platform instances.</li>
<li class="li">Discovery payloads and CI relationships compliant with TNI (Telecom Network Inventory). For more information, see <a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/concept//csh" href="https://servicenow-be-prod.servicenow.com/csh?topicname=telecom-network-inventory&version=zurich&pubname=zurich-telecom-network-inventory" class="xref">Telecommunications Network Inventory</a>.</li>
<li class="li">Work within an SGC (Service Graph Connector) application scope and want to customize ETL behavior without modifying core logic.</li>
<li class="li">Benefit from predefined mappings, validated JSON schema support, and a UI-driven configuration interface.</li>
</ul>
</section>
<section class="section" id="exploring-the-telco-generic-schema-etl-framework__section_n34_vhy_dfc"><h2 id="d2529e82" class="title sectiontitle">Key capabilities and features</h2>
<div class="p">
<ul class="ul" id="exploring-the-telco-generic-schema-etl-framework__ul_zcm_xhy_dfc">
<li class="li">Auto-provisioned with TSOM core: Installs automatically and is ready to use across telecom connectors.</li>
<li class="li">Generic schema-based ingestion: Supports a unified data schema for telecom CIs.</li>
<li class="li">Supports duplication and customization: Duplicate the Telecom Discovery Builder framework ETL into your application scope using IntegrationHub ETL Studio.</li>
<li class="li">TNI support: Aligned to the TNI data model and the ETL logic can be extended to generate and link TNI entities.</li>
<li class="li">Flexible field mapping interface: Configure import sets, data sources, targets, and transformation logic through a UI-driven experience.</li>
</ul>
</div>
</section>
<section class="section" id="exploring-the-telco-generic-schema-etl-framework__section_ypx_1ms_z2c"><h2 id="d2529e109" class="title sectiontitle">Key benefits</h2>
<div class="p">Use Telecom Discovery Builder framework ETL to gain:<ul class="ul" id="exploring-the-telco-generic-schema-etl-framework__ul_m4l_cms_z2c">
<li class="li">Consistency in how telecom configuration items (CIs) are structured and loaded into the CMDB.</li>
<li class="li">Reusability through duplication and customization across connectors.</li>
<li class="li">Compliance with TNI schemas and discovery model requirements.</li>
<li class="li">Flexibility to extend and tailor data transformations without compromising the base schema.</li>
</ul></div>
</section>
</div>
<nav role="navigation"></nav><nav role="navigation" class="tasksNavigation"></nav><nav role="navigation" class="related-links"><div class="col-md-4"><dt>Related tasks</dt><dd><ul><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/task/configuring-tni-entiry-support-for-duplicated-etls.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/configuring-tni-entiry-support-for-duplicated-etls.html" class="link" title="When Telecom Network Inventory (TNI) is enabled, every Configuration Item (CI) created by a duplicated ETL must have a corresponding TNI Entity.">Extend TNI entity support for duplicated ETLs</a></li></ul></dd></div><div class="col-md-4"><dt>Related concepts</dt><dd><ul><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/concept/configuring-the-telco-generic-schema-etl.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/configuring-the-telco-generic-schema-etl.html" class="link" title="Leverage the prebuilt Telecom Discovery Builder framework ETL by duplicating it into your connector scope, assigning the appropriate data source, and deploying it as part of a new service graph connector.">Configuring the Telecom Discovery Builder framework ETL in a connector</a></li></ul></dd></div></nav>
</article></main></body></article> | {
"attachments": {
"all_attachments": null,
"topic_attachments": []
},
"available_languages": [
"enus"
],
"breadcrumbs": [
{
"title": "Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html"
},
{
"title": "Exploring Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/exploring-tsom.html"
},
{
"title": "Telecom Visibility",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/tsom-visibility.html"
},
{
"title": "Telecom Discovery",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/exploring-telecom-discovery.html"
}
],
"breadcrumbs_html": "<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops\">Zurich Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html\">Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/exploring-tsom.html\">Exploring Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/tsom-visibility.html\">Telecom Visibility</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/exploring-telecom-discovery.html\">Telecom Discovery</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<span class=\"active\">Telecom Discovery Builder framework</span>",
"bundle_id": "zurich-telecom-service-ops",
"bundle_key": 2733,
"bundle_landing_page": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html",
"bundle_subtitle": null,
"bundle_title": "Zurich Telecommunications Service Operations Management",
"canonical_link": null,
"dates": {
"Added on": "2025-08-02T00:48:08.794016Z",
"Created on": "2025-04-14T00:00:00Z",
"Initial upload": "2025-07-30T22:24:33.519043Z",
"Updated on": "2025-07-31T00:00:00Z"
},
"dislike_url": "https://servicenow-be-prod.servicenow.com/dislike/55686935",
"dislikes": 0,
"es_archived_content": false,
"is_in_fav": false,
"is_liked": null,
"is_watched": false,
"keywords": [
" zurich zurich"
],
"labels": [
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "zurich",
"navtitle": "Zurich",
"outputclasses": [],
"subjectHeadId": "versions",
"subjectheadNavtitle": "Versions",
"visibility": "show-facet"
},
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "tsom",
"navtitle": "Telecommunications Service Operations Management",
"outputclasses": [],
"subjectHeadId": "products",
"subjectheadNavtitle": "Products",
"visibility": "show-facet"
}
],
"labels_text": "Versions > Zurich; Products > CRM and Industry Products > Telecommunications Media and Technology Assurance > Telecommunications Service Operations Management",
"like_url": "https://servicenow-be-prod.servicenow.com/like/55686935",
"likes": 0,
"metadata": {
"AI Search": null,
"AI Search Assist": null,
"Application Insights": null,
"Capabilities": null,
"Code Signing": null,
"Contextual Search": null,
"DC.contributor": null,
"DC.coverage": null,
"DC.creator": "ServiceNow",
"DC.date.created": "2025-04-14T12:55:19+05:30",
"DC.date.modified": "2025-07-31",
"DC.format": "HTML5",
"DC.identifier": "exploring-the-telco-generic-schema-etl-framework",
"DC.language": null,
"DC.relation": "configuring-the-telco-generic-schema-etl.html",
"DC.rights.owner": "(C) Copyright 2025",
"DC.subject": null,
"DC.type": "concept",
"Data Discovery": null,
"Data Policy": null,
"Data Privacy": null,
"Discovery": null,
"External Content for AI Search": null,
"Field Administration": null,
"Field Normalization": null,
"Key Management Framework": null,
"Localization Framework": null,
"Now Platform": null,
"PlatSec": null,
"Platform": null,
"Platform Administration": null,
"Platform Performance": null,
"Platform Privacy": null,
"Proactive Triggers": null,
"Process Optimization": null,
"RN doc editing record number": null,
"Search Administration": null,
"Secrets Management": null,
"ServiceNow AI Platform": null,
"State Model": null,
"Subscription Management": null,
"Task Communications Management": null,
"Timeline Visualizations": null,
"User Administration": null,
"User Experience Analytics": null,
"Zing": null,
"ai-now-assist": null,
"app-name": null,
"app_route": null,
"azureapimanagemen": null,
"change-completed": null,
"change-item": null,
"change-request-id": null,
"change-request-reference": null,
"com.glide.embedded_help.category": null,
"component": null,
"copyright": "(C) Copyright 2025",
"crossroads": null,
"data": null,
"description": "The Telecom Discovery Builder framework ETL (Extract, Transform, Load) is a reusable and schema-aligned component delivered with the Telecom Service Operations Management (TSOM) Core application. It provides a consistent and extensible method for ingesting telecom inventory data into the ServiceNow",
"dominant_bundle": null,
"erp-canvas-video": null,
"fsm-mobile": null,
"fsm-route": null,
"fsm-sched-opt": null,
"fsm-wrk-order": null,
"genai-round-7": null,
"generator": "DITA-OT",
"glossPartOfSpeech": null,
"glossStatus": null,
"guided setup": null,
"guided tours": null,
"keywords": null,
"min-toc": null,
"mini": null,
"mini-to truec": null,
"mini-toc": "yes",
"mini_toc": null,
"minitoc": null,
"modification": null,
"now-assist-app-gen-video": null,
"order": null,
"page-type": null,
"page-type ": null,
"prodname": null,
"product": null,
"product_name": null,
"release": null,
"resourceID": null,
"roles": null,
"route_page": null,
"route_params_listId": null,
"route_params_table": null,
"route_params_type": null,
"route_type": null,
"setconfigurationproperties": null,
"topic": null,
"translation-type": "source",
"version": null,
"workflow": "Customer and Industry",
"workplace-srvc-delvry-ditamap": null
},
"page_id": "product/tmt-telecom-service-operations-mgt/concept/exploring-the-telco-generic-schema-etl-framework.html",
"page_key": 55686935,
"preprocessed_PDF": "https://downloads.docs.servicenow.com/pdf/enus/servicenow-zurich-telecom-service-ops-enus.pdf",
"rating": null,
"read_time_data": {
"char_count": 2924,
"img_count": 0,
"read_time": 2,
"video_links": [
""
],
"word_count": 400
},
"related_links": [
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "Leverage the prebuilt Telecom Discovery Builder framework ETL by duplicating it into your connector scope, assigning the appropriate data source, and deploying it as part of a new service graph connector.",
"title": "Configuring the Telecom Discovery Builder framework ETL in a connector",
"topic": "/product/tmt-telecom-service-operations-mgt/concept/configuring-the-telco-generic-schema-etl.html",
"type": "concept",
"url": null
},
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "When Telecom Network Inventory (TNI) is enabled, every Configuration Item (CI) created by a duplicated ETL must have a corresponding TNI Entity.",
"title": "Extend TNI entity support for duplicated ETLs",
"topic": "/product/tmt-telecom-service-operations-mgt/task/configuring-tni-entiry-support-for-duplicated-etls.html",
"type": "task",
"url": null
}
],
"search_title": null,
"title": "Telecom Discovery Builder framework",
"topic_cluster": {
"clustered_by": {
"enabled": true,
"primary_key": "versions",
"primary_sort": "top-down",
"type": "subjecthead"
},
"clustered_labels": [
"versions"
],
"clustered_topics": [],
"clustering_title": "Zurich"
},
"topic_html": "<article class=\"hascomments\" data-page=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/exploring-the-telco-generic-schema-etl-framework.html\" id=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/exploring-the-telco-generic-schema-etl-framework.html\"><body id=\"exploring-the-telco-generic-schema-etl-framework\"><main role=\"main\"><article role=\"article\" class=\"dita\" id=\"exploring-the-telco-generic-schema-etl-framework\" aria-labelledby=\"title_exploring-the-telco-generic-schema-etl-framework\">\n <h1 class=\"title topictitle1\" id=\"title_exploring-the-telco-generic-schema-etl-framework\">Telecom Discovery Builder framework</h1>\n \n \n <div class=\"body conbody\"><p class=\"shortdesc\">The Telecom Discovery Builder framework ETL (Extract, Transform, Load) is a reusable and schema-aligned component delivered with the Telecom Service Operations Management (TSOM) Core application. It provides a consistent and\n extensible method for ingesting telecom inventory data into the ServiceNow Configuration Management Database (CMDB) across multiple Service Graph Connectors (SGCs).</p>\n <p class=\"p\">The Telecom Discovery Builder framework ETL serves as a baseline data ingestion utility designed to handle telecom-specific configuration item (CI) data. It enables connector development teams to avoid building ETLs from scratch by\n offering a standardized transform logic that can be duplicated and customized for each connector.</p>\n <p class=\"p\">Once the TSOM Core plugin is activated, the generic ETL is auto-provisioned and becomes available in the IntegrationHub ETL Studio, ready to be reused and adapted to connector-specific needs.</p>\n <section class=\"section\" id=\"exploring-the-telco-generic-schema-etl-framework__section_rmr_xgy_dfc\"><h2 id=\"d2529e48\" class=\"title sectiontitle\">Why and when to use the Telecom Discovery Builder framework</h2>\n \n <p class=\"p\">Building ETL logic or transform maps from scratch for each new telecom connector can be time-consuming, error-prone, and inconsistent. The Telecom Discovery Builder framework streamlines the process by providing a standardized,\n reusable foundation that ensures consistency across implementations.</p>\n <p class=\"p\">Use the Telecom Discovery Builder framework when you want to:</p>\n <ul class=\"ul\" id=\"exploring-the-telco-generic-schema-etl-framework__ul_c5x_zgy_dfc\">\n <li class=\"li\">Deploy a new Service Graph Connector in a telecom environment and want to avoid building the ETL from scratch.</li>\n <li class=\"li\">Maintain schema-aligned consistency across multiple connectors and platform instances.</li>\n <li class=\"li\">Discovery payloads and CI relationships compliant with TNI (Telecom Network Inventory). For more information, see <a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept//csh\" href=\"https://servicenow-be-prod.servicenow.com/csh?topicname=telecom-network-inventory&version=zurich&pubname=zurich-telecom-network-inventory\" class=\"xref\">Telecommunications Network Inventory</a>.</li>\n <li class=\"li\">Work within an SGC (Service Graph Connector) application scope and want to customize ETL behavior without modifying core logic.</li>\n <li class=\"li\">Benefit from predefined mappings, validated JSON schema support, and a UI-driven configuration interface.</li>\n </ul>\n </section>\n <section class=\"section\" id=\"exploring-the-telco-generic-schema-etl-framework__section_n34_vhy_dfc\"><h2 id=\"d2529e82\" class=\"title sectiontitle\">Key capabilities and features</h2>\n \n <div class=\"p\">\n <ul class=\"ul\" id=\"exploring-the-telco-generic-schema-etl-framework__ul_zcm_xhy_dfc\">\n <li class=\"li\">Auto-provisioned with TSOM core: Installs automatically and is ready to use across telecom connectors.</li>\n <li class=\"li\">Generic schema-based ingestion: Supports a unified data schema for telecom CIs.</li>\n <li class=\"li\">Supports duplication and customization: Duplicate the Telecom Discovery Builder framework ETL into your application scope using IntegrationHub ETL Studio.</li>\n <li class=\"li\">TNI support: Aligned to the TNI data model and the ETL logic can be extended to generate and link TNI entities.</li>\n <li class=\"li\">Flexible field mapping interface: Configure import sets, data sources, targets, and transformation logic through a UI-driven experience.</li>\n </ul>\n </div>\n </section>\n <section class=\"section\" id=\"exploring-the-telco-generic-schema-etl-framework__section_ypx_1ms_z2c\"><h2 id=\"d2529e109\" class=\"title sectiontitle\">Key benefits</h2>\n \n <div class=\"p\">Use Telecom Discovery Builder framework ETL to gain:<ul class=\"ul\" id=\"exploring-the-telco-generic-schema-etl-framework__ul_m4l_cms_z2c\">\n <li class=\"li\">Consistency in how telecom configuration items (CIs) are structured and loaded into the CMDB.</li>\n <li class=\"li\">Reusability through duplication and customization across connectors.</li>\n <li class=\"li\">Compliance with TNI schemas and discovery model requirements.</li>\n <li class=\"li\">Flexibility to extend and tailor data transformations without compromising the base schema.</li>\n </ul></div>\n </section>\n </div>\n <nav role=\"navigation\"></nav><nav role=\"navigation\" class=\"tasksNavigation\"></nav><nav role=\"navigation\" class=\"related-links\"><div class=\"col-md-4\"><dt>Related tasks</dt><dd><ul><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/task/configuring-tni-entiry-support-for-duplicated-etls.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/configuring-tni-entiry-support-for-duplicated-etls.html\" class=\"link\" title=\"When Telecom Network Inventory (TNI) is enabled, every Configuration Item (CI) created by a duplicated ETL must have a corresponding TNI Entity.\">Extend TNI entity support for duplicated ETLs</a></li></ul></dd></div><div class=\"col-md-4\"><dt>Related concepts</dt><dd><ul><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept/configuring-the-telco-generic-schema-etl.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/configuring-the-telco-generic-schema-etl.html\" class=\"link\" title=\"Leverage the prebuilt Telecom Discovery Builder framework ETL by duplicating it into your connector scope, assigning the appropriate data source, and deploying it as part of a new service graph connector.\">Configuring the Telecom Discovery Builder framework ETL in a connector</a></li></ul></dd></div></nav>\n</article></main></body></article>",
"topic_language": "enus",
"views": 0,
"your_rating": null
} | # Telecom Discovery Builder framework
The Telecom Discovery Builder framework ETL (Extract, Transform, Load) is a reusable and schema-aligned component delivered with the Telecom Service Operations Management (TSOM) Core application. It provides a consistent and
extensible method for ingesting telecom inventory data into the ServiceNow Configuration Management Database (CMDB) across multiple Service Graph Connectors (SGCs).
The Telecom Discovery Builder framework ETL serves as a baseline data ingestion utility designed to handle telecom-specific configuration item (CI) data. It enables connector development teams to avoid building ETLs from scratch by
offering a standardized transform logic that can be duplicated and customized for each connector.
Once the TSOM Core plugin is activated, the generic ETL is auto-provisioned and becomes available in the IntegrationHub ETL Studio, ready to be reused and adapted to connector-specific needs.
## Why and when to use the Telecom Discovery Builder framework
Building ETL logic or transform maps from scratch for each new telecom connector can be time-consuming, error-prone, and inconsistent. The Telecom Discovery Builder framework streamlines the process by providing a standardized,
reusable foundation that ensures consistency across implementations.
Use the Telecom Discovery Builder framework when you want to:
* Deploy a new Service Graph Connector in a telecom environment and want to avoid building the ETL from scratch.
* Maintain schema-aligned consistency across multiple connectors and platform instances.
* Discovery payloads and CI relationships compliant with TNI (Telecom Network Inventory). For more information, see Telecommunications Network Inventory.
* Work within an SGC (Service Graph Connector) application scope and want to customize ETL behavior without modifying core logic.
* Benefit from predefined mappings, validated JSON schema support, and a UI-driven configuration interface.
## Key capabilities and features
* Auto-provisioned with TSOM core: Installs automatically and is ready to use across telecom connectors.
* Generic schema-based ingestion: Supports a unified data schema for telecom CIs.
* Supports duplication and customization: Duplicate the Telecom Discovery Builder framework ETL into your application scope using IntegrationHub ETL Studio.
* TNI support: Aligned to the TNI data model and the ETL logic can be extended to generate and link TNI entities.
* Flexible field mapping interface: Configure import sets, data sources, targets, and transformation logic through a UI-driven experience.
## Key benefits
Use Telecom Discovery Builder framework ETL to gain:
* Consistency in how telecom configuration items (CIs) are structured and loaded into the CMDB.
* Reusability through duplication and customization across connectors.
* Compliance with TNI schemas and discovery model requirements.
* Flexibility to extend and tailor data transformations without compromising the base schema.
| ---
title: Telecom Discovery Builder framework
description: The Telecom Discovery Builder framework ETL (Extract, Transform, Load)
is a reusable and schema-aligned component delivered with the Telecom Service Operations
Management (TSOM) Core application. It provides a consistent and extensible method
for ingesting telecom inventory data into the ServiceNow
keywords: []
breadcrumbs:
- Telecommunications Service Operations Management
- Exploring Telecommunications Service Operations Management
- Telecom Visibility
- Telecom Discovery
---
# Telecom Discovery Builder framework
The Telecom Discovery Builder framework ETL (Extract, Transform, Load) is a reusable and schema-aligned component delivered with the Telecom Service Operations Management (TSOM) Core application. It provides a consistent and
extensible method for ingesting telecom inventory data into the ServiceNow Configuration Management Database (CMDB) across multiple Service Graph Connectors (SGCs).
The Telecom Discovery Builder framework ETL serves as a baseline data ingestion utility designed to handle telecom-specific configuration item (CI) data. It enables connector development teams to avoid building ETLs from scratch by
offering a standardized transform logic that can be duplicated and customized for each connector.
Once the TSOM Core plugin is activated, the generic ETL is auto-provisioned and becomes available in the IntegrationHub ETL Studio, ready to be reused and adapted to connector-specific needs.
## Why and when to use the Telecom Discovery Builder framework
Building ETL logic or transform maps from scratch for each new telecom connector can be time-consuming, error-prone, and inconsistent. The Telecom Discovery Builder framework streamlines the process by providing a standardized,
reusable foundation that ensures consistency across implementations.
Use the Telecom Discovery Builder framework when you want to:
* Deploy a new Service Graph Connector in a telecom environment and want to avoid building the ETL from scratch.
* Maintain schema-aligned consistency across multiple connectors and platform instances.
* Discovery payloads and CI relationships compliant with TNI (Telecom Network Inventory). For more information, see Telecommunications Network Inventory.
* Work within an SGC (Service Graph Connector) application scope and want to customize ETL behavior without modifying core logic.
* Benefit from predefined mappings, validated JSON schema support, and a UI-driven configuration interface.
## Key capabilities and features
* Auto-provisioned with TSOM core: Installs automatically and is ready to use across telecom connectors.
* Generic schema-based ingestion: Supports a unified data schema for telecom CIs.
* Supports duplication and customization: Duplicate the Telecom Discovery Builder framework ETL into your application scope using IntegrationHub ETL Studio.
* TNI support: Aligned to the TNI data model and the ETL logic can be extended to generate and link TNI entities.
* Flexible field mapping interface: Configure import sets, data sources, targets, and transformation logic through a UI-driven experience.
## Key benefits
Use Telecom Discovery Builder framework ETL to gain:
* Consistency in how telecom configuration items (CIs) are structured and loaded into the CMDB.
* Reusability through duplication and customization across connectors.
* Compliance with TNI schemas and discovery model requirements.
* Flexibility to extend and tailor data transformations without compromising the base schema.
|
https://www.servicenow.com/docs/en-US/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/exploring-tsom.html | https://servicenow-be-prod.servicenow.com/api/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/exploring-tsom.html | 2025-08-02 | daily | 0.5 | 268.xml | en-US | zurich-telecom-service-ops | product/tmt-telecom-service-operations-mgt/concept/exploring-tsom.html | zurich | Exploring Telecommunications Service Operations Management | Learn how Telecommunications Service Operations Management (TSOM) empowers communication service providers (CSPs) proactively monitor, analyze, and resolve network and service issues before they impact customers. Built on the ServiceNow AI Platform, TSOM delivers a unified operations view across distributed, multi-domain | [] | [
"Telecommunications Service Operations Management"
] | <article class="hascomments" data-page="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/exploring-tsom.html" id="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/exploring-tsom.html"><body id="exploring-tsom"><main role="main"><article role="article" class="dita" id="exploring-tsom" aria-labelledby="title_exploring-tsom">
<h1 class="title topictitle1" id="title_exploring-tsom">Exploring <span class="ph">Telecommunications Service Operations Management</span></h1>
<div class="body conbody"><p class="shortdesc">Learn how <span class="ph">Telecommunications Service Operations Management</span> (TSOM) empowers communication service providers (CSPs) proactively monitor, analyze, and resolve network and service issues before they impact customers. Built on the <span class="ph">ServiceNow AI Platform</span>, TSOM delivers a unified operations view across distributed, multi-domain telecom environments, helping teams improve service availability, operational efficiency, and customer satisfaction.</p>
<p class="p"><span class="ph">Telecommunications Service Operations Management</span> is a solution for telecom providers that offers complete visibility into network and service health. TSOM collects, correlates, and prioritizes events from across network domains—such as
access, transport, and core—using standard APIs and the power of the <span class="ph">ServiceNow AI Platform</span>. By providing real-time, actionable insights, TSOM enables both frontline and back-office teams to address service-impacting issues and maintain consistent performance.</p>
<section class="section" id="exploring-tsom__section_rxm_5dj_tfc"><h2 id="d1313e58" class="title sectiontitle">How TSOM works</h2>
<div class="p"><span class="ph">Telecommunications Service Operations Management</span> simplifies telecom operations by connecting with existing monitoring and telemetry platforms, identifying actionable patterns, and automating resolution workflows. It leverages: <ul class="ul" id="exploring-tsom__ul_l4t_wdj_tfc">
<li class="li">External event management via Telecommunications API notifications for standardized alarm ingestion.</li>
<li class="li"><span class="ph">Event Management</span> for event correlation, suppression, and prioritization.</li>
<li class="li">Metric Intelligence to detect threshold breaches, performance degradation, and anomalous behavior in real time.</li>
<li class="li">Health Log Analytics to analyze log data, triage related issues, and identify root causes before users are impacted.</li>
<li class="li">Service Impact Analysis to assess and trace service disruptions based on impacted infrastructure and business services.</li>
<li class="li">Service Graph Connectors and Discovery to build a dynamic, telecom-aware CMDB.</li>
</ul></div>
</section>
<section class="section" id="exploring-tsom__section_ql1_cdk_b2c"><h2 id="d1313e91" class="title sectiontitle">TSOM Architecture and Telecom Applications</h2><img src="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/../images/architecture-telecom-applications.png?_LANG=enus" class="image" id="exploring-tsom__image_wzp_5dk_b2c" alt="TSOM architecture and telecom applications."/></section>
<section class="section" id="exploring-tsom__section_kbx_gdj_tfc"><h2 id="d1313e101" class="title sectiontitle">Key features</h2>
<div class="p">
<div class="table-wrap"><table count-columns="2" class="table" id="exploring-tsom__table_rcr_fdj_tfc"><caption><span class="table--title-label">Table 1. </span><span class="title">TSOM key capabilities</span></caption><colgroup><col/><col/></colgroup><thead class="thead">
<tr class="row">
<th class="entry" id="exploring-tsom__table_rcr_fdj_tfc__entry__1">Capability</th>
<th class="entry" id="exploring-tsom__table_rcr_fdj_tfc__entry__2">Description</th>
</tr>
</thead><tbody class="tbody">
<tr class="row">
<td class="entry" headers="exploring-tsom__table_rcr_fdj_tfc__entry__1">Real-time event monitoring</td>
<td class="entry" headers="exploring-tsom__table_rcr_fdj_tfc__entry__2">Ingest alarms and events from multi-domain network monitoring systems using External event management via Telecommunications API notifications.</td>
</tr>
<tr class="row">
<td class="entry" headers="exploring-tsom__table_rcr_fdj_tfc__entry__1">Event correlation & analysis</td>
<td class="entry" headers="exploring-tsom__table_rcr_fdj_tfc__entry__2">Leverage Event Management and Metric Intelligence to correlate related events, reduce noise, and detect anomalies. For more information, see <a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/concept//csh" href="https://servicenow-be-prod.servicenow.com/csh?topicname=event_open-api&version=zurich&pubname=zurich-api-reference" class="xref">Event Notification Management Open API</a>.</td>
</tr>
<tr class="row">
<td class="entry" headers="exploring-tsom__table_rcr_fdj_tfc__entry__1">Telecom Visibility</td>
<td class="entry" headers="exploring-tsom__table_rcr_fdj_tfc__entry__2">Gain end-to-end visualization of network and service health, including impact traceability.</td>
</tr>
<tr class="row">
<td class="entry" headers="exploring-tsom__table_rcr_fdj_tfc__entry__1">Service Impact Analysis</td>
<td class="entry" headers="exploring-tsom__table_rcr_fdj_tfc__entry__2">Understand how network or infrastructure issues affect services and prioritize remediation based on business impact.</td>
</tr>
<tr class="row">
<td class="entry" headers="exploring-tsom__table_rcr_fdj_tfc__entry__1">Metric Intelligence</td>
<td class="entry" headers="exploring-tsom__table_rcr_fdj_tfc__entry__2">Monitor performance trends, detect threshold breaches and anomalies in metrics to proactively identify issues. For more information, see <a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/concept//csh" href="https://servicenow-be-prod.servicenow.com/csh?topicname=operational-metrics&version=zurich&pubname=zurich-it-operations-management" class="xref">Metric Intelligence</a>.</td>
</tr>
<tr class="row">
<td class="entry" headers="exploring-tsom__table_rcr_fdj_tfc__entry__1">Health Log Analytics</td>
<td class="entry" headers="exploring-tsom__table_rcr_fdj_tfc__entry__2">The <span class="ph">ServiceNow</span> Health Log Analytics application helps prevent IT issues before your users are affected. It helps you identify the root cause of an issue by enabling you to triage related logs and
analyze the raw data. For more information, see <a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/concept//csh" href="https://servicenow-be-prod.servicenow.com/csh?topicname=hla-landing-page&version=zurich&pubname=zurich-it-operations-management" class="xref">Health Log Analytics</a></td>
</tr>
<tr class="row">
<td class="entry" headers="exploring-tsom__table_rcr_fdj_tfc__entry__1">Automated remediation</td>
<td class="entry" headers="exploring-tsom__table_rcr_fdj_tfc__entry__2">Use guided workflows and playbooks to drive fast, consistent, and auditable issue resolution.</td>
</tr>
<tr class="row">
<td class="entry" headers="exploring-tsom__table_rcr_fdj_tfc__entry__1">Telecom-aware CMDB</td>
<td class="entry" headers="exploring-tsom__table_rcr_fdj_tfc__entry__2">Link infrastructure, services, and physical/logical configuration items (CIs) using a telecom-specific model for accurate root cause analysis.</td>
</tr>
<tr class="row">
<td class="entry" headers="exploring-tsom__table_rcr_fdj_tfc__entry__1">Alert Management</td>
<td class="entry" headers="exploring-tsom__table_rcr_fdj_tfc__entry__2">Manage alerts efficiently with correlation, grouping, and automated response actions. For more information, see <a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/concept//csh" href="https://servicenow-be-prod.servicenow.com/csh?topicname=c_EMAlert&version=zurich&pubname=zurich-it-operations-management" class="xref">Manage and monitor alerts</a>.</td>
</tr>
</tbody></table></div>
</div>
</section>
<section class="section" id="exploring-tsom__section_x1j_p2j_tfc"><h2 id="d1313e238" class="title sectiontitle">Key benefits</h2>
<div class="p">
<ul class="ul" id="exploring-tsom__ul_jjq_q2j_tfc">
<li class="li">MTTD and MTTR reduction: Identify and respond to service-impacting issues before escalation.</li>
<li class="li">Improve operational efficiency: Noise reduction and streamline operations with guided workflows.</li>
<li class="li">Gain End-to-End Visibility: Understand how infrastructure issues impact customer-facing services.</li>
<li class="li">Integrate seamlessly: Ingest data from legacy and modern NMS/EMS tools with open standards.</li>
<li class="li">Ensure compliance: Align with TM Forum standards for telecom service assurance.</li>
</ul>
</div>
</section>
<section class="section" id="exploring-tsom__section_xty_drj_tfc"><h2 id="d1313e266" class="title sectiontitle">Key personas</h2>
<div class="p">
<ul class="ul" id="exploring-tsom__ul_pvt_dsj_tfc">
<li class="li">Network Operations Center (NOC) agents: Monitor network events and execute guided resolutions.</li>
<li class="li">Service Assurance managers: Analyze service trends and track resolution metrics.</li>
<li class="li">System Integrators / admins: Configure data ingestion, correlation rules, and workflows.</li>
<li class="li">Back-office analysts: Investigate root causes and track CI relationships in the CMDB.</li>
</ul>
</div>
</section>
<section class="section" id="exploring-tsom__section_pdc_4rj_tfc"><h2 id="d1313e290" class="title sectiontitle">Integration with the <span class="ph">ServiceNow AI Platform</span></h2>
<div class="p">TSOM is embedded into the Now Platform and integrates seamlessly with core capabilities such as: <ul class="ul" id="exploring-tsom__ul_c53_yrj_tfc">
<li class="li">Discovery</li>
<li class="li">Service Mapping</li>
<li class="li">CMDB</li>
<li class="li">Flow Designer and Playbooks</li>
</ul>This integration confirms consistent workflows, accurate service models, and unified operations management across telecom domains.</div>
</section>
</div>
<nav role="navigation"></nav><nav role="navigation" class="tasksNavigation"></nav><nav role="navigation" class="related-links"><div class="col-md-4"><dt>Related concepts</dt><dd><ul><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/concept/telecommunications-api-notification.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/telecommunications-api-notification.html" class="link" title="Use the Telecommunications API notification to receive the external events that occurring in the customer network system so that you can promptly respond to them in the ServiceNow.">External event management via Telecommunications API notifications</a></li><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/concept/tsom-visibility.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/tsom-visibility.html" class="link" title="Telecom Visibility extends the discovery and reconciliation capabilities of ITOM Visibility to meet the specific needs of telecom service providers. It enables accurate, telecom-aware network inventory by discovering real-time network data, reconciling mismatches, and maintaining a consistent telecom model in your CMDB and TNI (Telecommunications Network Inventory).">Telecom Visibility</a></li></ul></dd></div></nav>
</article></main></body></article> | {
"attachments": {
"all_attachments": null,
"topic_attachments": []
},
"available_languages": [
"enus"
],
"breadcrumbs": [
{
"title": "Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html"
}
],
"breadcrumbs_html": "<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops\">Zurich Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html\">Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<span class=\"active\">Exploring Telecommunications Service Operations Management</span>",
"bundle_id": "zurich-telecom-service-ops",
"bundle_key": 2733,
"bundle_landing_page": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html",
"bundle_subtitle": null,
"bundle_title": "Zurich Telecommunications Service Operations Management",
"canonical_link": null,
"dates": {
"Added on": "2025-08-02T00:48:08.794016Z",
"Created on": "2025-06-24T00:00:00Z",
"Initial upload": "2025-07-30T22:24:33.519043Z",
"Updated on": "2025-07-31T00:00:00Z"
},
"dislike_url": "https://servicenow-be-prod.servicenow.com/dislike/55686936",
"dislikes": 0,
"es_archived_content": false,
"is_in_fav": false,
"is_liked": null,
"is_watched": false,
"keywords": [
" zurich zurich"
],
"labels": [
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "zurich",
"navtitle": "Zurich",
"outputclasses": [],
"subjectHeadId": "versions",
"subjectheadNavtitle": "Versions",
"visibility": "show-facet"
},
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "tsom",
"navtitle": "Telecommunications Service Operations Management",
"outputclasses": [],
"subjectHeadId": "products",
"subjectheadNavtitle": "Products",
"visibility": "show-facet"
}
],
"labels_text": "Versions > Zurich; Products > CRM and Industry Products > Telecommunications Media and Technology Assurance > Telecommunications Service Operations Management",
"like_url": "https://servicenow-be-prod.servicenow.com/like/55686936",
"likes": 0,
"metadata": {
"AI Search": null,
"AI Search Assist": null,
"Application Insights": null,
"Capabilities": null,
"Code Signing": null,
"Contextual Search": null,
"DC.contributor": null,
"DC.coverage": null,
"DC.creator": "ServiceNow",
"DC.date.created": "2025-06-24T09:32:34+05:30",
"DC.date.modified": "2025-07-31",
"DC.format": "HTML5",
"DC.identifier": "exploring-tsom",
"DC.language": null,
"DC.relation": "telecommunications-api-notification.html",
"DC.rights.owner": "(C) Copyright 2025",
"DC.subject": null,
"DC.type": "concept",
"Data Discovery": null,
"Data Policy": null,
"Data Privacy": null,
"Discovery": null,
"External Content for AI Search": null,
"Field Administration": null,
"Field Normalization": null,
"Key Management Framework": null,
"Localization Framework": null,
"Now Platform": null,
"PlatSec": null,
"Platform": null,
"Platform Administration": null,
"Platform Performance": null,
"Platform Privacy": null,
"Proactive Triggers": null,
"Process Optimization": null,
"RN doc editing record number": null,
"Search Administration": null,
"Secrets Management": null,
"ServiceNow AI Platform": null,
"State Model": null,
"Subscription Management": null,
"Task Communications Management": null,
"Timeline Visualizations": null,
"User Administration": null,
"User Experience Analytics": null,
"Zing": null,
"ai-now-assist": null,
"app-name": null,
"app_route": null,
"azureapimanagemen": null,
"change-completed": null,
"change-item": null,
"change-request-id": null,
"change-request-reference": null,
"com.glide.embedded_help.category": null,
"component": null,
"copyright": "(C) Copyright 2025",
"crossroads": null,
"data": null,
"description": "Learn how Telecommunications Service Operations Management (TSOM) empowers communication service providers (CSPs) proactively monitor, analyze, and resolve network and service issues before they impact customers. Built on the ServiceNow AI Platform, TSOM delivers a unified operations view across distributed, multi-domain",
"dominant_bundle": null,
"erp-canvas-video": null,
"fsm-mobile": null,
"fsm-route": null,
"fsm-sched-opt": null,
"fsm-wrk-order": null,
"genai-round-7": null,
"generator": "DITA-OT",
"glossPartOfSpeech": null,
"glossStatus": null,
"guided setup": null,
"guided tours": null,
"keywords": null,
"min-toc": null,
"mini": null,
"mini-to truec": null,
"mini-toc": "yes",
"mini_toc": null,
"minitoc": null,
"modification": null,
"now-assist-app-gen-video": null,
"order": null,
"page-type": null,
"page-type ": null,
"prodname": null,
"product": null,
"product_name": null,
"release": null,
"resourceID": null,
"roles": null,
"route_page": null,
"route_params_listId": null,
"route_params_table": null,
"route_params_type": null,
"route_type": null,
"setconfigurationproperties": null,
"topic": null,
"translation-type": "source",
"version": null,
"workflow": "Customer and Industry",
"workplace-srvc-delvry-ditamap": null
},
"page_id": "product/tmt-telecom-service-operations-mgt/concept/exploring-tsom.html",
"page_key": 55686936,
"preprocessed_PDF": "https://downloads.docs.servicenow.com/pdf/enus/servicenow-zurich-telecom-service-ops-enus.pdf",
"rating": null,
"read_time_data": {
"char_count": 4586,
"img_count": 1,
"read_time": 3,
"video_links": [
""
],
"word_count": 588
},
"related_links": [
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "Use the Telecommunications API notification to receive the external events that occurring in the customer network system so that you can promptly respond to them in the ServiceNow.",
"title": "External event management via Telecommunications API notifications",
"topic": "/product/tmt-telecom-service-operations-mgt/concept/telecommunications-api-notification.html",
"type": "concept",
"url": null
},
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "Telecom Visibility extends the discovery and reconciliation capabilities of ITOM Visibility to meet the specific needs of telecom service providers. It enables accurate, telecom-aware network inventory by discovering real-time network data, reconciling mismatches, and maintaining a consistent telecom model in your CMDB and TNI (Telecommunications Network Inventory).",
"title": "Telecom Visibility",
"topic": "/product/tmt-telecom-service-operations-mgt/concept/tsom-visibility.html",
"type": "concept",
"url": null
}
],
"search_title": null,
"title": "Exploring Telecommunications Service Operations Management",
"topic_cluster": {
"clustered_by": {
"enabled": true,
"primary_key": "versions",
"primary_sort": "top-down",
"type": "subjecthead"
},
"clustered_labels": [
"versions"
],
"clustered_topics": [],
"clustering_title": "Zurich"
},
"topic_html": "<article class=\"hascomments\" data-page=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/exploring-tsom.html\" id=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/exploring-tsom.html\"><body id=\"exploring-tsom\"><main role=\"main\"><article role=\"article\" class=\"dita\" id=\"exploring-tsom\" aria-labelledby=\"title_exploring-tsom\">\n <h1 class=\"title topictitle1\" id=\"title_exploring-tsom\">Exploring <span class=\"ph\">Telecommunications Service Operations Management</span></h1>\n \n \n <div class=\"body conbody\"><p class=\"shortdesc\">Learn how <span class=\"ph\">Telecommunications Service Operations Management</span> (TSOM) empowers communication service providers (CSPs) proactively monitor, analyze, and resolve network and service issues before they impact customers. Built on the <span class=\"ph\">ServiceNow AI Platform</span>, TSOM delivers a unified operations view across distributed, multi-domain telecom environments, helping teams improve service availability, operational efficiency, and customer satisfaction.</p>\n <p class=\"p\"><span class=\"ph\">Telecommunications Service Operations Management</span> is a solution for telecom providers that offers complete visibility into network and service health. TSOM collects, correlates, and prioritizes events from across network domains—such as\n access, transport, and core—using standard APIs and the power of the <span class=\"ph\">ServiceNow AI Platform</span>. By providing real-time, actionable insights, TSOM enables both frontline and back-office teams to address service-impacting issues and maintain consistent performance.</p>\n <section class=\"section\" id=\"exploring-tsom__section_rxm_5dj_tfc\"><h2 id=\"d1313e58\" class=\"title sectiontitle\">How TSOM works</h2>\n \n <div class=\"p\"><span class=\"ph\">Telecommunications Service Operations Management</span> simplifies telecom operations by connecting with existing monitoring and telemetry platforms, identifying actionable patterns, and automating resolution workflows. It leverages: <ul class=\"ul\" id=\"exploring-tsom__ul_l4t_wdj_tfc\">\n <li class=\"li\">External event management via Telecommunications API notifications for standardized alarm ingestion.</li>\n <li class=\"li\"><span class=\"ph\">Event Management</span> for event correlation, suppression, and prioritization.</li>\n <li class=\"li\">Metric Intelligence to detect threshold breaches, performance degradation, and anomalous behavior in real time.</li>\n <li class=\"li\">Health Log Analytics to analyze log data, triage related issues, and identify root causes before users are impacted.</li>\n <li class=\"li\">Service Impact Analysis to assess and trace service disruptions based on impacted infrastructure and business services.</li>\n <li class=\"li\">Service Graph Connectors and Discovery to build a dynamic, telecom-aware CMDB.</li>\n </ul></div>\n </section>\n <section class=\"section\" id=\"exploring-tsom__section_ql1_cdk_b2c\"><h2 id=\"d1313e91\" class=\"title sectiontitle\">TSOM Architecture and Telecom Applications</h2><img src=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/../images/architecture-telecom-applications.png?_LANG=enus\" class=\"image\" id=\"exploring-tsom__image_wzp_5dk_b2c\" alt=\"TSOM architecture and telecom applications.\"/></section>\n <section class=\"section\" id=\"exploring-tsom__section_kbx_gdj_tfc\"><h2 id=\"d1313e101\" class=\"title sectiontitle\">Key features</h2>\n \n <div class=\"p\">\n <div class=\"table-wrap\"><table count-columns=\"2\" class=\"table\" id=\"exploring-tsom__table_rcr_fdj_tfc\"><caption><span class=\"table--title-label\">Table 1. </span><span class=\"title\">TSOM key capabilities</span></caption><colgroup><col/><col/></colgroup><thead class=\"thead\">\n <tr class=\"row\">\n <th class=\"entry\" id=\"exploring-tsom__table_rcr_fdj_tfc__entry__1\">Capability</th>\n <th class=\"entry\" id=\"exploring-tsom__table_rcr_fdj_tfc__entry__2\">Description</th>\n </tr>\n </thead><tbody class=\"tbody\">\n <tr class=\"row\">\n <td class=\"entry\" headers=\"exploring-tsom__table_rcr_fdj_tfc__entry__1\">Real-time event monitoring</td>\n <td class=\"entry\" headers=\"exploring-tsom__table_rcr_fdj_tfc__entry__2\">Ingest alarms and events from multi-domain network monitoring systems using External event management via Telecommunications API notifications.</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry\" headers=\"exploring-tsom__table_rcr_fdj_tfc__entry__1\">Event correlation & analysis</td>\n <td class=\"entry\" headers=\"exploring-tsom__table_rcr_fdj_tfc__entry__2\">Leverage Event Management and Metric Intelligence to correlate related events, reduce noise, and detect anomalies. For more information, see <a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept//csh\" href=\"https://servicenow-be-prod.servicenow.com/csh?topicname=event_open-api&version=zurich&pubname=zurich-api-reference\" class=\"xref\">Event Notification Management Open API</a>.</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry\" headers=\"exploring-tsom__table_rcr_fdj_tfc__entry__1\">Telecom Visibility</td>\n <td class=\"entry\" headers=\"exploring-tsom__table_rcr_fdj_tfc__entry__2\">Gain end-to-end visualization of network and service health, including impact traceability.</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry\" headers=\"exploring-tsom__table_rcr_fdj_tfc__entry__1\">Service Impact Analysis</td>\n <td class=\"entry\" headers=\"exploring-tsom__table_rcr_fdj_tfc__entry__2\">Understand how network or infrastructure issues affect services and prioritize remediation based on business impact.</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry\" headers=\"exploring-tsom__table_rcr_fdj_tfc__entry__1\">Metric Intelligence</td>\n <td class=\"entry\" headers=\"exploring-tsom__table_rcr_fdj_tfc__entry__2\">Monitor performance trends, detect threshold breaches and anomalies in metrics to proactively identify issues. For more information, see <a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept//csh\" href=\"https://servicenow-be-prod.servicenow.com/csh?topicname=operational-metrics&version=zurich&pubname=zurich-it-operations-management\" class=\"xref\">Metric Intelligence</a>.</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry\" headers=\"exploring-tsom__table_rcr_fdj_tfc__entry__1\">Health Log Analytics</td>\n <td class=\"entry\" headers=\"exploring-tsom__table_rcr_fdj_tfc__entry__2\">The <span class=\"ph\">ServiceNow</span> Health Log Analytics application helps prevent IT issues before your users are affected. It helps you identify the root cause of an issue by enabling you to triage related logs and\n analyze the raw data. For more information, see <a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept//csh\" href=\"https://servicenow-be-prod.servicenow.com/csh?topicname=hla-landing-page&version=zurich&pubname=zurich-it-operations-management\" class=\"xref\">Health Log Analytics</a></td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry\" headers=\"exploring-tsom__table_rcr_fdj_tfc__entry__1\">Automated remediation</td>\n <td class=\"entry\" headers=\"exploring-tsom__table_rcr_fdj_tfc__entry__2\">Use guided workflows and playbooks to drive fast, consistent, and auditable issue resolution.</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry\" headers=\"exploring-tsom__table_rcr_fdj_tfc__entry__1\">Telecom-aware CMDB</td>\n <td class=\"entry\" headers=\"exploring-tsom__table_rcr_fdj_tfc__entry__2\">Link infrastructure, services, and physical/logical configuration items (CIs) using a telecom-specific model for accurate root cause analysis.</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry\" headers=\"exploring-tsom__table_rcr_fdj_tfc__entry__1\">Alert Management</td>\n <td class=\"entry\" headers=\"exploring-tsom__table_rcr_fdj_tfc__entry__2\">Manage alerts efficiently with correlation, grouping, and automated response actions. For more information, see <a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept//csh\" href=\"https://servicenow-be-prod.servicenow.com/csh?topicname=c_EMAlert&version=zurich&pubname=zurich-it-operations-management\" class=\"xref\">Manage and monitor alerts</a>.</td>\n </tr>\n </tbody></table></div>\n </div>\n </section>\n <section class=\"section\" id=\"exploring-tsom__section_x1j_p2j_tfc\"><h2 id=\"d1313e238\" class=\"title sectiontitle\">Key benefits</h2>\n \n <div class=\"p\">\n <ul class=\"ul\" id=\"exploring-tsom__ul_jjq_q2j_tfc\">\n <li class=\"li\">MTTD and MTTR reduction: Identify and respond to service-impacting issues before escalation.</li>\n <li class=\"li\">Improve operational efficiency: Noise reduction and streamline operations with guided workflows.</li>\n <li class=\"li\">Gain End-to-End Visibility: Understand how infrastructure issues impact customer-facing services.</li>\n <li class=\"li\">Integrate seamlessly: Ingest data from legacy and modern NMS/EMS tools with open standards.</li>\n <li class=\"li\">Ensure compliance: Align with TM Forum standards for telecom service assurance.</li>\n </ul>\n </div>\n </section>\n <section class=\"section\" id=\"exploring-tsom__section_xty_drj_tfc\"><h2 id=\"d1313e266\" class=\"title sectiontitle\">Key personas</h2>\n \n <div class=\"p\">\n <ul class=\"ul\" id=\"exploring-tsom__ul_pvt_dsj_tfc\">\n <li class=\"li\">Network Operations Center (NOC) agents: Monitor network events and execute guided resolutions.</li>\n <li class=\"li\">Service Assurance managers: Analyze service trends and track resolution metrics.</li>\n <li class=\"li\">System Integrators / admins: Configure data ingestion, correlation rules, and workflows.</li>\n <li class=\"li\">Back-office analysts: Investigate root causes and track CI relationships in the CMDB.</li>\n </ul>\n </div>\n </section>\n <section class=\"section\" id=\"exploring-tsom__section_pdc_4rj_tfc\"><h2 id=\"d1313e290\" class=\"title sectiontitle\">Integration with the <span class=\"ph\">ServiceNow AI Platform</span></h2>\n \n <div class=\"p\">TSOM is embedded into the Now Platform and integrates seamlessly with core capabilities such as: <ul class=\"ul\" id=\"exploring-tsom__ul_c53_yrj_tfc\">\n <li class=\"li\">Discovery</li>\n <li class=\"li\">Service Mapping</li>\n <li class=\"li\">CMDB</li>\n <li class=\"li\">Flow Designer and Playbooks</li>\n </ul>This integration confirms consistent workflows, accurate service models, and unified operations management across telecom domains.</div>\n </section>\n </div>\n <nav role=\"navigation\"></nav><nav role=\"navigation\" class=\"tasksNavigation\"></nav><nav role=\"navigation\" class=\"related-links\"><div class=\"col-md-4\"><dt>Related concepts</dt><dd><ul><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept/telecommunications-api-notification.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/telecommunications-api-notification.html\" class=\"link\" title=\"Use the Telecommunications API notification to receive the external events that occurring in the customer network system so that you can promptly respond to them in the ServiceNow.\">External event management via Telecommunications API notifications</a></li><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept/tsom-visibility.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/tsom-visibility.html\" class=\"link\" title=\"Telecom Visibility extends the discovery and reconciliation capabilities of ITOM Visibility to meet the specific needs of telecom service providers. It enables accurate, telecom-aware network inventory by discovering real-time network data, reconciling mismatches, and maintaining a consistent telecom model in your CMDB and TNI (Telecommunications Network Inventory).\">Telecom Visibility</a></li></ul></dd></div></nav>\n</article></main></body></article>",
"topic_language": "enus",
"views": 0,
"your_rating": null
} | # Exploring Telecommunications Service Operations Management
Learn how Telecommunications Service Operations Management (TSOM) empowers communication service providers (CSPs) proactively monitor, analyze, and resolve network and service issues before they impact customers. Built on the ServiceNow AI Platform, TSOM delivers a unified operations view across distributed, multi-domain telecom environments, helping teams improve service availability, operational efficiency, and customer satisfaction.
Telecommunications Service Operations Management is a solution for telecom providers that offers complete visibility into network and service health. TSOM collects, correlates, and prioritizes events from across network domains—such as
access, transport, and core—using standard APIs and the power of the ServiceNow AI Platform. By providing real-time, actionable insights, TSOM enables both frontline and back-office teams to address service-impacting issues and maintain consistent performance.
## How TSOM works
Telecommunications Service Operations Management simplifies telecom operations by connecting with existing monitoring and telemetry platforms, identifying actionable patterns, and automating resolution workflows. It leverages:
* External event management via Telecommunications API notifications for standardized alarm ingestion.
* Event Management for event correlation, suppression, and prioritization.
* Metric Intelligence to detect threshold breaches, performance degradation, and anomalous behavior in real time.
* Health Log Analytics to analyze log data, triage related issues, and identify root causes before users are impacted.
* Service Impact Analysis to assess and trace service disruptions based on impacted infrastructure and business services.
* Service Graph Connectors and Discovery to build a dynamic, telecom-aware CMDB.
## TSOM Architecture and Telecom Applications
## Key features
Table 1. TSOM key capabilities
| Capability | Description |
| --- | --- |
| Real-time event monitoring | Ingest alarms and events from multi-domain network monitoring systems using External event management via Telecommunications API notifications. |
| Event correlation & analysis | Leverage Event Management and Metric Intelligence to correlate related events, reduce noise, and detect anomalies. For more information, see Event Notification Management Open API. |
| Telecom Visibility | Gain end-to-end visualization of network and service health, including impact traceability. |
| Service Impact Analysis | Understand how network or infrastructure issues affect services and prioritize remediation based on business impact. |
| Metric Intelligence | Monitor performance trends, detect threshold breaches and anomalies in metrics to proactively identify issues. For more information, see Metric Intelligence. |
| Health Log Analytics | The ServiceNow Health Log Analytics application helps prevent IT issues before your users are affected. It helps you identify the root cause of an issue by enabling you to triage related logs and analyze the raw data. For more information, see Health Log Analytics |
| Automated remediation | Use guided workflows and playbooks to drive fast, consistent, and auditable issue resolution. |
| Telecom-aware CMDB | Link infrastructure, services, and physical/logical configuration items (CIs) using a telecom-specific model for accurate root cause analysis. |
| Alert Management | Manage alerts efficiently with correlation, grouping, and automated response actions. For more information, see Manage and monitor alerts. |
## Key benefits
* MTTD and MTTR reduction: Identify and respond to service-impacting issues before escalation.
* Improve operational efficiency: Noise reduction and streamline operations with guided workflows.
* Gain End-to-End Visibility: Understand how infrastructure issues impact customer-facing services.
* Integrate seamlessly: Ingest data from legacy and modern NMS/EMS tools with open standards.
* Ensure compliance: Align with TM Forum standards for telecom service assurance.
## Key personas
* Network Operations Center (NOC) agents: Monitor network events and execute guided resolutions.
* Service Assurance managers: Analyze service trends and track resolution metrics.
* System Integrators / admins: Configure data ingestion, correlation rules, and workflows.
* Back-office analysts: Investigate root causes and track CI relationships in the CMDB.
## Integration with the ServiceNow AI Platform
TSOM is embedded into the Now Platform and integrates seamlessly with core capabilities such as:
* Discovery
* Service Mapping
* CMDB
* Flow Designer and Playbooks
This integration confirms consistent workflows, accurate service models, and unified operations management across telecom domains.
| ---
title: Exploring Telecommunications Service Operations Management
description: Learn how Telecommunications Service Operations Management (TSOM) empowers
communication service providers (CSPs) proactively monitor, analyze, and resolve
network and service issues before they impact customers. Built on the ServiceNow
AI Platform, TSOM delivers a unified operations view across distributed, multi-domain
keywords: []
breadcrumbs:
- Telecommunications Service Operations Management
---
# Exploring Telecommunications Service Operations Management
Learn how Telecommunications Service Operations Management (TSOM) empowers communication service providers (CSPs) proactively monitor, analyze, and resolve network and service issues before they impact customers. Built on the ServiceNow AI Platform, TSOM delivers a unified operations view across distributed, multi-domain telecom environments, helping teams improve service availability, operational efficiency, and customer satisfaction.
Telecommunications Service Operations Management is a solution for telecom providers that offers complete visibility into network and service health. TSOM collects, correlates, and prioritizes events from across network domains—such as
access, transport, and core—using standard APIs and the power of the ServiceNow AI Platform. By providing real-time, actionable insights, TSOM enables both frontline and back-office teams to address service-impacting issues and maintain consistent performance.
## How TSOM works
Telecommunications Service Operations Management simplifies telecom operations by connecting with existing monitoring and telemetry platforms, identifying actionable patterns, and automating resolution workflows. It leverages:
* External event management via Telecommunications API notifications for standardized alarm ingestion.
* Event Management for event correlation, suppression, and prioritization.
* Metric Intelligence to detect threshold breaches, performance degradation, and anomalous behavior in real time.
* Health Log Analytics to analyze log data, triage related issues, and identify root causes before users are impacted.
* Service Impact Analysis to assess and trace service disruptions based on impacted infrastructure and business services.
* Service Graph Connectors and Discovery to build a dynamic, telecom-aware CMDB.
## TSOM Architecture and Telecom Applications
## Key features
Table 1. TSOM key capabilities
| Capability | Description |
| --- | --- |
| Real-time event monitoring | Ingest alarms and events from multi-domain network monitoring systems using External event management via Telecommunications API notifications. |
| Event correlation & analysis | Leverage Event Management and Metric Intelligence to correlate related events, reduce noise, and detect anomalies. For more information, see Event Notification Management Open API. |
| Telecom Visibility | Gain end-to-end visualization of network and service health, including impact traceability. |
| Service Impact Analysis | Understand how network or infrastructure issues affect services and prioritize remediation based on business impact. |
| Metric Intelligence | Monitor performance trends, detect threshold breaches and anomalies in metrics to proactively identify issues. For more information, see Metric Intelligence. |
| Health Log Analytics | The ServiceNow Health Log Analytics application helps prevent IT issues before your users are affected. It helps you identify the root cause of an issue by enabling you to triage related logs and analyze the raw data. For more information, see Health Log Analytics |
| Automated remediation | Use guided workflows and playbooks to drive fast, consistent, and auditable issue resolution. |
| Telecom-aware CMDB | Link infrastructure, services, and physical/logical configuration items (CIs) using a telecom-specific model for accurate root cause analysis. |
| Alert Management | Manage alerts efficiently with correlation, grouping, and automated response actions. For more information, see Manage and monitor alerts. |
## Key benefits
* MTTD and MTTR reduction: Identify and respond to service-impacting issues before escalation.
* Improve operational efficiency: Noise reduction and streamline operations with guided workflows.
* Gain End-to-End Visibility: Understand how infrastructure issues impact customer-facing services.
* Integrate seamlessly: Ingest data from legacy and modern NMS/EMS tools with open standards.
* Ensure compliance: Align with TM Forum standards for telecom service assurance.
## Key personas
* Network Operations Center (NOC) agents: Monitor network events and execute guided resolutions.
* Service Assurance managers: Analyze service trends and track resolution metrics.
* System Integrators / admins: Configure data ingestion, correlation rules, and workflows.
* Back-office analysts: Investigate root causes and track CI relationships in the CMDB.
## Integration with the ServiceNow AI Platform
TSOM is embedded into the Now Platform and integrates seamlessly with core capabilities such as:
* Discovery
* Service Mapping
* CMDB
* Flow Designer and Playbooks
This integration confirms consistent workflows, accurate service models, and unified operations management across telecom domains.
|
https://www.servicenow.com/docs/en-US/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/overview-of-standardized-json-common-data-set.html | https://servicenow-be-prod.servicenow.com/api/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/overview-of-standardized-json-common-data-set.html | 2025-08-02 | daily | 0.5 | 268.xml | en-US | zurich-telecom-service-ops | product/tmt-telecom-service-operations-mgt/concept/overview-of-standardized-json-common-data-set.html | zurich | Standardized JSON common data set to support all service graph connectors | Use the TSOM architecture to support standardized Service Graph Connectors using a unified schema and reusable ETL logic. This reduces onboarding time for new connectors and simplifies integration with CMDB. | [] | [
"Telecommunications Service Operations Management",
"Configuring Telecommunications Service Operations Management",
"Set up Telecom Visibility",
"Configuring the Telecom Discovery Builder framework ETL in a connector"
] | <article class="hascomments" data-page="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/overview-of-standardized-json-common-data-set.html" id="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/overview-of-standardized-json-common-data-set.html"><body id="overview-of-standardized-json-common-data-set"><main role="main"><article role="article" class="dita" id="overview-of-standardized-json-common-data-set" aria-labelledby="title_overview-of-standardized-json-common-data-set">
<h1 class="title topictitle1" id="title_overview-of-standardized-json-common-data-set">Standardized JSON common data set to support all service graph connectors</h1>
<div class="body conbody"><p class="shortdesc">Use the TSOM architecture to support standardized Service Graph Connectors using a unified schema and reusable ETL logic. This reduces onboarding time for new connectors and simplifies integration with CMDB.</p>
<section class="section" id="overview-of-standardized-json-common-data-set__section_phm_y1g_1gc"><h2 id="d3684e42" class="title sectiontitle">1. Define the common JSON Schema</h2>
<p class="p">Standardize the output of all service graph connectors to align with a single JSON format that conforms to the TNI schema.</p>
<div class="p">Ensure the following points:<ol class="ol" id="overview-of-standardized-json-common-data-set__ol_gqd_1bg_1gc">
<li class="li">Implement conversion logic in the collector or adaptor to output data in the common schema.</li>
<li class="li">Ensure:<ul class="ul" id="overview-of-standardized-json-common-data-set__ul_hqd_1bg_1gc">
<li class="li">Slot-on-slot or card-on-card hierarchies are excluded.</li>
<li class="li">Logical interfaces are clearly marked with <code class="ph codeph">virtual=true</code>.</li>
<li class="li">Equipment types align to model-class mappings.</li>
</ul></li>
</ol></div>
<div class="note note note_note"><span class="note__title">Note:</span> The schema should support runtime adaptability to TNI changes if available.</div>
<p class="p">The following is the JSON schema common data set that supports all TSOM service graph connectors:</p>
<div class="p">
<pre class="prettyprint language-plaintext"><code class="pre codeblock language-plaintext">{
"$schema": "http://json-schema.org/draft-07/schema#",
"title": "Telco Generic Schema",
"version": "2.0.1",
"oneOf": [
{
"type": "object",
"properties": {
"logical_composites": {
"type": "array",
"items": {
"$ref": "#/$defs/logical_composite"
}
}
},
"required": [
"logical_composites"
],
"additionalProperties": false
},
{
"type": "object",
"properties": {
"devices": {
"type": "array",
"items": {
"$ref": "#/$defs/device"
}
}
},
"required": [
"devices"
],
"additionalProperties": false
},
{
"type": "object",
"properties": {
"logical_connections": {
"type": "array",
"items": {
"$ref": "#/$defs/logical_connection"
}
}
},
"required": [
"logical_connections"
],
"additionalProperties": false
},
{
"type": "object",
"properties": {
"port_relations": {
"type": "array",
"items": {
"$ref": "#/$defs/port_relation"
}
}
},
"required": [
"port_relations"
],
"additionalProperties": false
},
{
"type": "object",
"properties": {
"logical_connection_relations": {
"type": "array",
"items": {
"$ref": "#/$defs/logical_connection_relation"
}
}
},
"required": [
"logical_connection_relations"
],
"additionalProperties": false
},
{
"type": "object",
"properties": {
"numbers": {
"type": "array",
"items": {
"$ref": "#/$defs/number"
}
}
},
"required": [
"numbers"
],
"additionalProperties": false
},
{
"type": "object",
"properties": {
"topologies": {
"type": "array",
"items": {
"$ref": "#/$defs/network_topology"
}
}
},
"required": [
"topologies"
],
"additionalProperties": false
},
{
"type": "object",
"properties": {
"topology_relations": {
"type": "array",
"items": {
"$ref": "#/$defs/network_topology_relation"
}
}
},
"required": [
"topology_relations"
],
"additionalProperties": false
}
],
"$defs": {
"keyRef": {
"type": "object",
"properties": { "key": { "type": "string" }
},
"required": [ "key" ],
"additionalProperties": false
},
"optionalKeyRef": { "type": [ "object", "null" ],
"properties": {
"key": { "type": "string" }
},
"additionalProperties": false
},
"value": {
"type": "object",
"properties": {
"from": { "type": [ "integer" ], "default": 0, "minimum": 0 },
"to": { "type": [ "integer" ], "default": 0, "minimum": 0 }
},
"required": [ "from", "to" ],
"additionalProperties": false
},
"logical_composite": {
"type": "object",
"properties": {
"class": { "type": "string", "enum": [ "logical_composite" ] },
"key": { "type": "string" },
"name": { "type": [ "string", "null" ] },
"description": { "type": [ "string", "null" ] },
"devices": { "type": "array", "items": { "$ref": "#/$defs/keyRef" } },
"power_units": { "type": "array", "items": { "$ref": "#/$defs/pdu" } },
"fan_shelves": { "type": "array", "items": { "$ref": "#/$defs/fan_shelf" } } },
"required": [ "key", "name" ]
},
"pdu": {
"type": "object",
"properties": {
"class": { "type": "string", "enum": [ "pdu" ] },
"key": { "type": "string" },
"name": { "type": [ "string", "null" ] },
"description": { "type": [ "string", "null" ] },
"model_name": { "type": [ "string", "null" ] },
"model_number": { "type": [ "string", "null" ] },
"unit_position": { "type": [ "integer", "null" ], "minimum": 1 },
"slots": { "type": "array", "items": { "$ref": "#/$defs/slot" } }
},
"required": [ "key", "name" ]
},
"fan_shelf": {
"type": "object",
"properties": {
"class": { "type": "string", "enum": [ "fan_shelf" ] },
"key": { "type": "string" },
"name": { "type": [ "string", "null" ] },
"description": { "type": [ "string", "null" ] },
"slots": { "type": "array", "items": { "$ref": "#/$defs/slot" } }
},
"required": [ "key", "name" ]
},
"device": {
"type": "object",
"properties": {
"class": { "type": "string", "enum": [ "device" ] },
"key": { "type": "string" },
"name": { "type": [ "string", "null" ] },
"description": { "type": [ "string", "null" ] },
"ip_address": { "type": [ "string", "null" ] },
"mac_address": { "type": [ "string", "null" ] },
"serial_number": { "type": [ "string", "null" ] },
"model_name": { "type": [ "string", "null" ] },
"model_number": { "type": [ "string", "null" ] },
"manufacturer": { "type": [ "string", "null" ] },
"firmware_version": { "type": [ "string", "null" ] },
"slots": { "type": "array", "items": { "$ref": "#/$defs/slot" } },
"ports": { "type": "array", "items": { "$ref": "#/$defs/port" } } },
"required": [ "key", "name", "serial_number" ]
},
"slot": {
"type": "object",
"properties": {
"class": { "type": "string", "enum": [ "slot" ] },
"key": { "type": "string" },
"name": { "type": [ "string", "null" ] },
"description": { "type": [ "string", "null" ] },
"model_name": { "type": [ "string", "null" ] },
"model_number": { "type": [ "string", "null" ] },
"manufacturer": { "type": [ "string", "null" ] },
"unit_position": { "type": [ "integer", "null" ], "minimum": 1 },
"cards": { "type": "array", "items": { "$ref": "#/$defs/card" } }
},
"required": [ "key", "name" ]
},
"card": {
"type": "object",
"properties": {
"class": { "type": "string", "enum": [ "card" ] },
"key": { "type": "string" },
"name": { "type": [ "string", "null" ] },
"description": { "type": [ "string", "null" ] },
"mac_address": { "type": [ "string", "null" ] },
"serial_number": { "type": [ "string", "null" ] },
"firmware_version": { "type": [ "string", "null" ] },
"model_name": { "type": [ "string", "null" ] },
"model_number": { "type": [ "string", "null" ] },
"manufacturer": { "type": [ "string", "null" ] },
"unit_position": { "type": [ "integer", "null" ], "minimum": 1 },
"slots": { "type": "array", "items": { "$ref": "#/$defs/slot" } },
"ports": { "type": "array", "items": { "$ref": "#/$defs/port" } }
},
"required": [ "key", "name" ]
},
"port": {
"type": "object",
"properties": {
"class": { "type": "string", "enum": [ "port" ] },
"key": { "type": "string" },
"name": { "type": [ "string", "null" ] },
"description": { "type": [ "string", "null" ] },
"model_name": { "type": [ "string", "null" ] },
"ip_address": { "type": [ "string", "null" ] },
"virtual": { "type": "boolean", "default": false },
"unit_position": { "type": [ "integer", "null" ], "minimum": 1 },
"bandwidth_name": { "type": [ "string", "null" ] },
"bandwidth_group": { "type": [ "string", "null" ] },
"bandwidth": { "type": [ "integer", "null" ], "minimum": 0 },
"mtu_size": { "type": [ "integer", "null" ], "minimum": 0 }
},
"required": [ "key", "name" ]
},
"number": {
"type": "object",
"properties": {
"class": { "type": "string", "enum": [ "number" ] },
"key": { "type": "string" },
"name": { "type": [ "string", "null" ] },
"related_ci_type": { "type": "string", "enum": [ "Network Interface", "Physical Connection", "Logical Connection", "Equipment", "Topology" ] },
"related_ci": { "$ref": "#/$defs/keyRef" },
"type": { "type": "string", "enum": [ "vlan_range", "vlan_subrange", "vlan", "lag_range", "lag" ] },
"vlan_type": { "type": "string", "enum": [ "inner", "outer" ] },
"value": { "$ref": "#/$defs/value" }
},
"required": [ "key", "name", "type", "related_ci_type", "related_ci", "value" ] },
"logical_connection": {
"type": "object",
"properties": {
"class": { "type": "string", "enum": [ "logical_connection" ] },
"key": { "type": "string" },
"name": { "type": [ "string", "null" ] },
"description": { "type": [ "string", "null" ] },
"model_name": { "type": [ "string", "null" ] },
"bandwidth_group": { "type": [ "string", "null" ] },
"bandwidth_name_a_to_z": { "type": [ "string", "null" ] },
"bandwidth_name_z_to_a": { "type": [ "string", "null" ] },
"bandwidth_a_to_z": { "type": [ "integer", "null" ], "minimum": 0 },
"bandwidth_z_to_a": { "type": [ "integer", "null" ], "minimum": 0 },
"equipment_a": { "$ref": "#/$defs/optionalKeyRef" },
"equipment_z": { "$ref": "#/$defs/optionalKeyRef" },
"port_a": { "$ref": "#/$defs/keyRef" },
"port_z": { "$ref": "#/$defs/keyRef" }
},
"required": [ "key", "name", "equipment_a", "equipment_z", "port_a", "port_z" ]
},
"port_relation": {
"type": "object",
"properties": {
"class": { "type": "string", "enum": [ "port_relation" ] },
"parent": { "$ref": "#/$defs/keyRef" },
"child": { "$ref": "#/$defs/keyRef" }
},
"required": [ "parent", "child" ]
},
"logical_connection_relation": {
"type": "object",
"properties": {
"class": { "type": "string", "enum": [ "logical_connection_relation" ] },
"sequence": { "type": [ "integer", "null" ], "minimum": 1 },
"route": { "type": [ "integer", "null" ], "minimum": 1 },
"parent": { "$ref": "#/$defs/keyRef" },
"child": { "$ref": "#/$defs/keyRef" }
},
"required": [ "parent", "child" ]
},
"network_topology": {
"type": "object",
"properties": {
"class": { "type": "string", "enum": [ "network_topology" ] },
"key": { "type": "string" },
"name": { "type": "string" },
"model_name": { "type": [ "string", "null" ] },
"devices": { "type": "array", "items": { "key": "#/$defs/optionalKeyRef" } },
"logical_connections": { "type": "array", "items": { "key": "#/$defs/optionalKeyRef" } }
},
"required": [ "key", "name", "devices", "logical_connections" ]
}
}
}</code></pre>
</div>
</section>
<section class="section" id="overview-of-standardized-json-common-data-set__section_ds1_hbg_1gc"><h2 id="d3684e89" class="title sectiontitle">2. Decouple Connectivity from ETL</h2>
<p class="p">Ensure flexibility by separating device interaction logic from transformation logic (ETL ingestion). Users can develop their own collectors independently of the ETL logic.</p>
<div class="p">Ensure the following points:<ol class="ol" id="overview-of-standardized-json-common-data-set__ol_es1_hbg_1gc">
<li class="li">Design collectors to focus only on connectivity and data conversion to the unified schema.</li>
<li class="li">Use or reuse any EMS/NMS adaptor (including third-party adaptors like Atrinet).</li>
<li class="li">Push the standardized data into ServiceNow import sets.</li>
</ol></div>
</section>
<section class="section" id="overview-of-standardized-json-common-data-set__section_fs1_hbg_1gc"><h2 id="d3684e112" class="title sectiontitle">3. Configure Generic ETL for CMDB Updates</h2>
<p class="p">Use a single reusable ETL to process all standardized import sets and update the CMDB accurately.</p>
<p class="p">Ensure the following points:</p>
<ol class="ol" id="overview-of-standardized-json-common-data-set__ol_gs1_hbg_1gc">
<li class="li">Validate the import set contains data in the standardized JSON format.</li>
<li class="li">Use the TSOM Generic ETL to:<ul class="ul" id="overview-of-standardized-json-common-data-set__ul_hs1_hbg_1gc">
<li class="li">Detect the entity type (e.g., Slot, Card, Logical Interface).</li>
<li class="li">Map each entity to the correct CI class based on model mapping logic.</li>
<li class="li">Populate fields including Inventory Category where applicable.</li>
</ul></li>
</ol>
<p class="p">Special Handling:</p>
<ul class="ul" id="overview-of-standardized-json-common-data-set__ul_is1_hbg_1gc">
<li class="li">Logical Interfaces → Port table (<code class="ph codeph">virtual=true</code>)</li>
<li class="li">Logical Connections → Logical Connection table</li>
<li class="li">PDU Cards → PDU table</li>
<li class="li">Equipment → Model-based CI class (most recent mapping if multiple exist)</li>
</ul>
</section>
<section class="section" id="overview-of-standardized-json-common-data-set__section_js1_hbg_1gc"><h2 id="d3684e166" class="title sectiontitle">4. Configure support for Multi-Chassis and Composite Devices</h2>
<p class="p">Model complex devices such as multi-chassis routers with correct CMDB relationships.</p>
<div class="p">Ensure the following points:<ol class="ol" id="overview-of-standardized-json-common-data-set__ol_ks1_hbg_1gc">
<li class="li">Use the Logical Composite construct to represent grouped entities like Router + PDU.</li>
<li class="li">Define individual components (Fan, Management, Slot) under their respective hierarchy.</li>
<li class="li">Map each entity as per the TNI modeling guidance.</li>
</ol></div>
<div class="p">Example: For a 7750-2s multi-chassis device:<ul class="ul" id="overview-of-standardized-json-common-data-set__ul_ls1_hbg_1gc">
<li class="li">Logical Composite → contains Router and PDU</li>
<li class="li">PDU → contains Slots → Cards → Sub-slots</li>
</ul></div>
</section>
<section class="section" id="overview-of-standardized-json-common-data-set__section_ms1_hbg_1gc"><h2 id="d3684e200" class="title sectiontitle">5. Enable TNI Entity Creation Based on Installation</h2>
<p class="p">Ensure consistency with TNI standards without unnecessary record creation.</p>
<div class="p">Ensure the following points:<ul class="ul" id="overview-of-standardized-json-common-data-set__ul_ns1_hbg_1gc">
<li class="li">If TNI is installed:<ul class="ul" id="overview-of-standardized-json-common-data-set__ul_os1_hbg_1gc">
<li class="li">Automatically create a TNI Entity for each discovered CI.</li>
<li class="li">Set Inventory Category appropriately (e.g., "Logical Connection", "Interface").</li>
</ul></li>
<li class="li">If TNI is not installed: Skip TNI entity creation to avoid orphaned or invalid records.</li>
</ul></div>
</section>
</div>
</article></main></body></article> | {
"attachments": {
"all_attachments": null,
"topic_attachments": []
},
"available_languages": [
"enus"
],
"breadcrumbs": [
{
"title": "Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html"
},
{
"title": "Configuring Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/configuring-tsom.html"
},
{
"title": "Set up Telecom Visibility",
"topic_id": "product/tmt-telecom-service-operations-mgt/task/configuring-tsom-visibility.html"
},
{
"title": "Configuring the Telecom Discovery Builder framework ETL in a connector",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/configuring-the-telco-generic-schema-etl.html"
}
],
"breadcrumbs_html": "<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops\">Zurich Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html\">Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/configuring-tsom.html\">Configuring Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/configuring-tsom-visibility.html\">Set up Telecom Visibility</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/configuring-the-telco-generic-schema-etl.html\">Configuring the Telecom Discovery Builder framework ETL in a connector</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<span class=\"active\">Standardized JSON common data set to support all service graph connectors</span>",
"bundle_id": "zurich-telecom-service-ops",
"bundle_key": 2733,
"bundle_landing_page": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html",
"bundle_subtitle": null,
"bundle_title": "Zurich Telecommunications Service Operations Management",
"canonical_link": null,
"dates": {
"Added on": "2025-08-02T00:48:08.794016Z",
"Created on": "2025-07-18T00:00:00Z",
"Initial upload": "2025-07-30T22:24:33.519043Z",
"Updated on": "2025-07-31T00:00:00Z"
},
"dislike_url": "https://servicenow-be-prod.servicenow.com/dislike/55686937",
"dislikes": 0,
"es_archived_content": false,
"is_in_fav": false,
"is_liked": null,
"is_watched": false,
"keywords": [
" zurich zurich"
],
"labels": [
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "zurich",
"navtitle": "Zurich",
"outputclasses": [],
"subjectHeadId": "versions",
"subjectheadNavtitle": "Versions",
"visibility": "show-facet"
},
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "tsom",
"navtitle": "Telecommunications Service Operations Management",
"outputclasses": [],
"subjectHeadId": "products",
"subjectheadNavtitle": "Products",
"visibility": "show-facet"
}
],
"labels_text": "Versions > Zurich; Products > CRM and Industry Products > Telecommunications Media and Technology Assurance > Telecommunications Service Operations Management",
"like_url": "https://servicenow-be-prod.servicenow.com/like/55686937",
"likes": 0,
"metadata": {
"AI Search": null,
"AI Search Assist": null,
"Application Insights": null,
"Capabilities": null,
"Code Signing": null,
"Contextual Search": null,
"DC.contributor": null,
"DC.coverage": null,
"DC.creator": "ServiceNow",
"DC.date.created": "2025-07-18T08:47:07+05:30",
"DC.date.modified": "2025-07-31",
"DC.format": "HTML5",
"DC.identifier": "overview-of-standardized-json-common-data-set",
"DC.language": null,
"DC.relation": null,
"DC.rights.owner": "(C) Copyright 2025",
"DC.subject": null,
"DC.type": "concept",
"Data Discovery": null,
"Data Policy": null,
"Data Privacy": null,
"Discovery": null,
"External Content for AI Search": null,
"Field Administration": null,
"Field Normalization": null,
"Key Management Framework": null,
"Localization Framework": null,
"Now Platform": null,
"PlatSec": null,
"Platform": null,
"Platform Administration": null,
"Platform Performance": null,
"Platform Privacy": null,
"Proactive Triggers": null,
"Process Optimization": null,
"RN doc editing record number": null,
"Search Administration": null,
"Secrets Management": null,
"ServiceNow AI Platform": null,
"State Model": null,
"Subscription Management": null,
"Task Communications Management": null,
"Timeline Visualizations": null,
"User Administration": null,
"User Experience Analytics": null,
"Zing": null,
"ai-now-assist": null,
"app-name": null,
"app_route": null,
"azureapimanagemen": null,
"change-completed": null,
"change-item": null,
"change-request-id": null,
"change-request-reference": null,
"com.glide.embedded_help.category": null,
"component": null,
"copyright": "(C) Copyright 2025",
"crossroads": null,
"data": null,
"description": "Use the TSOM architecture to support standardized Service Graph Connectors using a unified schema and reusable ETL logic. This reduces onboarding time for new connectors and simplifies integration with CMDB.",
"dominant_bundle": null,
"erp-canvas-video": null,
"fsm-mobile": null,
"fsm-route": null,
"fsm-sched-opt": null,
"fsm-wrk-order": null,
"genai-round-7": null,
"generator": "DITA-OT",
"glossPartOfSpeech": null,
"glossStatus": null,
"guided setup": null,
"guided tours": null,
"keywords": null,
"min-toc": null,
"mini": null,
"mini-to truec": null,
"mini-toc": "yes",
"mini_toc": null,
"minitoc": null,
"modification": null,
"now-assist-app-gen-video": null,
"order": null,
"page-type": null,
"page-type ": null,
"prodname": null,
"product": null,
"product_name": null,
"release": null,
"resourceID": null,
"roles": null,
"route_page": null,
"route_params_listId": null,
"route_params_table": null,
"route_params_type": null,
"route_type": null,
"setconfigurationproperties": null,
"topic": null,
"translation-type": "source",
"version": null,
"workflow": "Customer and Industry",
"workplace-srvc-delvry-ditamap": null
},
"page_id": "product/tmt-telecom-service-operations-mgt/concept/overview-of-standardized-json-common-data-set.html",
"page_key": 55686937,
"preprocessed_PDF": "https://downloads.docs.servicenow.com/pdf/enus/servicenow-zurich-telecom-service-ops-enus.pdf",
"rating": null,
"read_time_data": {
"char_count": 13927,
"img_count": 0,
"read_time": 7,
"video_links": [
""
],
"word_count": 1700
},
"related_links": [],
"search_title": null,
"title": "Standardized JSON common data set to support all service graph connectors",
"topic_cluster": {
"clustered_by": {
"enabled": true,
"primary_key": "versions",
"primary_sort": "top-down",
"type": "subjecthead"
},
"clustered_labels": [
"versions"
],
"clustered_topics": [],
"clustering_title": "Zurich"
},
"topic_html": "<article class=\"hascomments\" data-page=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/overview-of-standardized-json-common-data-set.html\" id=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/overview-of-standardized-json-common-data-set.html\"><body id=\"overview-of-standardized-json-common-data-set\"><main role=\"main\"><article role=\"article\" class=\"dita\" id=\"overview-of-standardized-json-common-data-set\" aria-labelledby=\"title_overview-of-standardized-json-common-data-set\">\n <h1 class=\"title topictitle1\" id=\"title_overview-of-standardized-json-common-data-set\">Standardized JSON common data set to support all service graph connectors</h1>\n \n \n <div class=\"body conbody\"><p class=\"shortdesc\">Use the TSOM architecture to support standardized Service Graph Connectors using a unified schema and reusable ETL logic. This reduces onboarding time for new connectors and simplifies integration with CMDB.</p>\n <section class=\"section\" id=\"overview-of-standardized-json-common-data-set__section_phm_y1g_1gc\"><h2 id=\"d3684e42\" class=\"title sectiontitle\">1. Define the common JSON Schema</h2>\n \n <p class=\"p\">Standardize the output of all service graph connectors to align with a single JSON format that conforms to the TNI schema.</p>\n <div class=\"p\">Ensure the following points:<ol class=\"ol\" id=\"overview-of-standardized-json-common-data-set__ol_gqd_1bg_1gc\">\n <li class=\"li\">Implement conversion logic in the collector or adaptor to output data in the common schema.</li>\n <li class=\"li\">Ensure:<ul class=\"ul\" id=\"overview-of-standardized-json-common-data-set__ul_hqd_1bg_1gc\">\n <li class=\"li\">Slot-on-slot or card-on-card hierarchies are excluded.</li>\n <li class=\"li\">Logical interfaces are clearly marked with <code class=\"ph codeph\">virtual=true</code>.</li>\n <li class=\"li\">Equipment types align to model-class mappings.</li>\n </ul></li>\n </ol></div>\n <div class=\"note note note_note\"><span class=\"note__title\">Note:</span> The schema should support runtime adaptability to TNI changes if available.</div>\n <p class=\"p\">The following is the JSON schema common data set that supports all TSOM service graph connectors:</p>\n <div class=\"p\">\n <pre class=\"prettyprint language-plaintext\"><code class=\"pre codeblock language-plaintext\">{\n "$schema": "http://json-schema.org/draft-07/schema#",\n "title": "Telco Generic Schema",\n "version": "2.0.1",\n "oneOf": [\n {\n "type": "object",\n "properties": {\n "logical_composites": {\n "type": "array",\n "items": {\n "$ref": "#/$defs/logical_composite"\n }\n }\n },\n "required": [\n "logical_composites"\n ],\n "additionalProperties": false\n },\n {\n "type": "object",\n "properties": {\n "devices": {\n "type": "array",\n "items": {\n "$ref": "#/$defs/device"\n }\n }\n },\n "required": [\n "devices"\n ],\n "additionalProperties": false\n },\n {\n "type": "object",\n "properties": {\n "logical_connections": {\n "type": "array",\n "items": {\n "$ref": "#/$defs/logical_connection"\n }\n }\n },\n "required": [\n "logical_connections"\n ],\n "additionalProperties": false\n },\n {\n "type": "object",\n "properties": {\n "port_relations": {\n "type": "array",\n "items": {\n "$ref": "#/$defs/port_relation"\n }\n }\n },\n "required": [\n "port_relations"\n ],\n "additionalProperties": false\n },\n {\n "type": "object",\n "properties": {\n "logical_connection_relations": {\n "type": "array",\n "items": {\n "$ref": "#/$defs/logical_connection_relation"\n }\n }\n },\n "required": [\n "logical_connection_relations"\n ],\n "additionalProperties": false\n },\n {\n "type": "object",\n "properties": {\n "numbers": {\n "type": "array",\n "items": {\n "$ref": "#/$defs/number"\n }\n }\n },\n "required": [\n "numbers"\n ],\n "additionalProperties": false\n },\n {\n "type": "object",\n "properties": {\n "topologies": {\n "type": "array",\n "items": {\n "$ref": "#/$defs/network_topology"\n }\n }\n },\n "required": [\n "topologies"\n ],\n "additionalProperties": false\n },\n {\n "type": "object",\n "properties": {\n "topology_relations": {\n "type": "array",\n "items": {\n "$ref": "#/$defs/network_topology_relation"\n }\n }\n },\n "required": [\n "topology_relations"\n ],\n "additionalProperties": false\n }\n ],\n "$defs": {\n "keyRef": {\n "type": "object",\n "properties": { "key": { "type": "string" }\n },\n "required": [ "key" ],\n "additionalProperties": false\n },\n "optionalKeyRef": { "type": [ "object", "null" ],\n "properties": {\n "key": { "type": "string" }\n },\n "additionalProperties": false\n },\n "value": {\n "type": "object",\n "properties": {\n "from": { "type": [ "integer" ], "default": 0, "minimum": 0 },\n "to": { "type": [ "integer" ], "default": 0, "minimum": 0 }\n },\n "required": [ "from", "to" ],\n "additionalProperties": false\n },\n "logical_composite": {\n "type": "object",\n "properties": {\n "class": { "type": "string", "enum": [ "logical_composite" ] },\n "key": { "type": "string" },\n "name": { "type": [ "string", "null" ] },\n "description": { "type": [ "string", "null" ] },\n "devices": { "type": "array", "items": { "$ref": "#/$defs/keyRef" } },\n "power_units": { "type": "array", "items": { "$ref": "#/$defs/pdu" } },\n "fan_shelves": { "type": "array", "items": { "$ref": "#/$defs/fan_shelf" } } },\n "required": [ "key", "name" ]\n },\n "pdu": {\n "type": "object",\n "properties": {\n "class": { "type": "string", "enum": [ "pdu" ] },\n "key": { "type": "string" },\n "name": { "type": [ "string", "null" ] },\n "description": { "type": [ "string", "null" ] },\n "model_name": { "type": [ "string", "null" ] },\n "model_number": { "type": [ "string", "null" ] },\n "unit_position": { "type": [ "integer", "null" ], "minimum": 1 },\n "slots": { "type": "array", "items": { "$ref": "#/$defs/slot" } }\n },\n "required": [ "key", "name" ]\n },\n "fan_shelf": {\n "type": "object",\n "properties": {\n "class": { "type": "string", "enum": [ "fan_shelf" ] },\n "key": { "type": "string" },\n "name": { "type": [ "string", "null" ] },\n "description": { "type": [ "string", "null" ] },\n "slots": { "type": "array", "items": { "$ref": "#/$defs/slot" } }\n },\n "required": [ "key", "name" ]\n },\n "device": {\n "type": "object",\n "properties": {\n "class": { "type": "string", "enum": [ "device" ] },\n "key": { "type": "string" },\n "name": { "type": [ "string", "null" ] },\n "description": { "type": [ "string", "null" ] },\n "ip_address": { "type": [ "string", "null" ] },\n "mac_address": { "type": [ "string", "null" ] },\n "serial_number": { "type": [ "string", "null" ] },\n "model_name": { "type": [ "string", "null" ] },\n "model_number": { "type": [ "string", "null" ] },\n "manufacturer": { "type": [ "string", "null" ] },\n "firmware_version": { "type": [ "string", "null" ] },\n "slots": { "type": "array", "items": { "$ref": "#/$defs/slot" } },\n "ports": { "type": "array", "items": { "$ref": "#/$defs/port" } } },\n "required": [ "key", "name", "serial_number" ]\n },\n "slot": {\n "type": "object",\n "properties": {\n "class": { "type": "string", "enum": [ "slot" ] },\n "key": { "type": "string" },\n "name": { "type": [ "string", "null" ] },\n "description": { "type": [ "string", "null" ] },\n "model_name": { "type": [ "string", "null" ] },\n "model_number": { "type": [ "string", "null" ] },\n "manufacturer": { "type": [ "string", "null" ] },\n "unit_position": { "type": [ "integer", "null" ], "minimum": 1 },\n "cards": { "type": "array", "items": { "$ref": "#/$defs/card" } }\n },\n "required": [ "key", "name" ]\n },\n "card": {\n "type": "object",\n "properties": {\n "class": { "type": "string", "enum": [ "card" ] },\n "key": { "type": "string" },\n "name": { "type": [ "string", "null" ] },\n "description": { "type": [ "string", "null" ] },\n "mac_address": { "type": [ "string", "null" ] },\n "serial_number": { "type": [ "string", "null" ] },\n "firmware_version": { "type": [ "string", "null" ] },\n "model_name": { "type": [ "string", "null" ] },\n "model_number": { "type": [ "string", "null" ] },\n "manufacturer": { "type": [ "string", "null" ] },\n "unit_position": { "type": [ "integer", "null" ], "minimum": 1 },\n "slots": { "type": "array", "items": { "$ref": "#/$defs/slot" } },\n "ports": { "type": "array", "items": { "$ref": "#/$defs/port" } }\n },\n "required": [ "key", "name" ]\n },\n "port": {\n "type": "object",\n "properties": {\n "class": { "type": "string", "enum": [ "port" ] },\n "key": { "type": "string" },\n "name": { "type": [ "string", "null" ] },\n "description": { "type": [ "string", "null" ] },\n "model_name": { "type": [ "string", "null" ] },\n "ip_address": { "type": [ "string", "null" ] },\n "virtual": { "type": "boolean", "default": false },\n "unit_position": { "type": [ "integer", "null" ], "minimum": 1 },\n "bandwidth_name": { "type": [ "string", "null" ] },\n "bandwidth_group": { "type": [ "string", "null" ] },\n "bandwidth": { "type": [ "integer", "null" ], "minimum": 0 },\n "mtu_size": { "type": [ "integer", "null" ], "minimum": 0 }\n },\n "required": [ "key", "name" ]\n },\n "number": {\n "type": "object",\n "properties": {\n "class": { "type": "string", "enum": [ "number" ] },\n "key": { "type": "string" },\n "name": { "type": [ "string", "null" ] },\n "related_ci_type": { "type": "string", "enum": [ "Network Interface", "Physical Connection", "Logical Connection", "Equipment", "Topology" ] },\n "related_ci": { "$ref": "#/$defs/keyRef" },\n "type": { "type": "string", "enum": [ "vlan_range", "vlan_subrange", "vlan", "lag_range", "lag" ] },\n "vlan_type": { "type": "string", "enum": [ "inner", "outer" ] },\n "value": { "$ref": "#/$defs/value" }\n },\n "required": [ "key", "name", "type", "related_ci_type", "related_ci", "value" ] },\n "logical_connection": {\n "type": "object",\n "properties": {\n "class": { "type": "string", "enum": [ "logical_connection" ] },\n "key": { "type": "string" },\n "name": { "type": [ "string", "null" ] },\n "description": { "type": [ "string", "null" ] },\n "model_name": { "type": [ "string", "null" ] },\n "bandwidth_group": { "type": [ "string", "null" ] },\n "bandwidth_name_a_to_z": { "type": [ "string", "null" ] },\n "bandwidth_name_z_to_a": { "type": [ "string", "null" ] },\n "bandwidth_a_to_z": { "type": [ "integer", "null" ], "minimum": 0 },\n "bandwidth_z_to_a": { "type": [ "integer", "null" ], "minimum": 0 },\n "equipment_a": { "$ref": "#/$defs/optionalKeyRef" },\n "equipment_z": { "$ref": "#/$defs/optionalKeyRef" },\n "port_a": { "$ref": "#/$defs/keyRef" },\n "port_z": { "$ref": "#/$defs/keyRef" }\n },\n "required": [ "key", "name", "equipment_a", "equipment_z", "port_a", "port_z" ]\n },\n "port_relation": {\n "type": "object",\n "properties": {\n "class": { "type": "string", "enum": [ "port_relation" ] },\n "parent": { "$ref": "#/$defs/keyRef" },\n "child": { "$ref": "#/$defs/keyRef" }\n },\n "required": [ "parent", "child" ]\n },\n "logical_connection_relation": {\n "type": "object",\n "properties": {\n "class": { "type": "string", "enum": [ "logical_connection_relation" ] },\n "sequence": { "type": [ "integer", "null" ], "minimum": 1 },\n "route": { "type": [ "integer", "null" ], "minimum": 1 },\n "parent": { "$ref": "#/$defs/keyRef" },\n "child": { "$ref": "#/$defs/keyRef" }\n },\n "required": [ "parent", "child" ]\n },\n "network_topology": {\n "type": "object",\n "properties": {\n "class": { "type": "string", "enum": [ "network_topology" ] },\n "key": { "type": "string" },\n "name": { "type": "string" },\n "model_name": { "type": [ "string", "null" ] },\n "devices": { "type": "array", "items": { "key": "#/$defs/optionalKeyRef" } },\n "logical_connections": { "type": "array", "items": { "key": "#/$defs/optionalKeyRef" } }\n },\n "required": [ "key", "name", "devices", "logical_connections" ]\n }\n }\n}</code></pre>\n </div>\n </section>\n <section class=\"section\" id=\"overview-of-standardized-json-common-data-set__section_ds1_hbg_1gc\"><h2 id=\"d3684e89\" class=\"title sectiontitle\">2. Decouple Connectivity from ETL</h2>\n \n <p class=\"p\">Ensure flexibility by separating device interaction logic from transformation logic (ETL ingestion). Users can develop their own collectors independently of the ETL logic.</p>\n <div class=\"p\">Ensure the following points:<ol class=\"ol\" id=\"overview-of-standardized-json-common-data-set__ol_es1_hbg_1gc\">\n <li class=\"li\">Design collectors to focus only on connectivity and data conversion to the unified schema.</li>\n <li class=\"li\">Use or reuse any EMS/NMS adaptor (including third-party adaptors like Atrinet).</li>\n <li class=\"li\">Push the standardized data into ServiceNow import sets.</li>\n </ol></div>\n </section>\n <section class=\"section\" id=\"overview-of-standardized-json-common-data-set__section_fs1_hbg_1gc\"><h2 id=\"d3684e112\" class=\"title sectiontitle\">3. Configure Generic ETL for CMDB Updates</h2>\n \n <p class=\"p\">Use a single reusable ETL to process all standardized import sets and update the CMDB accurately.</p>\n <p class=\"p\">Ensure the following points:</p>\n <ol class=\"ol\" id=\"overview-of-standardized-json-common-data-set__ol_gs1_hbg_1gc\">\n <li class=\"li\">Validate the import set contains data in the standardized JSON format.</li>\n <li class=\"li\">Use the TSOM Generic ETL to:<ul class=\"ul\" id=\"overview-of-standardized-json-common-data-set__ul_hs1_hbg_1gc\">\n <li class=\"li\">Detect the entity type (e.g., Slot, Card, Logical Interface).</li>\n <li class=\"li\">Map each entity to the correct CI class based on model mapping logic.</li>\n <li class=\"li\">Populate fields including Inventory Category where applicable.</li>\n </ul></li>\n </ol>\n <p class=\"p\">Special Handling:</p>\n <ul class=\"ul\" id=\"overview-of-standardized-json-common-data-set__ul_is1_hbg_1gc\">\n <li class=\"li\">Logical Interfaces → Port table (<code class=\"ph codeph\">virtual=true</code>)</li>\n <li class=\"li\">Logical Connections → Logical Connection table</li>\n <li class=\"li\">PDU Cards → PDU table</li>\n <li class=\"li\">Equipment → Model-based CI class (most recent mapping if multiple exist)</li>\n </ul>\n </section>\n <section class=\"section\" id=\"overview-of-standardized-json-common-data-set__section_js1_hbg_1gc\"><h2 id=\"d3684e166\" class=\"title sectiontitle\">4. Configure support for Multi-Chassis and Composite Devices</h2>\n \n <p class=\"p\">Model complex devices such as multi-chassis routers with correct CMDB relationships.</p>\n <div class=\"p\">Ensure the following points:<ol class=\"ol\" id=\"overview-of-standardized-json-common-data-set__ol_ks1_hbg_1gc\">\n <li class=\"li\">Use the Logical Composite construct to represent grouped entities like Router + PDU.</li>\n <li class=\"li\">Define individual components (Fan, Management, Slot) under their respective hierarchy.</li>\n <li class=\"li\">Map each entity as per the TNI modeling guidance.</li>\n </ol></div>\n <div class=\"p\">Example: For a 7750-2s multi-chassis device:<ul class=\"ul\" id=\"overview-of-standardized-json-common-data-set__ul_ls1_hbg_1gc\">\n <li class=\"li\">Logical Composite → contains Router and PDU</li>\n <li class=\"li\">PDU → contains Slots → Cards → Sub-slots</li>\n </ul></div>\n </section>\n <section class=\"section\" id=\"overview-of-standardized-json-common-data-set__section_ms1_hbg_1gc\"><h2 id=\"d3684e200\" class=\"title sectiontitle\">5. Enable TNI Entity Creation Based on Installation</h2>\n \n <p class=\"p\">Ensure consistency with TNI standards without unnecessary record creation.</p>\n <div class=\"p\">Ensure the following points:<ul class=\"ul\" id=\"overview-of-standardized-json-common-data-set__ul_ns1_hbg_1gc\">\n <li class=\"li\">If TNI is installed:<ul class=\"ul\" id=\"overview-of-standardized-json-common-data-set__ul_os1_hbg_1gc\">\n <li class=\"li\">Automatically create a TNI Entity for each discovered CI.</li>\n <li class=\"li\">Set Inventory Category appropriately (e.g., "Logical Connection", "Interface").</li>\n </ul></li>\n <li class=\"li\">If TNI is not installed: Skip TNI entity creation to avoid orphaned or invalid records.</li>\n </ul></div>\n </section>\n </div>\n</article></main></body></article>",
"topic_language": "enus",
"views": 0,
"your_rating": null
} | # Standardized JSON common data set to support all service graph connectors
Use the TSOM architecture to support standardized Service Graph Connectors using a unified schema and reusable ETL logic. This reduces onboarding time for new connectors and simplifies integration with CMDB.
## 1. Define the common JSON Schema
Standardize the output of all service graph connectors to align with a single JSON format that conforms to the TNI schema.
Ensure the following points:
1. Implement conversion logic in the collector or adaptor to output data in the common schema.
2. Ensure:
* Slot-on-slot or card-on-card hierarchies are excluded.
* Logical interfaces are clearly marked with `virtual=true`.
* Equipment types align to model-class mappings.
Note: The schema should support runtime adaptability to TNI changes if available.
The following is the JSON schema common data set that supports all TSOM service graph connectors:
```None
{
"$schema": "http://json-schema.org/draft-07/schema#",
"title": "Telco Generic Schema",
"version": "2.0.1",
"oneOf": [
{
"type": "object",
"properties": {
"logical_composites": {
"type": "array",
"items": {
"$ref": "#/$defs/logical_composite"
}
}
},
"required": [
"logical_composites"
],
"additionalProperties": false
},
{
"type": "object",
"properties": {
"devices": {
"type": "array",
"items": {
"$ref": "#/$defs/device"
}
}
},
"required": [
"devices"
],
"additionalProperties": false
},
{
"type": "object",
"properties": {
"logical_connections": {
"type": "array",
"items": {
"$ref": "#/$defs/logical_connection"
}
}
},
"required": [
"logical_connections"
],
"additionalProperties": false
},
{
"type": "object",
"properties": {
"port_relations": {
"type": "array",
"items": {
"$ref": "#/$defs/port_relation"
}
}
},
"required": [
"port_relations"
],
"additionalProperties": false
},
{
"type": "object",
"properties": {
"logical_connection_relations": {
"type": "array",
"items": {
"$ref": "#/$defs/logical_connection_relation"
}
}
},
"required": [
"logical_connection_relations"
],
"additionalProperties": false
},
{
"type": "object",
"properties": {
"numbers": {
"type": "array",
"items": {
"$ref": "#/$defs/number"
}
}
},
"required": [
"numbers"
],
"additionalProperties": false
},
{
"type": "object",
"properties": {
"topologies": {
"type": "array",
"items": {
"$ref": "#/$defs/network_topology"
}
}
},
"required": [
"topologies"
],
"additionalProperties": false
},
{
"type": "object",
"properties": {
"topology_relations": {
"type": "array",
"items": {
"$ref": "#/$defs/network_topology_relation"
}
}
},
"required": [
"topology_relations"
],
"additionalProperties": false
}
],
"$defs": {
"keyRef": {
"type": "object",
"properties": { "key": { "type": "string" }
},
"required": [ "key" ],
"additionalProperties": false
},
"optionalKeyRef": { "type": [ "object", "null" ],
"properties": {
"key": { "type": "string" }
},
"additionalProperties": false
},
"value": {
"type": "object",
"properties": {
"from": { "type": [ "integer" ], "default": 0, "minimum": 0 },
"to": { "type": [ "integer" ], "default": 0, "minimum": 0 }
},
"required": [ "from", "to" ],
"additionalProperties": false
},
"logical_composite": {
"type": "object",
"properties": {
"class": { "type": "string", "enum": [ "logical_composite" ] },
"key": { "type": "string" },
"name": { "type": [ "string", "null" ] },
"description": { "type": [ "string", "null" ] },
"devices": { "type": "array", "items": { "$ref": "#/$defs/keyRef" } },
"power_units": { "type": "array", "items": { "$ref": "#/$defs/pdu" } },
"fan_shelves": { "type": "array", "items": { "$ref": "#/$defs/fan_shelf" } } },
"required": [ "key", "name" ]
},
"pdu": {
"type": "object",
"properties": {
"class": { "type": "string", "enum": [ "pdu" ] },
"key": { "type": "string" },
"name": { "type": [ "string", "null" ] },
"description": { "type": [ "string", "null" ] },
"model_name": { "type": [ "string", "null" ] },
"model_number": { "type": [ "string", "null" ] },
"unit_position": { "type": [ "integer", "null" ], "minimum": 1 },
"slots": { "type": "array", "items": { "$ref": "#/$defs/slot" } }
},
"required": [ "key", "name" ]
},
"fan_shelf": {
"type": "object",
"properties": {
"class": { "type": "string", "enum": [ "fan_shelf" ] },
"key": { "type": "string" },
"name": { "type": [ "string", "null" ] },
"description": { "type": [ "string", "null" ] },
"slots": { "type": "array", "items": { "$ref": "#/$defs/slot" } }
},
"required": [ "key", "name" ]
},
"device": {
"type": "object",
"properties": {
"class": { "type": "string", "enum": [ "device" ] },
"key": { "type": "string" },
"name": { "type": [ "string", "null" ] },
"description": { "type": [ "string", "null" ] },
"ip_address": { "type": [ "string", "null" ] },
"mac_address": { "type": [ "string", "null" ] },
"serial_number": { "type": [ "string", "null" ] },
"model_name": { "type": [ "string", "null" ] },
"model_number": { "type": [ "string", "null" ] },
"manufacturer": { "type": [ "string", "null" ] },
"firmware_version": { "type": [ "string", "null" ] },
"slots": { "type": "array", "items": { "$ref": "#/$defs/slot" } },
"ports": { "type": "array", "items": { "$ref": "#/$defs/port" } } },
"required": [ "key", "name", "serial_number" ]
},
"slot": {
"type": "object",
"properties": {
"class": { "type": "string", "enum": [ "slot" ] },
"key": { "type": "string" },
"name": { "type": [ "string", "null" ] },
"description": { "type": [ "string", "null" ] },
"model_name": { "type": [ "string", "null" ] },
"model_number": { "type": [ "string", "null" ] },
"manufacturer": { "type": [ "string", "null" ] },
"unit_position": { "type": [ "integer", "null" ], "minimum": 1 },
"cards": { "type": "array", "items": { "$ref": "#/$defs/card" } }
},
"required": [ "key", "name" ]
},
"card": {
"type": "object",
"properties": {
"class": { "type": "string", "enum": [ "card" ] },
"key": { "type": "string" },
"name": { "type": [ "string", "null" ] },
"description": { "type": [ "string", "null" ] },
"mac_address": { "type": [ "string", "null" ] },
"serial_number": { "type": [ "string", "null" ] },
"firmware_version": { "type": [ "string", "null" ] },
"model_name": { "type": [ "string", "null" ] },
"model_number": { "type": [ "string", "null" ] },
"manufacturer": { "type": [ "string", "null" ] },
"unit_position": { "type": [ "integer", "null" ], "minimum": 1 },
"slots": { "type": "array", "items": { "$ref": "#/$defs/slot" } },
"ports": { "type": "array", "items": { "$ref": "#/$defs/port" } }
},
"required": [ "key", "name" ]
},
"port": {
"type": "object",
"properties": {
"class": { "type": "string", "enum": [ "port" ] },
"key": { "type": "string" },
"name": { "type": [ "string", "null" ] },
"description": { "type": [ "string", "null" ] },
"model_name": { "type": [ "string", "null" ] },
"ip_address": { "type": [ "string", "null" ] },
"virtual": { "type": "boolean", "default": false },
"unit_position": { "type": [ "integer", "null" ], "minimum": 1 },
"bandwidth_name": { "type": [ "string", "null" ] },
"bandwidth_group": { "type": [ "string", "null" ] },
"bandwidth": { "type": [ "integer", "null" ], "minimum": 0 },
"mtu_size": { "type": [ "integer", "null" ], "minimum": 0 }
},
"required": [ "key", "name" ]
},
"number": {
"type": "object",
"properties": {
"class": { "type": "string", "enum": [ "number" ] },
"key": { "type": "string" },
"name": { "type": [ "string", "null" ] },
"related_ci_type": { "type": "string", "enum": [ "Network Interface", "Physical Connection", "Logical Connection", "Equipment", "Topology" ] },
"related_ci": { "$ref": "#/$defs/keyRef" },
"type": { "type": "string", "enum": [ "vlan_range", "vlan_subrange", "vlan", "lag_range", "lag" ] },
"vlan_type": { "type": "string", "enum": [ "inner", "outer" ] },
"value": { "$ref": "#/$defs/value" }
},
"required": [ "key", "name", "type", "related_ci_type", "related_ci", "value" ] },
"logical_connection": {
"type": "object",
"properties": {
"class": { "type": "string", "enum": [ "logical_connection" ] },
"key": { "type": "string" },
"name": { "type": [ "string", "null" ] },
"description": { "type": [ "string", "null" ] },
"model_name": { "type": [ "string", "null" ] },
"bandwidth_group": { "type": [ "string", "null" ] },
"bandwidth_name_a_to_z": { "type": [ "string", "null" ] },
"bandwidth_name_z_to_a": { "type": [ "string", "null" ] },
"bandwidth_a_to_z": { "type": [ "integer", "null" ], "minimum": 0 },
"bandwidth_z_to_a": { "type": [ "integer", "null" ], "minimum": 0 },
"equipment_a": { "$ref": "#/$defs/optionalKeyRef" },
"equipment_z": { "$ref": "#/$defs/optionalKeyRef" },
"port_a": { "$ref": "#/$defs/keyRef" },
"port_z": { "$ref": "#/$defs/keyRef" }
},
"required": [ "key", "name", "equipment_a", "equipment_z", "port_a", "port_z" ]
},
"port_relation": {
"type": "object",
"properties": {
"class": { "type": "string", "enum": [ "port_relation" ] },
"parent": { "$ref": "#/$defs/keyRef" },
"child": { "$ref": "#/$defs/keyRef" }
},
"required": [ "parent", "child" ]
},
"logical_connection_relation": {
"type": "object",
"properties": {
"class": { "type": "string", "enum": [ "logical_connection_relation" ] },
"sequence": { "type": [ "integer", "null" ], "minimum": 1 },
"route": { "type": [ "integer", "null" ], "minimum": 1 },
"parent": { "$ref": "#/$defs/keyRef" },
"child": { "$ref": "#/$defs/keyRef" }
},
"required": [ "parent", "child" ]
},
"network_topology": {
"type": "object",
"properties": {
"class": { "type": "string", "enum": [ "network_topology" ] },
"key": { "type": "string" },
"name": { "type": "string" },
"model_name": { "type": [ "string", "null" ] },
"devices": { "type": "array", "items": { "key": "#/$defs/optionalKeyRef" } },
"logical_connections": { "type": "array", "items": { "key": "#/$defs/optionalKeyRef" } }
},
"required": [ "key", "name", "devices", "logical_connections" ]
}
}
}
```
## 2. Decouple Connectivity from ETL
Ensure flexibility by separating device interaction logic from transformation logic (ETL ingestion). Users can develop their own collectors independently of the ETL logic.
Ensure the following points:
1. Design collectors to focus only on connectivity and data conversion to the unified schema.
2. Use or reuse any EMS/NMS adaptor (including third-party adaptors like Atrinet).
3. Push the standardized data into ServiceNow import sets.
## 3. Configure Generic ETL for CMDB Updates
Use a single reusable ETL to process all standardized import sets and update the CMDB accurately.
Ensure the following points:
1. Validate the import set contains data in the standardized JSON format.
2. Use the TSOM Generic ETL to:
* Detect the entity type (e.g., Slot, Card, Logical Interface).
* Map each entity to the correct CI class based on model mapping logic.
* Populate fields including Inventory Category where applicable.
Special Handling:
* Logical Interfaces → Port table (`virtual=true`)
* Logical Connections → Logical Connection table
* PDU Cards → PDU table
* Equipment → Model-based CI class (most recent mapping if multiple exist)
## 4. Configure support for Multi-Chassis and Composite Devices
Model complex devices such as multi-chassis routers with correct CMDB relationships.
Ensure the following points:
1. Use the Logical Composite construct to represent grouped entities like Router + PDU.
2. Define individual components (Fan, Management, Slot) under their respective hierarchy.
3. Map each entity as per the TNI modeling guidance.
Example: For a 7750-2s multi-chassis device:
* Logical Composite → contains Router and PDU
* PDU → contains Slots → Cards → Sub-slots
## 5. Enable TNI Entity Creation Based on Installation
Ensure consistency with TNI standards without unnecessary record creation.
Ensure the following points:
* If TNI is installed:
+ Automatically create a TNI Entity for each discovered CI.
+ Set Inventory Category appropriately (e.g., "Logical Connection", "Interface").
* If TNI is not installed: Skip TNI entity creation to avoid orphaned or invalid records.
| ---
title: Standardized JSON common data set to support all service graph connectors
description: Use the TSOM architecture to support standardized Service Graph Connectors
using a unified schema and reusable ETL logic. This reduces onboarding time for
new connectors and simplifies integration with CMDB.
keywords: []
breadcrumbs:
- Telecommunications Service Operations Management
- Configuring Telecommunications Service Operations Management
- Set up Telecom Visibility
- Configuring the Telecom Discovery Builder framework ETL in a connector
---
# Standardized JSON common data set to support all service graph connectors
Use the TSOM architecture to support standardized Service Graph Connectors using a unified schema and reusable ETL logic. This reduces onboarding time for new connectors and simplifies integration with CMDB.
## 1. Define the common JSON Schema
Standardize the output of all service graph connectors to align with a single JSON format that conforms to the TNI schema.
Ensure the following points:
1. Implement conversion logic in the collector or adaptor to output data in the common schema.
2. Ensure:
* Slot-on-slot or card-on-card hierarchies are excluded.
* Logical interfaces are clearly marked with `virtual=true`.
* Equipment types align to model-class mappings.
Note: The schema should support runtime adaptability to TNI changes if available.
The following is the JSON schema common data set that supports all TSOM service graph connectors:
```None
{
"$schema": "http://json-schema.org/draft-07/schema#",
"title": "Telco Generic Schema",
"version": "2.0.1",
"oneOf": [
{
"type": "object",
"properties": {
"logical_composites": {
"type": "array",
"items": {
"$ref": "#/$defs/logical_composite"
}
}
},
"required": [
"logical_composites"
],
"additionalProperties": false
},
{
"type": "object",
"properties": {
"devices": {
"type": "array",
"items": {
"$ref": "#/$defs/device"
}
}
},
"required": [
"devices"
],
"additionalProperties": false
},
{
"type": "object",
"properties": {
"logical_connections": {
"type": "array",
"items": {
"$ref": "#/$defs/logical_connection"
}
}
},
"required": [
"logical_connections"
],
"additionalProperties": false
},
{
"type": "object",
"properties": {
"port_relations": {
"type": "array",
"items": {
"$ref": "#/$defs/port_relation"
}
}
},
"required": [
"port_relations"
],
"additionalProperties": false
},
{
"type": "object",
"properties": {
"logical_connection_relations": {
"type": "array",
"items": {
"$ref": "#/$defs/logical_connection_relation"
}
}
},
"required": [
"logical_connection_relations"
],
"additionalProperties": false
},
{
"type": "object",
"properties": {
"numbers": {
"type": "array",
"items": {
"$ref": "#/$defs/number"
}
}
},
"required": [
"numbers"
],
"additionalProperties": false
},
{
"type": "object",
"properties": {
"topologies": {
"type": "array",
"items": {
"$ref": "#/$defs/network_topology"
}
}
},
"required": [
"topologies"
],
"additionalProperties": false
},
{
"type": "object",
"properties": {
"topology_relations": {
"type": "array",
"items": {
"$ref": "#/$defs/network_topology_relation"
}
}
},
"required": [
"topology_relations"
],
"additionalProperties": false
}
],
"$defs": {
"keyRef": {
"type": "object",
"properties": { "key": { "type": "string" }
},
"required": [ "key" ],
"additionalProperties": false
},
"optionalKeyRef": { "type": [ "object", "null" ],
"properties": {
"key": { "type": "string" }
},
"additionalProperties": false
},
"value": {
"type": "object",
"properties": {
"from": { "type": [ "integer" ], "default": 0, "minimum": 0 },
"to": { "type": [ "integer" ], "default": 0, "minimum": 0 }
},
"required": [ "from", "to" ],
"additionalProperties": false
},
"logical_composite": {
"type": "object",
"properties": {
"class": { "type": "string", "enum": [ "logical_composite" ] },
"key": { "type": "string" },
"name": { "type": [ "string", "null" ] },
"description": { "type": [ "string", "null" ] },
"devices": { "type": "array", "items": { "$ref": "#/$defs/keyRef" } },
"power_units": { "type": "array", "items": { "$ref": "#/$defs/pdu" } },
"fan_shelves": { "type": "array", "items": { "$ref": "#/$defs/fan_shelf" } } },
"required": [ "key", "name" ]
},
"pdu": {
"type": "object",
"properties": {
"class": { "type": "string", "enum": [ "pdu" ] },
"key": { "type": "string" },
"name": { "type": [ "string", "null" ] },
"description": { "type": [ "string", "null" ] },
"model_name": { "type": [ "string", "null" ] },
"model_number": { "type": [ "string", "null" ] },
"unit_position": { "type": [ "integer", "null" ], "minimum": 1 },
"slots": { "type": "array", "items": { "$ref": "#/$defs/slot" } }
},
"required": [ "key", "name" ]
},
"fan_shelf": {
"type": "object",
"properties": {
"class": { "type": "string", "enum": [ "fan_shelf" ] },
"key": { "type": "string" },
"name": { "type": [ "string", "null" ] },
"description": { "type": [ "string", "null" ] },
"slots": { "type": "array", "items": { "$ref": "#/$defs/slot" } }
},
"required": [ "key", "name" ]
},
"device": {
"type": "object",
"properties": {
"class": { "type": "string", "enum": [ "device" ] },
"key": { "type": "string" },
"name": { "type": [ "string", "null" ] },
"description": { "type": [ "string", "null" ] },
"ip_address": { "type": [ "string", "null" ] },
"mac_address": { "type": [ "string", "null" ] },
"serial_number": { "type": [ "string", "null" ] },
"model_name": { "type": [ "string", "null" ] },
"model_number": { "type": [ "string", "null" ] },
"manufacturer": { "type": [ "string", "null" ] },
"firmware_version": { "type": [ "string", "null" ] },
"slots": { "type": "array", "items": { "$ref": "#/$defs/slot" } },
"ports": { "type": "array", "items": { "$ref": "#/$defs/port" } } },
"required": [ "key", "name", "serial_number" ]
},
"slot": {
"type": "object",
"properties": {
"class": { "type": "string", "enum": [ "slot" ] },
"key": { "type": "string" },
"name": { "type": [ "string", "null" ] },
"description": { "type": [ "string", "null" ] },
"model_name": { "type": [ "string", "null" ] },
"model_number": { "type": [ "string", "null" ] },
"manufacturer": { "type": [ "string", "null" ] },
"unit_position": { "type": [ "integer", "null" ], "minimum": 1 },
"cards": { "type": "array", "items": { "$ref": "#/$defs/card" } }
},
"required": [ "key", "name" ]
},
"card": {
"type": "object",
"properties": {
"class": { "type": "string", "enum": [ "card" ] },
"key": { "type": "string" },
"name": { "type": [ "string", "null" ] },
"description": { "type": [ "string", "null" ] },
"mac_address": { "type": [ "string", "null" ] },
"serial_number": { "type": [ "string", "null" ] },
"firmware_version": { "type": [ "string", "null" ] },
"model_name": { "type": [ "string", "null" ] },
"model_number": { "type": [ "string", "null" ] },
"manufacturer": { "type": [ "string", "null" ] },
"unit_position": { "type": [ "integer", "null" ], "minimum": 1 },
"slots": { "type": "array", "items": { "$ref": "#/$defs/slot" } },
"ports": { "type": "array", "items": { "$ref": "#/$defs/port" } }
},
"required": [ "key", "name" ]
},
"port": {
"type": "object",
"properties": {
"class": { "type": "string", "enum": [ "port" ] },
"key": { "type": "string" },
"name": { "type": [ "string", "null" ] },
"description": { "type": [ "string", "null" ] },
"model_name": { "type": [ "string", "null" ] },
"ip_address": { "type": [ "string", "null" ] },
"virtual": { "type": "boolean", "default": false },
"unit_position": { "type": [ "integer", "null" ], "minimum": 1 },
"bandwidth_name": { "type": [ "string", "null" ] },
"bandwidth_group": { "type": [ "string", "null" ] },
"bandwidth": { "type": [ "integer", "null" ], "minimum": 0 },
"mtu_size": { "type": [ "integer", "null" ], "minimum": 0 }
},
"required": [ "key", "name" ]
},
"number": {
"type": "object",
"properties": {
"class": { "type": "string", "enum": [ "number" ] },
"key": { "type": "string" },
"name": { "type": [ "string", "null" ] },
"related_ci_type": { "type": "string", "enum": [ "Network Interface", "Physical Connection", "Logical Connection", "Equipment", "Topology" ] },
"related_ci": { "$ref": "#/$defs/keyRef" },
"type": { "type": "string", "enum": [ "vlan_range", "vlan_subrange", "vlan", "lag_range", "lag" ] },
"vlan_type": { "type": "string", "enum": [ "inner", "outer" ] },
"value": { "$ref": "#/$defs/value" }
},
"required": [ "key", "name", "type", "related_ci_type", "related_ci", "value" ] },
"logical_connection": {
"type": "object",
"properties": {
"class": { "type": "string", "enum": [ "logical_connection" ] },
"key": { "type": "string" },
"name": { "type": [ "string", "null" ] },
"description": { "type": [ "string", "null" ] },
"model_name": { "type": [ "string", "null" ] },
"bandwidth_group": { "type": [ "string", "null" ] },
"bandwidth_name_a_to_z": { "type": [ "string", "null" ] },
"bandwidth_name_z_to_a": { "type": [ "string", "null" ] },
"bandwidth_a_to_z": { "type": [ "integer", "null" ], "minimum": 0 },
"bandwidth_z_to_a": { "type": [ "integer", "null" ], "minimum": 0 },
"equipment_a": { "$ref": "#/$defs/optionalKeyRef" },
"equipment_z": { "$ref": "#/$defs/optionalKeyRef" },
"port_a": { "$ref": "#/$defs/keyRef" },
"port_z": { "$ref": "#/$defs/keyRef" }
},
"required": [ "key", "name", "equipment_a", "equipment_z", "port_a", "port_z" ]
},
"port_relation": {
"type": "object",
"properties": {
"class": { "type": "string", "enum": [ "port_relation" ] },
"parent": { "$ref": "#/$defs/keyRef" },
"child": { "$ref": "#/$defs/keyRef" }
},
"required": [ "parent", "child" ]
},
"logical_connection_relation": {
"type": "object",
"properties": {
"class": { "type": "string", "enum": [ "logical_connection_relation" ] },
"sequence": { "type": [ "integer", "null" ], "minimum": 1 },
"route": { "type": [ "integer", "null" ], "minimum": 1 },
"parent": { "$ref": "#/$defs/keyRef" },
"child": { "$ref": "#/$defs/keyRef" }
},
"required": [ "parent", "child" ]
},
"network_topology": {
"type": "object",
"properties": {
"class": { "type": "string", "enum": [ "network_topology" ] },
"key": { "type": "string" },
"name": { "type": "string" },
"model_name": { "type": [ "string", "null" ] },
"devices": { "type": "array", "items": { "key": "#/$defs/optionalKeyRef" } },
"logical_connections": { "type": "array", "items": { "key": "#/$defs/optionalKeyRef" } }
},
"required": [ "key", "name", "devices", "logical_connections" ]
}
}
}
```
## 2. Decouple Connectivity from ETL
Ensure flexibility by separating device interaction logic from transformation logic (ETL ingestion). Users can develop their own collectors independently of the ETL logic.
Ensure the following points:
1. Design collectors to focus only on connectivity and data conversion to the unified schema.
2. Use or reuse any EMS/NMS adaptor (including third-party adaptors like Atrinet).
3. Push the standardized data into ServiceNow import sets.
## 3. Configure Generic ETL for CMDB Updates
Use a single reusable ETL to process all standardized import sets and update the CMDB accurately.
Ensure the following points:
1. Validate the import set contains data in the standardized JSON format.
2. Use the TSOM Generic ETL to:
* Detect the entity type (e.g., Slot, Card, Logical Interface).
* Map each entity to the correct CI class based on model mapping logic.
* Populate fields including Inventory Category where applicable.
Special Handling:
* Logical Interfaces → Port table (`virtual=true`)
* Logical Connections → Logical Connection table
* PDU Cards → PDU table
* Equipment → Model-based CI class (most recent mapping if multiple exist)
## 4. Configure support for Multi-Chassis and Composite Devices
Model complex devices such as multi-chassis routers with correct CMDB relationships.
Ensure the following points:
1. Use the Logical Composite construct to represent grouped entities like Router + PDU.
2. Define individual components (Fan, Management, Slot) under their respective hierarchy.
3. Map each entity as per the TNI modeling guidance.
Example: For a 7750-2s multi-chassis device:
* Logical Composite → contains Router and PDU
* PDU → contains Slots → Cards → Sub-slots
## 5. Enable TNI Entity Creation Based on Installation
Ensure consistency with TNI standards without unnecessary record creation.
Ensure the following points:
* If TNI is installed:
+ Automatically create a TNI Entity for each discovered CI.
+ Set Inventory Category appropriately (e.g., "Logical Connection", "Interface").
* If TNI is not installed: Skip TNI entity creation to avoid orphaned or invalid records.
|
https://www.servicenow.com/docs/en-US/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/service-graph-connector-for-nokia-altiplano.html | https://servicenow-be-prod.servicenow.com/api/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/service-graph-connector-for-nokia-altiplano.html | 2025-08-02 | daily | 0.5 | 268.xml | en-US | zurich-telecom-service-ops | product/tmt-telecom-service-operations-mgt/concept/service-graph-connector-for-nokia-altiplano.html | zurich | Telecom Discovery via Nokia Altiplano | The Service Graph Connector for Nokia Altiplano offers a telecom-aware integration that brings real-time network inventory from the Nokia Altiplano Access Network SDN Controller into your ServiceNow CMDB. | [] | [
"Telecommunications Service Operations Management",
"Exploring Telecommunications Service Operations Management",
"Telecom Visibility",
"Telecom Discovery",
"Indirect Discovery using Service Graph Connectors"
] | <article class="hascomments" data-page="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/service-graph-connector-for-nokia-altiplano.html" id="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/service-graph-connector-for-nokia-altiplano.html"><body><main role="main"><article role="article" class="dita" aria-labelledby="title_service-graph-connector-for-nokia-altiplano"><article class="nested0" aria-labelledby="title_service-graph-connector-for-nokia-altiplano" id="service-graph-connector-for-nokia-altiplano">
<h1 class="title topictitle1" id="title_service-graph-connector-for-nokia-altiplano">Telecom Discovery via Nokia Altiplano</h1>
<div class="body conbody"><p class="shortdesc">The Service Graph Connector for Nokia Altiplano offers a telecom-aware integration that brings real-time network inventory from the Nokia Altiplano Access Network SDN Controller into your ServiceNow CMDB.</p>
<p class="p">Designed for service providers and telecom enterprises, this connector enables complete visibility, control, and synchronization of your physical and logical network infrastructure. This integration uses REST APIs and a MID Server to
deliver a telecom-model-aligned view of your network, enabling more accurate service modeling, inventory management, and operational efficiency.</p>
<section class="section" id="service-graph-connector-for-nokia-altiplano__section_bqr_q1x_vfc"><h2 id="d8683e49" class="title sectiontitle">Key benefits</h2>
<div class="p">
<ul class="ul" id="service-graph-connector-for-nokia-altiplano__ul_i2f_4bx_vfc">
<li class="li">Accurate inventory synchronization: Automatically populate the CMDB with up-to-date physical and logical inventory from Nokia Altiplano using secure, REST API-based ingestion. This includes OLTs, ONUs/ONTs, interface cards, ports,
slots, and logical connections.</li>
<li class="li">Telecom-Aware CI modeling: Model your network infrastructure in a telecom-aligned format using purpose-built CI classes and relationships. The connector ensures the accurate representation of devices and their
dependencies—mirroring your actual network topology.</li>
<li class="li">Simplified and Guided Setup: Reduce time-to-value with a built-in guided setup that walks you through connection configuration, data source management, and import scheduling with ease.</li>
<li class="li">Flexible discovery options: Choose how and when to run discovery based on your needs—whether it’s full bulk loads, targeted filtered discovery, or phased OLT-only imports. Apply custom filters by device IP or name.</li>
<li class="li">Multi-Instance support: Scale effortlessly by onboarding multiple Altiplano instances independently. Configure connection aliases and define import schedules per instance for complete operational flexibility.</li>
</ul>
</div>
<div class="note note note_note"><span class="note__title">Note:</span> Supported Nokia Altiplano Controller minimum version is 24.6. For a general overview of Service Graph Connector technology, see <a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/concept//csh" href="https://servicenow-be-prod.servicenow.com/csh?topicname=cmdb-sgc-intro&version=zurich&pubname=zurich-servicenow-platform" class="xref">Getting started with Service Graph Connectors</a>.</div>
</section>
<section class="section" id="service-graph-connector-for-nokia-altiplano__section_tdk_v1g_12c"><h2 id="d8683e82" class="title sectiontitle">Nokia Altiplano SGC Architecture</h2><p class="p">The following infographic helps you understand the architecture of Nokia Altiplano service graph connector.</p><img src="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/../images/telecom-service-graph-connector-nokia-altiplano.png?_LANG=enus" class="image" id="service-graph-connector-for-nokia-altiplano__image_rfq_y1j_b2c" alt="Nokia altiplano architecture."/></section>
<section class="section" id="service-graph-connector-for-nokia-altiplano__section_snt_jbg_12c"><h2 id="d8683e94" class="title sectiontitle">Use cases</h2>
<div class="p">The following are examples on how you can use the Nokia Altiplano Service Graph Connector:<ul class="ul" id="service-graph-connector-for-nokia-altiplano__ul_xpq_1dg_12c">
<li class="li">Automatically ingest and structure network data into ServiceNow’s CMDB for both physical and logical network elements: This creates a telecom-model-aligned CMDB view that mirrors your live network environment.<ul class="ul" id="service-graph-connector-for-nokia-altiplano__ul_n4p_1cx_vfc">
<li class="li">Physical Components: OLTs, ONUs/ONTs, slots, subslots, cards, and ports</li>
<li class="li">Logical Components: Logical ports, VLANs, Link Aggregation Groups (LAGs), and logical paths between devices</li>
</ul></li>
<li class="li">Maintain the integrity of your network data with scheduled, automated reconciliation that:<ul class="ul" id="service-graph-connector-for-nokia-altiplano__ul_c5n_tnx_vfc">
<li class="li">Detects and responds to real-time changes</li>
<li class="li">Prevents data drift or stale records</li>
<li class="li">Supports operational processes like service assurance, order fulfillment, and network planning</li>
</ul></li>
<li class="li">Discover beyond physical infrastructure by capturing and managing logical connectivity within ServiceNow:<ul class="ul" id="service-graph-connector-for-nokia-altiplano__ul_k3d_vnx_vfc">
<li class="li">Identify and model logical ports, LAGs, and logical paths like PON and VLAN connections</li>
<li class="li">Link logical CIs with physical components using parent-child and member-of relationships</li>
<li class="li">Enhance diagnostics, impact analysis, and service modeling by visualizing end-to-end logical topologies</li>
</ul></li>
<li class="li">Leverage ServiceNow’s built-in Extract, Transform, Load (ETL) framework to simplify and accelerate integration:<ul class="ul" id="service-graph-connector-for-nokia-altiplano__ul_jn1_ynx_vfc">
<li class="li">Predefined transformation maps and CI class definitions reduce development overhead</li>
<li class="li">Reuse existing CMDB structures to minimize customization</li>
<li class="li">Rapidly onboard new Altiplano instances and scale across your network infrastructure</li>
</ul></li>
</ul></div>
</section>
<section class="section" id="service-graph-connector-for-nokia-altiplano__section_o4p_1cx_vfc"><h2 id="d8683e158" class="title sectiontitle">Key capabilities and components</h2>
<div class="p">
<div class="table-wrap"><table count-columns="3" class="table frame-all" id="service-graph-connector-for-nokia-altiplano__table_nxg_1vx_vfc"><caption><span class="table--title-label">Table 1. </span><span class="title">Key capabilities and components</span></caption><colgroup><col style="width:33.33333333333333%"/><col style="width:33.33333333333333%"/><col style="width:33.33333333333333%"/></colgroup><thead class="thead">
<tr class="row">
<th class="entry colsep-1 rowsep-1" id="service-graph-connector-for-nokia-altiplano__table_nxg_1vx_vfc__entry__1">Capability</th>
<th class="entry colsep-1 rowsep-1" id="service-graph-connector-for-nokia-altiplano__table_nxg_1vx_vfc__entry__2">Description</th>
<th class="entry colsep-1 rowsep-1" id="service-graph-connector-for-nokia-altiplano__table_nxg_1vx_vfc__entry__3">Supporting component</th>
</tr>
</thead><tbody class="tbody">
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="service-graph-connector-for-nokia-altiplano__table_nxg_1vx_vfc__entry__1">Telecom-aware CMDB modeling</td>
<td class="entry colsep-1 rowsep-1" headers="service-graph-connector-for-nokia-altiplano__table_nxg_1vx_vfc__entry__2">Maps Altiplano physical and logical inventory (OLT, ONU/ONT, ports, slots, cards, interfaces) into CMDB with telecom-specific CI classes and relationships.</td>
<td class="entry colsep-1 rowsep-1" headers="service-graph-connector-for-nokia-altiplano__table_nxg_1vx_vfc__entry__3">RTE, IRE, CMDB tables (<code class="ph codeph">cmdb_ci_optical_line_terminal</code>, <code class="ph codeph">cmdb_ci_optical_network_terminal</code>, etc.)</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="service-graph-connector-for-nokia-altiplano__table_nxg_1vx_vfc__entry__1">Automated data ingestion</td>
<td class="entry colsep-1 rowsep-1" headers="service-graph-connector-for-nokia-altiplano__table_nxg_1vx_vfc__entry__2">Retrieves device inventory from Nokia Altiplano via REST APIs with secure, scheduled imports.</td>
<td class="entry colsep-1 rowsep-1" headers="service-graph-connector-for-nokia-altiplano__table_nxg_1vx_vfc__entry__3">MID Server, Data Sources (SGC-Nokia Altiplano Bulk/Filtered Discovery)</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="service-graph-connector-for-nokia-altiplano__table_nxg_1vx_vfc__entry__1">Custom discovery control</td>
<td class="entry colsep-1 rowsep-1" headers="service-graph-connector-for-nokia-altiplano__table_nxg_1vx_vfc__entry__2">Choose OLT-only or include ONU data, apply filters by IP or name, schedule jobs per instance.</td>
<td class="entry colsep-1 rowsep-1" headers="service-graph-connector-for-nokia-altiplano__table_nxg_1vx_vfc__entry__3">Import Schedules, System Properties (<code class="ph codeph">sn_sgc_altiplano.enable_onu_discovery</code>, etc.)</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="service-graph-connector-for-nokia-altiplano__table_nxg_1vx_vfc__entry__1">Multi-instance support</td>
<td class="entry colsep-1 rowsep-1" headers="service-graph-connector-for-nokia-altiplano__table_nxg_1vx_vfc__entry__2">Configure and manage discovery independently for multiple Altiplano controllers.</td>
<td class="entry colsep-1 rowsep-1" headers="service-graph-connector-for-nokia-altiplano__table_nxg_1vx_vfc__entry__3">Connection Aliases, Credential Aliases</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="service-graph-connector-for-nokia-altiplano__table_nxg_1vx_vfc__entry__1">Parallel data processing</td>
<td class="entry colsep-1 rowsep-1" headers="service-graph-connector-for-nokia-altiplano__table_nxg_1vx_vfc__entry__2">Improve performance by running concurrent data-source jobs for large datasets.</td>
<td class="entry colsep-1 rowsep-1" headers="service-graph-connector-for-nokia-altiplano__table_nxg_1vx_vfc__entry__3">System Property: <code class="ph codeph">sn_sgc_altiplano.parallel_number_of_data_source_jobs</code>, Enable Parallel Loading</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="service-graph-connector-for-nokia-altiplano__table_nxg_1vx_vfc__entry__1">Guided configuration</td>
<td class="entry colsep-1 rowsep-1" headers="service-graph-connector-for-nokia-altiplano__table_nxg_1vx_vfc__entry__2">Simplifies setup with step-by-step interface for creating connections, credentials, and jobs.</td>
<td class="entry colsep-1 rowsep-1" headers="service-graph-connector-for-nokia-altiplano__table_nxg_1vx_vfc__entry__3">Guided Setup UI (Navigation: All > Service Graph Connectors > Nokia Altiplano > Setup)</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="service-graph-connector-for-nokia-altiplano__table_nxg_1vx_vfc__entry__1">Model-driven CI classification</td>
<td class="entry colsep-1 rowsep-1" headers="service-graph-connector-for-nokia-altiplano__table_nxg_1vx_vfc__entry__2">Matches discovered devices to models and assigns correct CI class (OLT, ONU, ONT), or falls back to Network Gear.</td>
<td class="entry colsep-1 rowsep-1" headers="service-graph-connector-for-nokia-altiplano__table_nxg_1vx_vfc__entry__3">Model Tables, System Property: <code class="ph codeph">sn_sgc_altiplano.onu_ci_class</code></td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="service-graph-connector-for-nokia-altiplano__table_nxg_1vx_vfc__entry__1">Relationship</td>
<td class="entry colsep-1 rowsep-1" headers="service-graph-connector-for-nokia-altiplano__table_nxg_1vx_vfc__entry__2">Establishes telecom-specific CI relationships (e.g., member-of, contains, logical path).</td>
<td class="entry colsep-1 rowsep-1" headers="service-graph-connector-for-nokia-altiplano__table_nxg_1vx_vfc__entry__3">IRE, Logical Connections CI (<code class="ph codeph">cmdb_ci_ni_logical_path</code>)</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="service-graph-connector-for-nokia-altiplano__table_nxg_1vx_vfc__entry__1">Dashboards and monitoring</td>
<td class="entry colsep-1 rowsep-1" headers="service-graph-connector-for-nokia-altiplano__table_nxg_1vx_vfc__entry__2">View status, results, and errors of each run; filter by connector or timeframe.</td>
<td class="entry colsep-1 rowsep-1" headers="service-graph-connector-for-nokia-altiplano__table_nxg_1vx_vfc__entry__3">Integration Commons for CMDB Dashboard</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="service-graph-connector-for-nokia-altiplano__table_nxg_1vx_vfc__entry__1">Scalable and reusable architecture</td>
<td class="entry colsep-1 rowsep-1" headers="service-graph-connector-for-nokia-altiplano__table_nxg_1vx_vfc__entry__2">Decoupled data sources, transformation, and CI reconciliation for easy scaling and customization.</td>
<td class="entry colsep-1 rowsep-1" headers="service-graph-connector-for-nokia-altiplano__table_nxg_1vx_vfc__entry__3">Import Sets (<code class="ph codeph">sn_sgc_altiplano_tsom_inventory</code>), Transformation Maps, System Properties</td>
</tr>
</tbody></table></div>
</div>
</section>
<section class="section" id="service-graph-connector-for-nokia-altiplano__section_r14_jdg_12c"><h2 id="d8683e342" class="title sectiontitle">CMDB Integrations Dashboard</h2>
<p class="p">The Integration Commons for CMDB store app provides a dashboard with a central view of the status, processing results, and processing errors of all installed Service Graph Connectors. You can see metrics for all integration runs. You
can filter the view to a specific integration, a specific time duration, or a specific integration run. For more details about monitoring integrations in the CMDB Integrations Dashboard, see <a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/concept//csh" href="https://servicenow-be-prod.servicenow.com/csh?topicname=integration-commons-for-cmdb&version=zurich&pubname=zurich-servicenow-platform" class="xref">Integration Commons for CMDB</a>.</p>
</section>
</div>
<nav role="navigation"></nav><nav role="navigation" class="tasksNavigation"></nav><nav role="navigation" class="related-links"><div class="col-md-4"><dt>Related concepts</dt><dd><ul><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/concept/configuring-service-graph-connector-nokia-altiplano.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/configuring-service-graph-connector-nokia-altiplano.html" class="link" title="Configure the Nokia Altiplano service graph connector to import physical and logical inventory data from the Nokia Altiplano Access Network SDN Controller into your ServiceNow Configuration Management Database (CMDB).">Configuring Nokia Altiplano service graph connector</a></li></ul></dd></div><div class="col-md-4"><dt>Related reference</dt><dd><ul><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/reference/properties-installed-with-nokia-altiplano.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/reference/properties-installed-with-nokia-altiplano.html" class="link" title="System properties control how the connector operates, including discovery options and performance settings.">System components installed with Nokia Altiplano</a></li></ul></dd></div></nav>
</article></article></main></body></article> | {
"attachments": {
"all_attachments": null,
"topic_attachments": []
},
"available_languages": [
"enus"
],
"breadcrumbs": [
{
"title": "Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html"
},
{
"title": "Exploring Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/exploring-tsom.html"
},
{
"title": "Telecom Visibility",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/tsom-visibility.html"
},
{
"title": "Telecom Discovery",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/exploring-telecom-discovery.html"
},
{
"title": "Indirect Discovery using Service Graph Connectors",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/telecom-discovery-using-service-graph-connector.html"
}
],
"breadcrumbs_html": "<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops\">Zurich Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html\">Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/exploring-tsom.html\">Exploring Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/tsom-visibility.html\">Telecom Visibility</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/exploring-telecom-discovery.html\">Telecom Discovery</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/telecom-discovery-using-service-graph-connector.html\">Indirect Discovery using Service Graph Connectors</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<span class=\"active\">Telecom Discovery via Nokia Altiplano</span>",
"bundle_id": "zurich-telecom-service-ops",
"bundle_key": 2733,
"bundle_landing_page": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html",
"bundle_subtitle": null,
"bundle_title": "Zurich Telecommunications Service Operations Management",
"canonical_link": null,
"dates": {
"Added on": "2025-08-02T00:48:08.794016Z",
"Created on": "2024-12-06T00:00:00Z",
"Initial upload": "2025-07-30T22:24:33.519043Z",
"Updated on": "2025-07-31T00:00:00Z"
},
"dislike_url": "https://servicenow-be-prod.servicenow.com/dislike/55686938",
"dislikes": 0,
"es_archived_content": false,
"is_in_fav": false,
"is_liked": null,
"is_watched": false,
"keywords": [
" zurich zurich"
],
"labels": [
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "zurich",
"navtitle": "Zurich",
"outputclasses": [],
"subjectHeadId": "versions",
"subjectheadNavtitle": "Versions",
"visibility": "show-facet"
},
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "tsom",
"navtitle": "Telecommunications Service Operations Management",
"outputclasses": [],
"subjectHeadId": "products",
"subjectheadNavtitle": "Products",
"visibility": "show-facet"
}
],
"labels_text": "Versions > Zurich; Products > CRM and Industry Products > Telecommunications Media and Technology Assurance > Telecommunications Service Operations Management",
"like_url": "https://servicenow-be-prod.servicenow.com/like/55686938",
"likes": 0,
"metadata": {
"AI Search": null,
"AI Search Assist": null,
"Application Insights": null,
"Capabilities": null,
"Code Signing": null,
"Contextual Search": null,
"DC.contributor": null,
"DC.coverage": null,
"DC.creator": "ServiceNow",
"DC.date.created": "2024-12-06T11:55:52+05:30",
"DC.date.modified": "2025-07-31",
"DC.format": "HTML5",
"DC.identifier": "service-graph-connector-for-nokia-altiplano",
"DC.language": null,
"DC.relation": "configuring-service-graph-connector-nokia-altiplano.html",
"DC.rights.owner": "(C) Copyright 2025",
"DC.subject": null,
"DC.type": "dita",
"Data Discovery": null,
"Data Policy": null,
"Data Privacy": null,
"Discovery": null,
"External Content for AI Search": null,
"Field Administration": null,
"Field Normalization": null,
"Key Management Framework": null,
"Localization Framework": null,
"Now Platform": null,
"PlatSec": null,
"Platform": null,
"Platform Administration": null,
"Platform Performance": null,
"Platform Privacy": null,
"Proactive Triggers": null,
"Process Optimization": null,
"RN doc editing record number": null,
"Search Administration": null,
"Secrets Management": null,
"ServiceNow AI Platform": null,
"State Model": null,
"Subscription Management": null,
"Task Communications Management": null,
"Timeline Visualizations": null,
"User Administration": null,
"User Experience Analytics": null,
"Zing": null,
"ai-now-assist": null,
"app-name": null,
"app_route": null,
"azureapimanagemen": null,
"change-completed": null,
"change-item": null,
"change-request-id": null,
"change-request-reference": null,
"com.glide.embedded_help.category": null,
"component": null,
"copyright": "(C) Copyright 2025",
"crossroads": null,
"data": null,
"description": "The Service Graph Connector for Nokia Altiplano offers a telecom-aware integration that brings real-time network inventory from the Nokia Altiplano Access Network SDN Controller into your ServiceNow CMDB.",
"dominant_bundle": null,
"erp-canvas-video": null,
"fsm-mobile": null,
"fsm-route": null,
"fsm-sched-opt": null,
"fsm-wrk-order": null,
"genai-round-7": null,
"generator": "DITA-OT",
"glossPartOfSpeech": null,
"glossStatus": null,
"guided setup": null,
"guided tours": null,
"keywords": null,
"min-toc": null,
"mini": null,
"mini-to truec": null,
"mini-toc": "yes",
"mini_toc": null,
"minitoc": null,
"modification": null,
"now-assist-app-gen-video": null,
"order": null,
"page-type": null,
"page-type ": null,
"prodname": null,
"product": null,
"product_name": null,
"release": null,
"resourceID": null,
"roles": null,
"route_page": null,
"route_params_listId": null,
"route_params_table": null,
"route_params_type": null,
"route_type": null,
"setconfigurationproperties": null,
"topic": null,
"translation-type": "source",
"version": null,
"workflow": "Customer and Industry",
"workplace-srvc-delvry-ditamap": null
},
"page_id": "product/tmt-telecom-service-operations-mgt/concept/service-graph-connector-for-nokia-altiplano.html",
"page_key": 55686938,
"preprocessed_PDF": "https://downloads.docs.servicenow.com/pdf/enus/servicenow-zurich-telecom-service-ops-enus.pdf",
"rating": null,
"read_time_data": {
"char_count": 6051,
"img_count": 1,
"read_time": 4,
"video_links": [
""
],
"word_count": 779
},
"related_links": [
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "Configure the Nokia Altiplano service graph connector to import physical and logical inventory data from the Nokia Altiplano Access Network SDN Controller into your ServiceNow Configuration Management Database (CMDB).",
"title": "Configuring Nokia Altiplano service graph connector",
"topic": "/product/tmt-telecom-service-operations-mgt/concept/configuring-service-graph-connector-nokia-altiplano.html",
"type": "concept",
"url": null
},
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "System properties control how the connector operates, including discovery options and performance settings.",
"title": "System components installed with Nokia Altiplano",
"topic": "/product/tmt-telecom-service-operations-mgt/reference/properties-installed-with-nokia-altiplano.html",
"type": "reference",
"url": null
}
],
"search_title": null,
"title": "Telecom Discovery via Nokia Altiplano",
"topic_cluster": {
"clustered_by": {
"enabled": true,
"primary_key": "versions",
"primary_sort": "top-down",
"type": "subjecthead"
},
"clustered_labels": [
"versions"
],
"clustered_topics": [
{
"bundle_id": "yokohama-telecom-service-ops",
"clustering_title": "Yokohama",
"es_archived_content": false,
"page_id": "product/tmt-telecom-service-operations-mgt/concept/service-graph-connector-for-nokia-altiplano.html"
}
],
"clustering_title": "Zurich"
},
"topic_html": "<article class=\"hascomments\" data-page=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/service-graph-connector-for-nokia-altiplano.html\" id=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/service-graph-connector-for-nokia-altiplano.html\"><body><main role=\"main\"><article role=\"article\" class=\"dita\" aria-labelledby=\"title_service-graph-connector-for-nokia-altiplano\"><article class=\"nested0\" aria-labelledby=\"title_service-graph-connector-for-nokia-altiplano\" id=\"service-graph-connector-for-nokia-altiplano\">\n <h1 class=\"title topictitle1\" id=\"title_service-graph-connector-for-nokia-altiplano\">Telecom Discovery via Nokia Altiplano</h1>\n \n \n <div class=\"body conbody\"><p class=\"shortdesc\">The Service Graph Connector for Nokia Altiplano offers a telecom-aware integration that brings real-time network inventory from the Nokia Altiplano Access Network SDN Controller into your ServiceNow CMDB.</p>\n <p class=\"p\">Designed for service providers and telecom enterprises, this connector enables complete visibility, control, and synchronization of your physical and logical network infrastructure. This integration uses REST APIs and a MID Server to\n deliver a telecom-model-aligned view of your network, enabling more accurate service modeling, inventory management, and operational efficiency.</p>\n <section class=\"section\" id=\"service-graph-connector-for-nokia-altiplano__section_bqr_q1x_vfc\"><h2 id=\"d8683e49\" class=\"title sectiontitle\">Key benefits</h2>\n \n <div class=\"p\">\n <ul class=\"ul\" id=\"service-graph-connector-for-nokia-altiplano__ul_i2f_4bx_vfc\">\n <li class=\"li\">Accurate inventory synchronization: Automatically populate the CMDB with up-to-date physical and logical inventory from Nokia Altiplano using secure, REST API-based ingestion. This includes OLTs, ONUs/ONTs, interface cards, ports,\n slots, and logical connections.</li>\n <li class=\"li\">Telecom-Aware CI modeling: Model your network infrastructure in a telecom-aligned format using purpose-built CI classes and relationships. The connector ensures the accurate representation of devices and their\n dependencies—mirroring your actual network topology.</li>\n <li class=\"li\">Simplified and Guided Setup: Reduce time-to-value with a built-in guided setup that walks you through connection configuration, data source management, and import scheduling with ease.</li>\n <li class=\"li\">Flexible discovery options: Choose how and when to run discovery based on your needs—whether it’s full bulk loads, targeted filtered discovery, or phased OLT-only imports. Apply custom filters by device IP or name.</li>\n <li class=\"li\">Multi-Instance support: Scale effortlessly by onboarding multiple Altiplano instances independently. Configure connection aliases and define import schedules per instance for complete operational flexibility.</li>\n </ul>\n </div>\n <div class=\"note note note_note\"><span class=\"note__title\">Note:</span> Supported Nokia Altiplano Controller minimum version is 24.6. For a general overview of Service Graph Connector technology, see <a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept//csh\" href=\"https://servicenow-be-prod.servicenow.com/csh?topicname=cmdb-sgc-intro&version=zurich&pubname=zurich-servicenow-platform\" class=\"xref\">Getting started with Service Graph Connectors</a>.</div>\n </section>\n <section class=\"section\" id=\"service-graph-connector-for-nokia-altiplano__section_tdk_v1g_12c\"><h2 id=\"d8683e82\" class=\"title sectiontitle\">Nokia Altiplano SGC Architecture</h2><p class=\"p\">The following infographic helps you understand the architecture of Nokia Altiplano service graph connector.</p><img src=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/../images/telecom-service-graph-connector-nokia-altiplano.png?_LANG=enus\" class=\"image\" id=\"service-graph-connector-for-nokia-altiplano__image_rfq_y1j_b2c\" alt=\"Nokia altiplano architecture.\"/></section>\n <section class=\"section\" id=\"service-graph-connector-for-nokia-altiplano__section_snt_jbg_12c\"><h2 id=\"d8683e94\" class=\"title sectiontitle\">Use cases</h2>\n \n <div class=\"p\">The following are examples on how you can use the Nokia Altiplano Service Graph Connector:<ul class=\"ul\" id=\"service-graph-connector-for-nokia-altiplano__ul_xpq_1dg_12c\">\n <li class=\"li\">Automatically ingest and structure network data into ServiceNow’s CMDB for both physical and logical network elements: This creates a telecom-model-aligned CMDB view that mirrors your live network environment.<ul class=\"ul\" id=\"service-graph-connector-for-nokia-altiplano__ul_n4p_1cx_vfc\">\n <li class=\"li\">Physical Components: OLTs, ONUs/ONTs, slots, subslots, cards, and ports</li>\n <li class=\"li\">Logical Components: Logical ports, VLANs, Link Aggregation Groups (LAGs), and logical paths between devices</li>\n </ul></li>\n <li class=\"li\">Maintain the integrity of your network data with scheduled, automated reconciliation that:<ul class=\"ul\" id=\"service-graph-connector-for-nokia-altiplano__ul_c5n_tnx_vfc\">\n <li class=\"li\">Detects and responds to real-time changes</li>\n <li class=\"li\">Prevents data drift or stale records</li>\n <li class=\"li\">Supports operational processes like service assurance, order fulfillment, and network planning</li>\n </ul></li>\n <li class=\"li\">Discover beyond physical infrastructure by capturing and managing logical connectivity within ServiceNow:<ul class=\"ul\" id=\"service-graph-connector-for-nokia-altiplano__ul_k3d_vnx_vfc\">\n <li class=\"li\">Identify and model logical ports, LAGs, and logical paths like PON and VLAN connections</li>\n <li class=\"li\">Link logical CIs with physical components using parent-child and member-of relationships</li>\n <li class=\"li\">Enhance diagnostics, impact analysis, and service modeling by visualizing end-to-end logical topologies</li>\n </ul></li>\n <li class=\"li\">Leverage ServiceNow’s built-in Extract, Transform, Load (ETL) framework to simplify and accelerate integration:<ul class=\"ul\" id=\"service-graph-connector-for-nokia-altiplano__ul_jn1_ynx_vfc\">\n <li class=\"li\">Predefined transformation maps and CI class definitions reduce development overhead</li>\n <li class=\"li\">Reuse existing CMDB structures to minimize customization</li>\n <li class=\"li\">Rapidly onboard new Altiplano instances and scale across your network infrastructure</li>\n </ul></li>\n </ul></div>\n </section>\n <section class=\"section\" id=\"service-graph-connector-for-nokia-altiplano__section_o4p_1cx_vfc\"><h2 id=\"d8683e158\" class=\"title sectiontitle\">Key capabilities and components</h2>\n \n <div class=\"p\">\n <div class=\"table-wrap\"><table count-columns=\"3\" class=\"table frame-all\" id=\"service-graph-connector-for-nokia-altiplano__table_nxg_1vx_vfc\"><caption><span class=\"table--title-label\">Table 1. </span><span class=\"title\">Key capabilities and components</span></caption><colgroup><col style=\"width:33.33333333333333%\"/><col style=\"width:33.33333333333333%\"/><col style=\"width:33.33333333333333%\"/></colgroup><thead class=\"thead\">\n <tr class=\"row\">\n <th class=\"entry colsep-1 rowsep-1\" id=\"service-graph-connector-for-nokia-altiplano__table_nxg_1vx_vfc__entry__1\">Capability</th>\n <th class=\"entry colsep-1 rowsep-1\" id=\"service-graph-connector-for-nokia-altiplano__table_nxg_1vx_vfc__entry__2\">Description</th>\n <th class=\"entry colsep-1 rowsep-1\" id=\"service-graph-connector-for-nokia-altiplano__table_nxg_1vx_vfc__entry__3\">Supporting component</th>\n </tr>\n </thead><tbody class=\"tbody\">\n <tr class=\"row\">\n <td class=\"entry colsep-1 rowsep-1\" headers=\"service-graph-connector-for-nokia-altiplano__table_nxg_1vx_vfc__entry__1\">Telecom-aware CMDB modeling</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"service-graph-connector-for-nokia-altiplano__table_nxg_1vx_vfc__entry__2\">Maps Altiplano physical and logical inventory (OLT, ONU/ONT, ports, slots, cards, interfaces) into CMDB with telecom-specific CI classes and relationships.</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"service-graph-connector-for-nokia-altiplano__table_nxg_1vx_vfc__entry__3\">RTE, IRE, CMDB tables (<code class=\"ph codeph\">cmdb_ci_optical_line_terminal</code>, <code class=\"ph codeph\">cmdb_ci_optical_network_terminal</code>, etc.)</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry colsep-1 rowsep-1\" headers=\"service-graph-connector-for-nokia-altiplano__table_nxg_1vx_vfc__entry__1\">Automated data ingestion</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"service-graph-connector-for-nokia-altiplano__table_nxg_1vx_vfc__entry__2\">Retrieves device inventory from Nokia Altiplano via REST APIs with secure, scheduled imports.</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"service-graph-connector-for-nokia-altiplano__table_nxg_1vx_vfc__entry__3\">MID Server, Data Sources (SGC-Nokia Altiplano Bulk/Filtered Discovery)</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry colsep-1 rowsep-1\" headers=\"service-graph-connector-for-nokia-altiplano__table_nxg_1vx_vfc__entry__1\">Custom discovery control</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"service-graph-connector-for-nokia-altiplano__table_nxg_1vx_vfc__entry__2\">Choose OLT-only or include ONU data, apply filters by IP or name, schedule jobs per instance.</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"service-graph-connector-for-nokia-altiplano__table_nxg_1vx_vfc__entry__3\">Import Schedules, System Properties (<code class=\"ph codeph\">sn_sgc_altiplano.enable_onu_discovery</code>, etc.)</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry colsep-1 rowsep-1\" headers=\"service-graph-connector-for-nokia-altiplano__table_nxg_1vx_vfc__entry__1\">Multi-instance support</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"service-graph-connector-for-nokia-altiplano__table_nxg_1vx_vfc__entry__2\">Configure and manage discovery independently for multiple Altiplano controllers.</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"service-graph-connector-for-nokia-altiplano__table_nxg_1vx_vfc__entry__3\">Connection Aliases, Credential Aliases</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry colsep-1 rowsep-1\" headers=\"service-graph-connector-for-nokia-altiplano__table_nxg_1vx_vfc__entry__1\">Parallel data processing</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"service-graph-connector-for-nokia-altiplano__table_nxg_1vx_vfc__entry__2\">Improve performance by running concurrent data-source jobs for large datasets.</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"service-graph-connector-for-nokia-altiplano__table_nxg_1vx_vfc__entry__3\">System Property: <code class=\"ph codeph\">sn_sgc_altiplano.parallel_number_of_data_source_jobs</code>, Enable Parallel Loading</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry colsep-1 rowsep-1\" headers=\"service-graph-connector-for-nokia-altiplano__table_nxg_1vx_vfc__entry__1\">Guided configuration</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"service-graph-connector-for-nokia-altiplano__table_nxg_1vx_vfc__entry__2\">Simplifies setup with step-by-step interface for creating connections, credentials, and jobs.</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"service-graph-connector-for-nokia-altiplano__table_nxg_1vx_vfc__entry__3\">Guided Setup UI (Navigation: All > Service Graph Connectors > Nokia Altiplano > Setup)</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry colsep-1 rowsep-1\" headers=\"service-graph-connector-for-nokia-altiplano__table_nxg_1vx_vfc__entry__1\">Model-driven CI classification</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"service-graph-connector-for-nokia-altiplano__table_nxg_1vx_vfc__entry__2\">Matches discovered devices to models and assigns correct CI class (OLT, ONU, ONT), or falls back to Network Gear.</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"service-graph-connector-for-nokia-altiplano__table_nxg_1vx_vfc__entry__3\">Model Tables, System Property: <code class=\"ph codeph\">sn_sgc_altiplano.onu_ci_class</code></td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry colsep-1 rowsep-1\" headers=\"service-graph-connector-for-nokia-altiplano__table_nxg_1vx_vfc__entry__1\">Relationship</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"service-graph-connector-for-nokia-altiplano__table_nxg_1vx_vfc__entry__2\">Establishes telecom-specific CI relationships (e.g., member-of, contains, logical path).</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"service-graph-connector-for-nokia-altiplano__table_nxg_1vx_vfc__entry__3\">IRE, Logical Connections CI (<code class=\"ph codeph\">cmdb_ci_ni_logical_path</code>)</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry colsep-1 rowsep-1\" headers=\"service-graph-connector-for-nokia-altiplano__table_nxg_1vx_vfc__entry__1\">Dashboards and monitoring</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"service-graph-connector-for-nokia-altiplano__table_nxg_1vx_vfc__entry__2\">View status, results, and errors of each run; filter by connector or timeframe.</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"service-graph-connector-for-nokia-altiplano__table_nxg_1vx_vfc__entry__3\">Integration Commons for CMDB Dashboard</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry colsep-1 rowsep-1\" headers=\"service-graph-connector-for-nokia-altiplano__table_nxg_1vx_vfc__entry__1\">Scalable and reusable architecture</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"service-graph-connector-for-nokia-altiplano__table_nxg_1vx_vfc__entry__2\">Decoupled data sources, transformation, and CI reconciliation for easy scaling and customization.</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"service-graph-connector-for-nokia-altiplano__table_nxg_1vx_vfc__entry__3\">Import Sets (<code class=\"ph codeph\">sn_sgc_altiplano_tsom_inventory</code>), Transformation Maps, System Properties</td>\n </tr>\n </tbody></table></div>\n </div>\n </section>\n <section class=\"section\" id=\"service-graph-connector-for-nokia-altiplano__section_r14_jdg_12c\"><h2 id=\"d8683e342\" class=\"title sectiontitle\">CMDB Integrations Dashboard</h2>\n \n <p class=\"p\">The Integration Commons for CMDB store app provides a dashboard with a central view of the status, processing results, and processing errors of all installed Service Graph Connectors. You can see metrics for all integration runs. You\n can filter the view to a specific integration, a specific time duration, or a specific integration run. For more details about monitoring integrations in the CMDB Integrations Dashboard, see <a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept//csh\" href=\"https://servicenow-be-prod.servicenow.com/csh?topicname=integration-commons-for-cmdb&version=zurich&pubname=zurich-servicenow-platform\" class=\"xref\">Integration Commons for CMDB</a>.</p>\n </section>\n </div>\n <nav role=\"navigation\"></nav><nav role=\"navigation\" class=\"tasksNavigation\"></nav><nav role=\"navigation\" class=\"related-links\"><div class=\"col-md-4\"><dt>Related concepts</dt><dd><ul><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept/configuring-service-graph-connector-nokia-altiplano.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/configuring-service-graph-connector-nokia-altiplano.html\" class=\"link\" title=\"Configure the Nokia Altiplano service graph connector to import physical and logical inventory data from the Nokia Altiplano Access Network SDN Controller into your ServiceNow Configuration Management Database (CMDB).\">Configuring Nokia Altiplano service graph connector</a></li></ul></dd></div><div class=\"col-md-4\"><dt>Related reference</dt><dd><ul><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/reference/properties-installed-with-nokia-altiplano.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/reference/properties-installed-with-nokia-altiplano.html\" class=\"link\" title=\"System properties control how the connector operates, including discovery options and performance settings.\">System components installed with Nokia Altiplano</a></li></ul></dd></div></nav>\n</article></article></main></body></article>",
"topic_language": "enus",
"views": 0,
"your_rating": null
} | # Telecom Discovery via Nokia Altiplano
The Service Graph Connector for Nokia Altiplano offers a telecom-aware integration that brings real-time network inventory from the Nokia Altiplano Access Network SDN Controller into your ServiceNow CMDB.
Designed for service providers and telecom enterprises, this connector enables complete visibility, control, and synchronization of your physical and logical network infrastructure. This integration uses REST APIs and a MID Server to
deliver a telecom-model-aligned view of your network, enabling more accurate service modeling, inventory management, and operational efficiency.
## Key benefits
* Accurate inventory synchronization: Automatically populate the CMDB with up-to-date physical and logical inventory from Nokia Altiplano using secure, REST API-based ingestion. This includes OLTs, ONUs/ONTs, interface cards, ports,
slots, and logical connections.
* Telecom-Aware CI modeling: Model your network infrastructure in a telecom-aligned format using purpose-built CI classes and relationships. The connector ensures the accurate representation of devices and their
dependencies—mirroring your actual network topology.
* Simplified and Guided Setup: Reduce time-to-value with a built-in guided setup that walks you through connection configuration, data source management, and import scheduling with ease.
* Flexible discovery options: Choose how and when to run discovery based on your needs—whether it’s full bulk loads, targeted filtered discovery, or phased OLT-only imports. Apply custom filters by device IP or name.
* Multi-Instance support: Scale effortlessly by onboarding multiple Altiplano instances independently. Configure connection aliases and define import schedules per instance for complete operational flexibility.
Note: Supported Nokia Altiplano Controller minimum version is 24.6. For a general overview of Service Graph Connector technology, see Getting started with Service Graph Connectors.
## Nokia Altiplano SGC Architecture
The following infographic helps you understand the architecture of Nokia Altiplano service graph connector.
## Use cases
The following are examples on how you can use the Nokia Altiplano Service Graph Connector:
* Automatically ingest and structure network data into ServiceNow’s CMDB for both physical and logical network elements: This creates a telecom-model-aligned CMDB view that mirrors your live network environment.
+ Physical Components: OLTs, ONUs/ONTs, slots, subslots, cards, and ports
+ Logical Components: Logical ports, VLANs, Link Aggregation Groups (LAGs), and logical paths between devices
* Maintain the integrity of your network data with scheduled, automated reconciliation that:
+ Detects and responds to real-time changes
+ Prevents data drift or stale records
+ Supports operational processes like service assurance, order fulfillment, and network planning
* Discover beyond physical infrastructure by capturing and managing logical connectivity within ServiceNow:
+ Identify and model logical ports, LAGs, and logical paths like PON and VLAN connections
+ Link logical CIs with physical components using parent-child and member-of relationships
+ Enhance diagnostics, impact analysis, and service modeling by visualizing end-to-end logical topologies
* Leverage ServiceNow’s built-in Extract, Transform, Load (ETL) framework to simplify and accelerate integration:
+ Predefined transformation maps and CI class definitions reduce development overhead
+ Reuse existing CMDB structures to minimize customization
+ Rapidly onboard new Altiplano instances and scale across your network infrastructure
## Key capabilities and components
Table 1. Key capabilities and components
| Capability | Description | Supporting component |
| --- | --- | --- |
| Telecom-aware CMDB modeling | Maps Altiplano physical and logical inventory (OLT, ONU/ONT, ports, slots, cards, interfaces) into CMDB with telecom-specific CI classes and relationships. | RTE, IRE, CMDB tables (`cmdb_ci_optical_line_terminal`, `cmdb_ci_optical_network_terminal`, etc.) |
| Automated data ingestion | Retrieves device inventory from Nokia Altiplano via REST APIs with secure, scheduled imports. | MID Server, Data Sources (SGC-Nokia Altiplano Bulk/Filtered Discovery) |
| Custom discovery control | Choose OLT-only or include ONU data, apply filters by IP or name, schedule jobs per instance. | Import Schedules, System Properties (`sn_sgc_altiplano.enable_onu_discovery`, etc.) |
| Multi-instance support | Configure and manage discovery independently for multiple Altiplano controllers. | Connection Aliases, Credential Aliases |
| Parallel data processing | Improve performance by running concurrent data-source jobs for large datasets. | System Property: `sn_sgc_altiplano.parallel_number_of_data_source_jobs`, Enable Parallel Loading |
| Guided configuration | Simplifies setup with step-by-step interface for creating connections, credentials, and jobs. | Guided Setup UI (Navigation: All > Service Graph Connectors > Nokia Altiplano > Setup) |
| Model-driven CI classification | Matches discovered devices to models and assigns correct CI class (OLT, ONU, ONT), or falls back to Network Gear. | Model Tables, System Property: `sn_sgc_altiplano.onu_ci_class` |
| Relationship | Establishes telecom-specific CI relationships (e.g., member-of, contains, logical path). | IRE, Logical Connections CI (`cmdb_ci_ni_logical_path`) |
| Dashboards and monitoring | View status, results, and errors of each run; filter by connector or timeframe. | Integration Commons for CMDB Dashboard |
| Scalable and reusable architecture | Decoupled data sources, transformation, and CI reconciliation for easy scaling and customization. | Import Sets (`sn_sgc_altiplano_tsom_inventory`), Transformation Maps, System Properties |
## CMDB Integrations Dashboard
The Integration Commons for CMDB store app provides a dashboard with a central view of the status, processing results, and processing errors of all installed Service Graph Connectors. You can see metrics for all integration runs. You
can filter the view to a specific integration, a specific time duration, or a specific integration run. For more details about monitoring integrations in the CMDB Integrations Dashboard, see Integration Commons for CMDB.
| ---
title: Telecom Discovery via Nokia Altiplano
description: The Service Graph Connector for Nokia Altiplano offers a telecom-aware
integration that brings real-time network inventory from the Nokia Altiplano Access
Network SDN Controller into your ServiceNow CMDB.
keywords: []
breadcrumbs:
- Telecommunications Service Operations Management
- Exploring Telecommunications Service Operations Management
- Telecom Visibility
- Telecom Discovery
- Indirect Discovery using Service Graph Connectors
---
# Telecom Discovery via Nokia Altiplano
The Service Graph Connector for Nokia Altiplano offers a telecom-aware integration that brings real-time network inventory from the Nokia Altiplano Access Network SDN Controller into your ServiceNow CMDB.
Designed for service providers and telecom enterprises, this connector enables complete visibility, control, and synchronization of your physical and logical network infrastructure. This integration uses REST APIs and a MID Server to
deliver a telecom-model-aligned view of your network, enabling more accurate service modeling, inventory management, and operational efficiency.
## Key benefits
* Accurate inventory synchronization: Automatically populate the CMDB with up-to-date physical and logical inventory from Nokia Altiplano using secure, REST API-based ingestion. This includes OLTs, ONUs/ONTs, interface cards, ports,
slots, and logical connections.
* Telecom-Aware CI modeling: Model your network infrastructure in a telecom-aligned format using purpose-built CI classes and relationships. The connector ensures the accurate representation of devices and their
dependencies—mirroring your actual network topology.
* Simplified and Guided Setup: Reduce time-to-value with a built-in guided setup that walks you through connection configuration, data source management, and import scheduling with ease.
* Flexible discovery options: Choose how and when to run discovery based on your needs—whether it’s full bulk loads, targeted filtered discovery, or phased OLT-only imports. Apply custom filters by device IP or name.
* Multi-Instance support: Scale effortlessly by onboarding multiple Altiplano instances independently. Configure connection aliases and define import schedules per instance for complete operational flexibility.
Note: Supported Nokia Altiplano Controller minimum version is 24.6. For a general overview of Service Graph Connector technology, see Getting started with Service Graph Connectors.
## Nokia Altiplano SGC Architecture
The following infographic helps you understand the architecture of Nokia Altiplano service graph connector.
## Use cases
The following are examples on how you can use the Nokia Altiplano Service Graph Connector:
* Automatically ingest and structure network data into ServiceNow’s CMDB for both physical and logical network elements: This creates a telecom-model-aligned CMDB view that mirrors your live network environment.
+ Physical Components: OLTs, ONUs/ONTs, slots, subslots, cards, and ports
+ Logical Components: Logical ports, VLANs, Link Aggregation Groups (LAGs), and logical paths between devices
* Maintain the integrity of your network data with scheduled, automated reconciliation that:
+ Detects and responds to real-time changes
+ Prevents data drift or stale records
+ Supports operational processes like service assurance, order fulfillment, and network planning
* Discover beyond physical infrastructure by capturing and managing logical connectivity within ServiceNow:
+ Identify and model logical ports, LAGs, and logical paths like PON and VLAN connections
+ Link logical CIs with physical components using parent-child and member-of relationships
+ Enhance diagnostics, impact analysis, and service modeling by visualizing end-to-end logical topologies
* Leverage ServiceNow’s built-in Extract, Transform, Load (ETL) framework to simplify and accelerate integration:
+ Predefined transformation maps and CI class definitions reduce development overhead
+ Reuse existing CMDB structures to minimize customization
+ Rapidly onboard new Altiplano instances and scale across your network infrastructure
## Key capabilities and components
Table 1. Key capabilities and components
| Capability | Description | Supporting component |
| --- | --- | --- |
| Telecom-aware CMDB modeling | Maps Altiplano physical and logical inventory (OLT, ONU/ONT, ports, slots, cards, interfaces) into CMDB with telecom-specific CI classes and relationships. | RTE, IRE, CMDB tables (`cmdb_ci_optical_line_terminal`, `cmdb_ci_optical_network_terminal`, etc.) |
| Automated data ingestion | Retrieves device inventory from Nokia Altiplano via REST APIs with secure, scheduled imports. | MID Server, Data Sources (SGC-Nokia Altiplano Bulk/Filtered Discovery) |
| Custom discovery control | Choose OLT-only or include ONU data, apply filters by IP or name, schedule jobs per instance. | Import Schedules, System Properties (`sn_sgc_altiplano.enable_onu_discovery`, etc.) |
| Multi-instance support | Configure and manage discovery independently for multiple Altiplano controllers. | Connection Aliases, Credential Aliases |
| Parallel data processing | Improve performance by running concurrent data-source jobs for large datasets. | System Property: `sn_sgc_altiplano.parallel_number_of_data_source_jobs`, Enable Parallel Loading |
| Guided configuration | Simplifies setup with step-by-step interface for creating connections, credentials, and jobs. | Guided Setup UI (Navigation: All > Service Graph Connectors > Nokia Altiplano > Setup) |
| Model-driven CI classification | Matches discovered devices to models and assigns correct CI class (OLT, ONU, ONT), or falls back to Network Gear. | Model Tables, System Property: `sn_sgc_altiplano.onu_ci_class` |
| Relationship | Establishes telecom-specific CI relationships (e.g., member-of, contains, logical path). | IRE, Logical Connections CI (`cmdb_ci_ni_logical_path`) |
| Dashboards and monitoring | View status, results, and errors of each run; filter by connector or timeframe. | Integration Commons for CMDB Dashboard |
| Scalable and reusable architecture | Decoupled data sources, transformation, and CI reconciliation for easy scaling and customization. | Import Sets (`sn_sgc_altiplano_tsom_inventory`), Transformation Maps, System Properties |
## CMDB Integrations Dashboard
The Integration Commons for CMDB store app provides a dashboard with a central view of the status, processing results, and processing errors of all installed Service Graph Connectors. You can see metrics for all integration runs. You
can filter the view to a specific integration, a specific time duration, or a specific integration run. For more details about monitoring integrations in the CMDB Integrations Dashboard, see Integration Commons for CMDB.
|
https://www.servicenow.com/docs/en-US/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/system-properties-affecting-telecom-discrepancy-identification-reconciliation.html | https://servicenow-be-prod.servicenow.com/api/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/system-properties-affecting-telecom-discrepancy-identification-reconciliation.html | 2025-08-02 | daily | 0.5 | 268.xml | en-US | zurich-telecom-service-ops | product/tmt-telecom-service-operations-mgt/concept/system-properties-affecting-telecom-discrepancy-identification-reconciliation.html | zurich | System components installed with Telecom Discrepancy Identification & Reconciliation | The system properties are part of the TSOM Visibility plugin (sn_tsom_core) and control the Telecom Discrepancy Identification & Reconciliation log (TSOM CMDB Audit). The TSOM Visibility plugin serves as an enabler for the TSOM Visibility applications, containing logic that is | [] | [
"Telecommunications Service Operations Management",
"Telecommunications Service Operations Management reference"
] | <article class="hascomments" data-page="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/system-properties-affecting-telecom-discrepancy-identification-reconciliation.html" id="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/system-properties-affecting-telecom-discrepancy-identification-reconciliation.html"><body id="system-properties-affecting-telecom-discrepancy-identification-reconciliation"><main role="main"><article role="article" class="dita" id="system-properties-affecting-telecom-discrepancy-identification-reconciliation" aria-labelledby="title_system-properties-affecting-telecom-discrepancy-identification-reconciliation">
<h1 class="title topictitle1" id="title_system-properties-affecting-telecom-discrepancy-identification-reconciliation">System components installed with Telecom Discrepancy Identification & Reconciliation</h1>
<div class="body conbody"><p class="shortdesc">The system properties are part of the TSOM Visibility plugin (sn_tsom_core) and control the Telecom Discrepancy Identification & Reconciliation log (TSOM CMDB Audit). The TSOM Visibility plugin serves as an enabler for the
TSOM Visibility applications, containing logic that is shared across the Telecom Discovery and Telecom Discrepancy Identification & Reconciliation solution.</p>
<div class="p">
<div class="table-wrap"><table count-columns="3" class="table frame-all" id="system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_c1p_wmd_b2c"><caption><span class="table--title-label">Table 1. </span><span class="title">Telecom Discrepancy Identification & Reconciliation System Properties (Impacts CMDB Audit)</span></caption><colgroup><col style="width:220"/><col style="width:161"/><col style="width:244"/></colgroup><thead class="thead">
<tr class="row">
<th class="entry colsep-1 rowsep-1" id="system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_c1p_wmd_b2c__entry__1">Property Name</th>
<th class="entry colsep-1 rowsep-1" id="system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_c1p_wmd_b2c__entry__2">Recommended / Default Value</th>
<th class="entry colsep-1 rowsep-1" id="system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_c1p_wmd_b2c__entry__3">Description</th>
</tr>
</thead><tbody class="tbody">
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_c1p_wmd_b2c__entry__1">sn_tsom_core.audit.log.level</td>
<td class="entry colsep-1 rowsep-1" headers="system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_c1p_wmd_b2c__entry__2">Telecom Discrepancy Audits' Logging.</td>
<td class="entry colsep-1 rowsep-1" headers="system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_c1p_wmd_b2c__entry__3">debug,info,warn <p class="p">Default value: info</p></td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_c1p_wmd_b2c__entry__1">sn_tsom_core.audit.relationship_types</td>
<td class="entry colsep-1 rowsep-1" headers="system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_c1p_wmd_b2c__entry__2">Displayed Names of Relationship Types that will be handled by Telecom Discrepancy Audit.</td>
<td class="entry colsep-1 rowsep-1" headers="system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_c1p_wmd_b2c__entry__3">Comma separated list of relationship types names<p class="p">Default value: Contains::Contained by</p></td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_c1p_wmd_b2c__entry__1">sn_tsom_core.audit.discovered_date.diff.threshold.in.days</td>
<td class="entry colsep-1 rowsep-1" headers="system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_c1p_wmd_b2c__entry__2">Most recent discovered date threshold in days. Used for Telecom Discrepancy Audit.</td>
<td class="entry colsep-1 rowsep-1" headers="system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_c1p_wmd_b2c__entry__3">String<p class="p">Default value: 2.5</p></td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_c1p_wmd_b2c__entry__1">sn_tsom_core.audit.suppress_CI_Model_missing_discrepancy_task_creation</td>
<td class="entry colsep-1 rowsep-1" headers="system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_c1p_wmd_b2c__entry__2">Suppress creation of CI Model missing discrepancy task for the tables.Used for Telecom Discrepancy Audit.</td>
<td class="entry colsep-1 rowsep-1" headers="system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_c1p_wmd_b2c__entry__3">cmdb_ci_ni_telco_equipment, cmdb_ci_ip_switch, cmdb_ci_ip_router, cmdb_ci_container_slot,cmdb_ci_container_subslot,cmdb_ci_interface_card,cmdb_ci_ni_interface</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_c1p_wmd_b2c__entry__1">sn_tsom_core.audit.equipment_tables</td>
<td class="entry colsep-1 rowsep-1" headers="system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_c1p_wmd_b2c__entry__2">Equipment tables that will be handled by Telecom Discrepancy Audit.</td>
<td class="entry colsep-1 rowsep-1" headers="system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_c1p_wmd_b2c__entry__3">Comma separated list of equipment tables names<p class="p">Default value: cmdb_ci_netgear</p></td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_c1p_wmd_b2c__entry__1">sn_tsom_core.audit.interface_card_tables</td>
<td class="entry colsep-1 rowsep-1" headers="system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_c1p_wmd_b2c__entry__2">Interface Cards tables that will be handled by Telecom Discrepancy Audit.</td>
<td class="entry colsep-1 rowsep-1" headers="system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_c1p_wmd_b2c__entry__3">Comma separated list of card tables names.<p class="p">Default value: cmdb_ci_interface_card</p></td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_c1p_wmd_b2c__entry__1">sn_tsom_core.audit.interface_tables</td>
<td class="entry colsep-1 rowsep-1" headers="system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_c1p_wmd_b2c__entry__2">Network Interface tables that will be handled by Telecom Discrepancy Audit.</td>
<td class="entry colsep-1 rowsep-1" headers="system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_c1p_wmd_b2c__entry__3">Comma separated list of interface tables names<p class="p">Default value: cmdb_ci_ni_interface</p></td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_c1p_wmd_b2c__entry__1">sn_tsom_core.audit.slot_tables</td>
<td class="entry colsep-1 rowsep-1" headers="system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_c1p_wmd_b2c__entry__2">Slot tables names that will be handled by Telecom Discrepancy Audit.</td>
<td class="entry colsep-1 rowsep-1" headers="system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_c1p_wmd_b2c__entry__3">Comma separated list of slot tables names<p class="p">Default value: cmdb_ci_container_slot</p></td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_c1p_wmd_b2c__entry__1">sn_tsom_core.audit.subslot_tables</td>
<td class="entry colsep-1 rowsep-1" headers="system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_c1p_wmd_b2c__entry__2">Subslot tables names that will be handled by Telecom Discrepancy Audit.</td>
<td class="entry colsep-1 rowsep-1" headers="system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_c1p_wmd_b2c__entry__3">Comma separated list of subslot tables names<p class="p">Default value is cmdb_ci_container_subslot</p></td>
</tr>
</tbody></table></div>
</div>
<div class="table-wrap"><table count-columns="2" class="table frame-all" id="system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_ydx_rcb_yfc"><caption><span class="table--title-label">Table 2. </span><span class="title">Telecom Discrepancy Identification & Reconciliation Audits</span></caption><colgroup><col style="width:220px"/><col style="width:678px"/></colgroup><thead class="thead">
<tr class="row">
<th class="entry colsep-1 rowsep-1" id="system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_ydx_rcb_yfc__entry__1">Audit Name</th>
<th class="entry colsep-1 rowsep-1" id="system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_ydx_rcb_yfc__entry__2">Description</th>
</tr>
</thead><tbody class="tbody">
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_ydx_rcb_yfc__entry__1">Telecom Discrepancy Audit</td>
<td class="entry colsep-1 rowsep-1" headers="system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_ydx_rcb_yfc__entry__2">Audits records in the <code class="ph codeph">cmdb_rel_ci</code> table. For each relationship record discovered by Nokia Altiplano or NSP, it validates the parent and child CIs based on: - Most recent discovery date - CI model - CI model
relationship (if TNI Core is installed). <div class="note note note_note"><span class="note__title">Note:</span> All discrepancy audits use a filtering mechanism that applies to equipment CIs. By default, the filter condition is: <code class="ph codeph">discovery_source CONTAINS TSOM</code>.</div></td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_ydx_rcb_yfc__entry__1">Telecom Logical Connections Discrepancy Audit</td>
<td class="entry colsep-1 rowsep-1" headers="system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_ydx_rcb_yfc__entry__2">Audits records in the <code class="ph codeph">cmdb_ci_ni_logical_path</code> table. For each logical connection discovered by Nokia Altiplano or NSP, it checks: - Empty endpoint (Port A or Port Z) - Each endpoint must be connected to only
one unique logical connection.</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_ydx_rcb_yfc__entry__1">Telecom Network Topology Discrepancy Audit</td>
<td class="entry colsep-1 rowsep-1" headers="system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_ydx_rcb_yfc__entry__2">Audits records in the <code class="ph codeph">cmdb_ci_network_topology</code> table. For each network topology CI discovered by Nokia Altiplano or NSP, it verifies: - At least one Contains:Contained By relationship with equipment - At least
one Members:Member Of relationship with a logical connection.</td>
</tr>
</tbody></table></div>
</div>
<nav role="navigation"></nav><nav role="navigation" class="tasksNavigation"></nav><nav role="navigation" class="related-links"><div class="col-md-4"><dt>Related tasks</dt><dd><ul><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/task/configure-telecom-reconciliation.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/configure-telecom-reconciliation.html" class="link" title="Activate the Telecom Discrepancy Identification and Reconciliation feature (part of the Telecom Visibility plugin) to ensure consistency between telecom network resources discovered in the live network and the data represented in the CMDB or Telecom Network Inventory (TNI). This feature helps detect and remediate mismatches automatically, supporting service accuracy and data integrity across your telecom environment.">Activate Telecom Discrepancy Identification and Reconciliation</a></li><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/task/run-audits.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/run-audits.html" class="link" title="The Telecom Discrepancy Audit validates the integrity of configuration items (CIs) and relationships across your telecom inventory using the CMDB Compliance framework.">Run Telecom Discrepancy audit</a></li></ul></dd></div><div class="col-md-4"><dt>Related concepts</dt><dd><ul><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/concept/exploring-telecom-reconciliation.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/exploring-telecom-reconciliation.html" class="link" title="Use the Telecom Discrepancy Identification and Reconciliation capability to keep your CMDB or Telecommunications Network Inventory (TNI) in sync with your live telecom network. By continuously auditing and comparing discovered data with inventory records, this solution helps you detect, classify, and automatically remediate inconsistencies before they impact service quality, assurance, or fulfillment processes.">Telecom Discrepancy Identification and Reconciliation</a></li></ul></dd></div></nav>
</article></main></body></article> | {
"attachments": {
"all_attachments": null,
"topic_attachments": []
},
"available_languages": [
"enus"
],
"breadcrumbs": [
{
"title": "Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html"
},
{
"title": "Telecommunications Service Operations Management reference",
"topic_id": "product/tmt-telecom-service-operations-mgt/reference/components-installed-with-tsom.html"
}
],
"breadcrumbs_html": "<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops\">Zurich Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html\">Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/reference/components-installed-with-tsom.html\">Telecommunications Service Operations Management reference</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<span class=\"active\">System components installed with Telecom Discrepancy Identification & Reconciliation</span>",
"bundle_id": "zurich-telecom-service-ops",
"bundle_key": 2733,
"bundle_landing_page": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html",
"bundle_subtitle": null,
"bundle_title": "Zurich Telecommunications Service Operations Management",
"canonical_link": null,
"dates": {
"Added on": "2025-08-02T00:48:08.794016Z",
"Created on": "2025-01-16T00:00:00Z",
"Initial upload": "2025-07-30T22:24:33.519043Z",
"Updated on": "2025-07-31T00:00:00Z"
},
"dislike_url": "https://servicenow-be-prod.servicenow.com/dislike/55686939",
"dislikes": 0,
"es_archived_content": false,
"is_in_fav": false,
"is_liked": null,
"is_watched": false,
"keywords": [
" zurich zurich"
],
"labels": [
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "zurich",
"navtitle": "Zurich",
"outputclasses": [],
"subjectHeadId": "versions",
"subjectheadNavtitle": "Versions",
"visibility": "show-facet"
},
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "tsom",
"navtitle": "Telecommunications Service Operations Management",
"outputclasses": [],
"subjectHeadId": "products",
"subjectheadNavtitle": "Products",
"visibility": "show-facet"
}
],
"labels_text": "Versions > Zurich; Products > CRM and Industry Products > Telecommunications Media and Technology Assurance > Telecommunications Service Operations Management",
"like_url": "https://servicenow-be-prod.servicenow.com/like/55686939",
"likes": 0,
"metadata": {
"AI Search": null,
"AI Search Assist": null,
"Application Insights": null,
"Capabilities": null,
"Code Signing": null,
"Contextual Search": null,
"DC.contributor": null,
"DC.coverage": null,
"DC.creator": "ServiceNow",
"DC.date.created": "2025-01-16T16:02:37+05:30",
"DC.date.modified": "2025-07-31",
"DC.format": "HTML5",
"DC.identifier": "system-properties-affecting-telecom-discrepancy-identification-reconciliation",
"DC.language": null,
"DC.relation": "../../../product/tmt-telecom-service-operations-mgt/reference/components-installed-with-tsom.html",
"DC.rights.owner": "(C) Copyright 2025",
"DC.subject": null,
"DC.type": "concept",
"Data Discovery": null,
"Data Policy": null,
"Data Privacy": null,
"Discovery": null,
"External Content for AI Search": null,
"Field Administration": null,
"Field Normalization": null,
"Key Management Framework": null,
"Localization Framework": null,
"Now Platform": null,
"PlatSec": null,
"Platform": null,
"Platform Administration": null,
"Platform Performance": null,
"Platform Privacy": null,
"Proactive Triggers": null,
"Process Optimization": null,
"RN doc editing record number": null,
"Search Administration": null,
"Secrets Management": null,
"ServiceNow AI Platform": null,
"State Model": null,
"Subscription Management": null,
"Task Communications Management": null,
"Timeline Visualizations": null,
"User Administration": null,
"User Experience Analytics": null,
"Zing": null,
"ai-now-assist": null,
"app-name": null,
"app_route": null,
"azureapimanagemen": null,
"change-completed": null,
"change-item": null,
"change-request-id": null,
"change-request-reference": null,
"com.glide.embedded_help.category": null,
"component": null,
"copyright": "(C) Copyright 2025",
"crossroads": null,
"data": null,
"description": "The system properties are part of the TSOM Visibility plugin (sn_tsom_core) and control the Telecom Discrepancy Identification & Reconciliation log (TSOM CMDB Audit). The TSOM Visibility plugin serves as an enabler for the TSOM Visibility applications, containing logic that is",
"dominant_bundle": null,
"erp-canvas-video": null,
"fsm-mobile": null,
"fsm-route": null,
"fsm-sched-opt": null,
"fsm-wrk-order": null,
"genai-round-7": null,
"generator": "DITA-OT",
"glossPartOfSpeech": null,
"glossStatus": null,
"guided setup": null,
"guided tours": null,
"keywords": null,
"min-toc": null,
"mini": null,
"mini-to truec": null,
"mini-toc": null,
"mini_toc": null,
"minitoc": null,
"modification": null,
"now-assist-app-gen-video": null,
"order": null,
"page-type": null,
"page-type ": null,
"prodname": null,
"product": null,
"product_name": null,
"release": null,
"resourceID": null,
"roles": null,
"route_page": null,
"route_params_listId": null,
"route_params_table": null,
"route_params_type": null,
"route_type": null,
"setconfigurationproperties": null,
"topic": null,
"translation-type": "source",
"version": null,
"workflow": "Customer and Industry",
"workplace-srvc-delvry-ditamap": null
},
"page_id": "product/tmt-telecom-service-operations-mgt/concept/system-properties-affecting-telecom-discrepancy-identification-reconciliation.html",
"page_key": 55686939,
"preprocessed_PDF": "https://downloads.docs.servicenow.com/pdf/enus/servicenow-zurich-telecom-service-ops-enus.pdf",
"rating": null,
"read_time_data": {
"char_count": 3348,
"img_count": 0,
"read_time": 2,
"video_links": [
""
],
"word_count": 404
},
"related_links": [
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "Use the Telecom Discrepancy Identification and Reconciliation capability to keep your CMDB or Telecommunications Network Inventory (TNI) in sync with your live telecom network. By continuously auditing and comparing discovered data with inventory records, this solution helps you detect, classify, and automatically remediate inconsistencies before they impact service quality, assurance, or fulfillment processes.",
"title": "Telecom Discrepancy Identification and Reconciliation",
"topic": "/product/tmt-telecom-service-operations-mgt/concept/exploring-telecom-reconciliation.html",
"type": "concept",
"url": null
},
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "Activate the Telecom Discrepancy Identification and Reconciliation feature (part of the Telecom Visibility plugin) to ensure consistency between telecom network resources discovered in the live network and the data represented in the CMDB or Telecom Network Inventory (TNI). This feature helps detect and remediate mismatches automatically, supporting service accuracy and data integrity across your telecom environment.",
"title": "Activate Telecom Discrepancy Identification and Reconciliation",
"topic": "/product/tmt-telecom-service-operations-mgt/task/configure-telecom-reconciliation.html",
"type": "task",
"url": null
},
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "The Telecom Discrepancy Audit validates the integrity of configuration items (CIs) and relationships across your telecom inventory using the CMDB Compliance framework.",
"title": "Run Telecom Discrepancy audit",
"topic": "/product/tmt-telecom-service-operations-mgt/task/run-audits.html",
"type": "task",
"url": null
}
],
"search_title": null,
"title": "System components installed with Telecom Discrepancy Identification & Reconciliation",
"topic_cluster": {
"clustered_by": {
"enabled": true,
"primary_key": "versions",
"primary_sort": "top-down",
"type": "subjecthead"
},
"clustered_labels": [
"versions"
],
"clustered_topics": [],
"clustering_title": "Zurich"
},
"topic_html": "<article class=\"hascomments\" data-page=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/system-properties-affecting-telecom-discrepancy-identification-reconciliation.html\" id=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/system-properties-affecting-telecom-discrepancy-identification-reconciliation.html\"><body id=\"system-properties-affecting-telecom-discrepancy-identification-reconciliation\"><main role=\"main\"><article role=\"article\" class=\"dita\" id=\"system-properties-affecting-telecom-discrepancy-identification-reconciliation\" aria-labelledby=\"title_system-properties-affecting-telecom-discrepancy-identification-reconciliation\">\n <h1 class=\"title topictitle1\" id=\"title_system-properties-affecting-telecom-discrepancy-identification-reconciliation\">System components installed with Telecom Discrepancy Identification & Reconciliation</h1>\n \n \n <div class=\"body conbody\"><p class=\"shortdesc\">The system properties are part of the TSOM Visibility plugin (sn_tsom_core) and control the Telecom Discrepancy Identification & Reconciliation log (TSOM CMDB Audit). The TSOM Visibility plugin serves as an enabler for the\n TSOM Visibility applications, containing logic that is shared across the Telecom Discovery and Telecom Discrepancy Identification & Reconciliation solution.</p>\n <div class=\"p\">\n <div class=\"table-wrap\"><table count-columns=\"3\" class=\"table frame-all\" id=\"system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_c1p_wmd_b2c\"><caption><span class=\"table--title-label\">Table 1. </span><span class=\"title\">Telecom Discrepancy Identification & Reconciliation System Properties (Impacts CMDB Audit)</span></caption><colgroup><col style=\"width:220\"/><col style=\"width:161\"/><col style=\"width:244\"/></colgroup><thead class=\"thead\">\n <tr class=\"row\">\n <th class=\"entry colsep-1 rowsep-1\" id=\"system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_c1p_wmd_b2c__entry__1\">Property Name</th>\n <th class=\"entry colsep-1 rowsep-1\" id=\"system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_c1p_wmd_b2c__entry__2\">Recommended / Default Value</th>\n <th class=\"entry colsep-1 rowsep-1\" id=\"system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_c1p_wmd_b2c__entry__3\">Description</th>\n </tr>\n </thead><tbody class=\"tbody\">\n <tr class=\"row\">\n <td class=\"entry colsep-1 rowsep-1\" headers=\"system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_c1p_wmd_b2c__entry__1\">sn_tsom_core.audit.log.level</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_c1p_wmd_b2c__entry__2\">Telecom Discrepancy Audits' Logging.</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_c1p_wmd_b2c__entry__3\">debug,info,warn <p class=\"p\">Default value: info</p></td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry colsep-1 rowsep-1\" headers=\"system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_c1p_wmd_b2c__entry__1\">sn_tsom_core.audit.relationship_types</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_c1p_wmd_b2c__entry__2\">Displayed Names of Relationship Types that will be handled by Telecom Discrepancy Audit.</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_c1p_wmd_b2c__entry__3\">Comma separated list of relationship types names<p class=\"p\">Default value: Contains::Contained by</p></td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry colsep-1 rowsep-1\" headers=\"system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_c1p_wmd_b2c__entry__1\">sn_tsom_core.audit.discovered_date.diff.threshold.in.days</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_c1p_wmd_b2c__entry__2\">Most recent discovered date threshold in days. Used for Telecom Discrepancy Audit.</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_c1p_wmd_b2c__entry__3\">String<p class=\"p\">Default value: 2.5</p></td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry colsep-1 rowsep-1\" headers=\"system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_c1p_wmd_b2c__entry__1\">sn_tsom_core.audit.suppress_CI_Model_missing_discrepancy_task_creation</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_c1p_wmd_b2c__entry__2\">Suppress creation of CI Model missing discrepancy task for the tables.Used for Telecom Discrepancy Audit.</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_c1p_wmd_b2c__entry__3\">cmdb_ci_ni_telco_equipment, cmdb_ci_ip_switch, cmdb_ci_ip_router, cmdb_ci_container_slot,cmdb_ci_container_subslot,cmdb_ci_interface_card,cmdb_ci_ni_interface</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry colsep-1 rowsep-1\" headers=\"system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_c1p_wmd_b2c__entry__1\">sn_tsom_core.audit.equipment_tables</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_c1p_wmd_b2c__entry__2\">Equipment tables that will be handled by Telecom Discrepancy Audit.</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_c1p_wmd_b2c__entry__3\">Comma separated list of equipment tables names<p class=\"p\">Default value: cmdb_ci_netgear</p></td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry colsep-1 rowsep-1\" headers=\"system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_c1p_wmd_b2c__entry__1\">sn_tsom_core.audit.interface_card_tables</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_c1p_wmd_b2c__entry__2\">Interface Cards tables that will be handled by Telecom Discrepancy Audit.</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_c1p_wmd_b2c__entry__3\">Comma separated list of card tables names.<p class=\"p\">Default value: cmdb_ci_interface_card</p></td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry colsep-1 rowsep-1\" headers=\"system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_c1p_wmd_b2c__entry__1\">sn_tsom_core.audit.interface_tables</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_c1p_wmd_b2c__entry__2\">Network Interface tables that will be handled by Telecom Discrepancy Audit.</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_c1p_wmd_b2c__entry__3\">Comma separated list of interface tables names<p class=\"p\">Default value: cmdb_ci_ni_interface</p></td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry colsep-1 rowsep-1\" headers=\"system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_c1p_wmd_b2c__entry__1\">sn_tsom_core.audit.slot_tables</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_c1p_wmd_b2c__entry__2\">Slot tables names that will be handled by Telecom Discrepancy Audit.</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_c1p_wmd_b2c__entry__3\">Comma separated list of slot tables names<p class=\"p\">Default value: cmdb_ci_container_slot</p></td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry colsep-1 rowsep-1\" headers=\"system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_c1p_wmd_b2c__entry__1\">sn_tsom_core.audit.subslot_tables</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_c1p_wmd_b2c__entry__2\">Subslot tables names that will be handled by Telecom Discrepancy Audit.</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_c1p_wmd_b2c__entry__3\">Comma separated list of subslot tables names<p class=\"p\">Default value is cmdb_ci_container_subslot</p></td>\n </tr>\n </tbody></table></div>\n </div>\n <div class=\"table-wrap\"><table count-columns=\"2\" class=\"table frame-all\" id=\"system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_ydx_rcb_yfc\"><caption><span class=\"table--title-label\">Table 2. </span><span class=\"title\">Telecom Discrepancy Identification & Reconciliation Audits</span></caption><colgroup><col style=\"width:220px\"/><col style=\"width:678px\"/></colgroup><thead class=\"thead\">\n <tr class=\"row\">\n <th class=\"entry colsep-1 rowsep-1\" id=\"system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_ydx_rcb_yfc__entry__1\">Audit Name</th>\n <th class=\"entry colsep-1 rowsep-1\" id=\"system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_ydx_rcb_yfc__entry__2\">Description</th>\n </tr>\n </thead><tbody class=\"tbody\">\n <tr class=\"row\">\n <td class=\"entry colsep-1 rowsep-1\" headers=\"system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_ydx_rcb_yfc__entry__1\">Telecom Discrepancy Audit</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_ydx_rcb_yfc__entry__2\">Audits records in the <code class=\"ph codeph\">cmdb_rel_ci</code> table. For each relationship record discovered by Nokia Altiplano or NSP, it validates the parent and child CIs based on: - Most recent discovery date - CI model - CI model\n relationship (if TNI Core is installed). <div class=\"note note note_note\"><span class=\"note__title\">Note:</span> All discrepancy audits use a filtering mechanism that applies to equipment CIs. By default, the filter condition is: <code class=\"ph codeph\">discovery_source CONTAINS TSOM</code>.</div></td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry colsep-1 rowsep-1\" headers=\"system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_ydx_rcb_yfc__entry__1\">Telecom Logical Connections Discrepancy Audit</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_ydx_rcb_yfc__entry__2\">Audits records in the <code class=\"ph codeph\">cmdb_ci_ni_logical_path</code> table. For each logical connection discovered by Nokia Altiplano or NSP, it checks: - Empty endpoint (Port A or Port Z) - Each endpoint must be connected to only\n one unique logical connection.</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry colsep-1 rowsep-1\" headers=\"system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_ydx_rcb_yfc__entry__1\">Telecom Network Topology Discrepancy Audit</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"system-properties-affecting-telecom-discrepancy-identification-reconciliation__table_ydx_rcb_yfc__entry__2\">Audits records in the <code class=\"ph codeph\">cmdb_ci_network_topology</code> table. For each network topology CI discovered by Nokia Altiplano or NSP, it verifies: - At least one Contains:Contained By relationship with equipment - At least\n one Members:Member Of relationship with a logical connection.</td>\n </tr>\n </tbody></table></div>\n </div>\n <nav role=\"navigation\"></nav><nav role=\"navigation\" class=\"tasksNavigation\"></nav><nav role=\"navigation\" class=\"related-links\"><div class=\"col-md-4\"><dt>Related tasks</dt><dd><ul><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/task/configure-telecom-reconciliation.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/configure-telecom-reconciliation.html\" class=\"link\" title=\"Activate the Telecom Discrepancy Identification and Reconciliation feature (part of the Telecom Visibility plugin) to ensure consistency between telecom network resources discovered in the live network and the data represented in the CMDB or Telecom Network Inventory (TNI). This feature helps detect and remediate mismatches automatically, supporting service accuracy and data integrity across your telecom environment.\">Activate Telecom Discrepancy Identification and Reconciliation</a></li><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/task/run-audits.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/run-audits.html\" class=\"link\" title=\"The Telecom Discrepancy Audit validates the integrity of configuration items (CIs) and relationships across your telecom inventory using the CMDB Compliance framework.\">Run Telecom Discrepancy audit</a></li></ul></dd></div><div class=\"col-md-4\"><dt>Related concepts</dt><dd><ul><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept/exploring-telecom-reconciliation.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/exploring-telecom-reconciliation.html\" class=\"link\" title=\"Use the Telecom Discrepancy Identification and Reconciliation capability to keep your CMDB or Telecommunications Network Inventory (TNI) in sync with your live telecom network. By continuously auditing and comparing discovered data with inventory records, this solution helps you detect, classify, and automatically remediate inconsistencies before they impact service quality, assurance, or fulfillment processes.\">Telecom Discrepancy Identification and Reconciliation</a></li></ul></dd></div></nav>\n</article></main></body></article>",
"topic_language": "enus",
"views": 0,
"your_rating": null
} | # System components installed with Telecom Discrepancy Identification & Reconciliation
The system properties are part of the TSOM Visibility plugin (sn\_tsom\_core) and control the Telecom Discrepancy Identification & Reconciliation log (TSOM CMDB Audit). The TSOM Visibility plugin serves as an enabler for the
TSOM Visibility applications, containing logic that is shared across the Telecom Discovery and Telecom Discrepancy Identification & Reconciliation solution.
Table 1. Telecom Discrepancy Identification & Reconciliation System Properties (Impacts CMDB Audit)
| Property Name | Recommended / Default Value | Description |
| --- | --- | --- |
| sn\_tsom\_core.audit.log.level | Telecom Discrepancy Audits' Logging. | debug,info,warn Default value: info |
| sn\_tsom\_core.audit.relationship\_types | Displayed Names of Relationship Types that will be handled by Telecom Discrepancy Audit. | Comma separated list of relationship types names Default value: Contains::Contained by |
| sn\_tsom\_core.audit.discovered\_date.diff.threshold.in.days | Most recent discovered date threshold in days. Used for Telecom Discrepancy Audit. | String Default value: 2.5 |
| sn\_tsom\_core.audit.suppress\_CI\_Model\_missing\_discrepancy\_task\_creation | Suppress creation of CI Model missing discrepancy task for the tables.Used for Telecom Discrepancy Audit. | cmdb\_ci\_ni\_telco\_equipment, cmdb\_ci\_ip\_switch, cmdb\_ci\_ip\_router, cmdb\_ci\_container\_slot,cmdb\_ci\_container\_subslot,cmdb\_ci\_interface\_card,cmdb\_ci\_ni\_interface |
| sn\_tsom\_core.audit.equipment\_tables | Equipment tables that will be handled by Telecom Discrepancy Audit. | Comma separated list of equipment tables names Default value: cmdb\_ci\_netgear |
| sn\_tsom\_core.audit.interface\_card\_tables | Interface Cards tables that will be handled by Telecom Discrepancy Audit. | Comma separated list of card tables names. Default value: cmdb\_ci\_interface\_card |
| sn\_tsom\_core.audit.interface\_tables | Network Interface tables that will be handled by Telecom Discrepancy Audit. | Comma separated list of interface tables names Default value: cmdb\_ci\_ni\_interface |
| sn\_tsom\_core.audit.slot\_tables | Slot tables names that will be handled by Telecom Discrepancy Audit. | Comma separated list of slot tables names Default value: cmdb\_ci\_container\_slot |
| sn\_tsom\_core.audit.subslot\_tables | Subslot tables names that will be handled by Telecom Discrepancy Audit. | Comma separated list of subslot tables names Default value is cmdb\_ci\_container\_subslot |
Table 2. Telecom Discrepancy Identification & Reconciliation Audits
| Audit Name | Description |
| --- | --- |
| Telecom Discrepancy Audit | Audits records in the `cmdb_rel_ci` table. For each relationship record discovered by Nokia Altiplano or NSP, it validates the parent and child CIs based on: - Most recent discovery date - CI model - CI model relationship (if TNI Core is installed). Note: All discrepancy audits use a filtering mechanism that applies to equipment CIs. By default, the filter condition is: `discovery_source CONTAINS TSOM`. |
| Telecom Logical Connections Discrepancy Audit | Audits records in the `cmdb_ci_ni_logical_path` table. For each logical connection discovered by Nokia Altiplano or NSP, it checks: - Empty endpoint (Port A or Port Z) - Each endpoint must be connected to only one unique logical connection. |
| Telecom Network Topology Discrepancy Audit | Audits records in the `cmdb_ci_network_topology` table. For each network topology CI discovered by Nokia Altiplano or NSP, it verifies: - At least one Contains:Contained By relationship with equipment - At least one Members:Member Of relationship with a logical connection. |
| ---
title: System components installed with Telecom Discrepancy Identification & Reconciliation
description: The system properties are part of the TSOM Visibility plugin (sn_tsom_core)
and control the Telecom Discrepancy Identification & Reconciliation log (TSOM CMDB
Audit). The TSOM Visibility plugin serves as an enabler for the TSOM Visibility
applications, containing logic that is
keywords: []
breadcrumbs:
- Telecommunications Service Operations Management
- Telecommunications Service Operations Management reference
---
# System components installed with Telecom Discrepancy Identification & Reconciliation
The system properties are part of the TSOM Visibility plugin (sn\_tsom\_core) and control the Telecom Discrepancy Identification & Reconciliation log (TSOM CMDB Audit). The TSOM Visibility plugin serves as an enabler for the
TSOM Visibility applications, containing logic that is shared across the Telecom Discovery and Telecom Discrepancy Identification & Reconciliation solution.
Table 1. Telecom Discrepancy Identification & Reconciliation System Properties (Impacts CMDB Audit)
| Property Name | Recommended / Default Value | Description |
| --- | --- | --- |
| sn\_tsom\_core.audit.log.level | Telecom Discrepancy Audits' Logging. | debug,info,warn Default value: info |
| sn\_tsom\_core.audit.relationship\_types | Displayed Names of Relationship Types that will be handled by Telecom Discrepancy Audit. | Comma separated list of relationship types names Default value: Contains::Contained by |
| sn\_tsom\_core.audit.discovered\_date.diff.threshold.in.days | Most recent discovered date threshold in days. Used for Telecom Discrepancy Audit. | String Default value: 2.5 |
| sn\_tsom\_core.audit.suppress\_CI\_Model\_missing\_discrepancy\_task\_creation | Suppress creation of CI Model missing discrepancy task for the tables.Used for Telecom Discrepancy Audit. | cmdb\_ci\_ni\_telco\_equipment, cmdb\_ci\_ip\_switch, cmdb\_ci\_ip\_router, cmdb\_ci\_container\_slot,cmdb\_ci\_container\_subslot,cmdb\_ci\_interface\_card,cmdb\_ci\_ni\_interface |
| sn\_tsom\_core.audit.equipment\_tables | Equipment tables that will be handled by Telecom Discrepancy Audit. | Comma separated list of equipment tables names Default value: cmdb\_ci\_netgear |
| sn\_tsom\_core.audit.interface\_card\_tables | Interface Cards tables that will be handled by Telecom Discrepancy Audit. | Comma separated list of card tables names. Default value: cmdb\_ci\_interface\_card |
| sn\_tsom\_core.audit.interface\_tables | Network Interface tables that will be handled by Telecom Discrepancy Audit. | Comma separated list of interface tables names Default value: cmdb\_ci\_ni\_interface |
| sn\_tsom\_core.audit.slot\_tables | Slot tables names that will be handled by Telecom Discrepancy Audit. | Comma separated list of slot tables names Default value: cmdb\_ci\_container\_slot |
| sn\_tsom\_core.audit.subslot\_tables | Subslot tables names that will be handled by Telecom Discrepancy Audit. | Comma separated list of subslot tables names Default value is cmdb\_ci\_container\_subslot |
Table 2. Telecom Discrepancy Identification & Reconciliation Audits
| Audit Name | Description |
| --- | --- |
| Telecom Discrepancy Audit | Audits records in the `cmdb_rel_ci` table. For each relationship record discovered by Nokia Altiplano or NSP, it validates the parent and child CIs based on: - Most recent discovery date - CI model - CI model relationship (if TNI Core is installed). Note: All discrepancy audits use a filtering mechanism that applies to equipment CIs. By default, the filter condition is: `discovery_source CONTAINS TSOM`. |
| Telecom Logical Connections Discrepancy Audit | Audits records in the `cmdb_ci_ni_logical_path` table. For each logical connection discovered by Nokia Altiplano or NSP, it checks: - Empty endpoint (Port A or Port Z) - Each endpoint must be connected to only one unique logical connection. |
| Telecom Network Topology Discrepancy Audit | Audits records in the `cmdb_ci_network_topology` table. For each network topology CI discovered by Nokia Altiplano or NSP, it verifies: - At least one Contains:Contained By relationship with equipment - At least one Members:Member Of relationship with a logical connection. |
|
https://www.servicenow.com/docs/en-US/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/telecom-cisco7613-router-pattern.html | https://servicenow-be-prod.servicenow.com/api/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/telecom-cisco7613-router-pattern.html | 2025-08-02 | daily | 0.5 | 268.xml | en-US | zurich-telecom-service-ops | product/tmt-telecom-service-operations-mgt/concept/telecom-cisco7613-router-pattern.html | zurich | Telecom Cisco 7613 Router Pattern | The ServiceNow® Telecom Discovery application uses the Telecom Cisco 7613 Router discovery pattern to find SNMP-based Cisco 7613 in the network. Discovering some of these resources requires updating the Telecommunications Discovery Patterns (TSOM Patterns) from the ServiceNow® Store. | [] | [
"Telecommunications Service Operations Management",
"Exploring Telecommunications Service Operations Management",
"Telecom Visibility",
"Telecom Discovery",
"Direct Discovery using Discovery Patterns"
] | <article class="hascomments" data-page="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/telecom-cisco7613-router-pattern.html" id="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/telecom-cisco7613-router-pattern.html"><body><main role="main"><article role="article" class="dita" aria-labelledby="title_telecom-cisco7613-router-pattern"><article class="nested0" aria-labelledby="title_telecom-cisco7613-router-pattern" id="telecom-cisco7613-router-pattern">
<h1 class="title topictitle1" id="title_telecom-cisco7613-router-pattern">Telecom Cisco 7613 Router Pattern</h1>
<div class="body conbody"><p class="shortdesc">The <span class="ph">ServiceNow®</span> Telecom Discovery application uses the Telecom Cisco 7613 Router discovery pattern to find SNMP-based Cisco 7613 in the network. Discovering some of these resources requires updating the Telecommunications
Discovery Patterns (TSOM Patterns) from the <span class="ph">ServiceNow®</span> Store.</p>
<p class="p">Telecom Discovery uses the Telecommunications Discovery Patterns to run Horizontal Discovery. This Telecommunications Discovery Pattern uses a set of SNMP requests to find, classify, and discover network elements.</p>
<p class="p">Telecom Cisco 7613 Router Pattern is part of the Telecommunications Discovery Patterns application (sn_tsom_patterns), which is part of TSOM Visibility.</p>
<section class="section" id="telecom-cisco7613-router-pattern__section_irz_2lk_zdc"><h2 id="d10924e60" class="title sectiontitle">Request apps on the Store</h2>
<p class="p" id="telecom-cisco7613-router-pattern__p_c21_nfg_h1c"><span class="ph" id="telecom-cisco7613-router-pattern__inline-send-to-store">Visit the <a class="xref true-external" href="https://store.servicenow.com/sn_appstore_store.do#!/store/home" target="_blank"><span class="ph">ServiceNow Store</span></a> 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 <a class="xref" href="https://docs.servicenow.com/bundle/store-release-notes/page/release-notes/store/sn-store-release-notes.html"><span class="ph">ServiceNow Store</span> version history release notes</a>.</span></p>
</section>
<section class="section" id="telecom-cisco7613-router-pattern__section_rtl_ttn_zdc"><h2 id="d10924e81" class="title sectiontitle">Prerequisites</h2>
<div class="p">
<ul class="ul" id="telecom-cisco7613-router-pattern__ul_mzs_ttn_zdc">
<li class="li">Subscription to TSOM.</li>
<li class="li">Verify that your network router devices have SNMP access.</li>
<li class="li">On the ServiceNow instance, configure SNMP credentials. For more information, see <a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/concept//csh" href="https://servicenow-be-prod.servicenow.com/csh?topicname=c_SNMPSupportForDiscovery&version=zurich&pubname=zurich-it-operations-management" class="xref">SNMP support for Discovery</a>.</li>
<li class="li">For setting up TSOM Patterns, see <a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/task/install-horizontal-telecommunication-discoverypatterns.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/install-horizontal-telecommunication-discoverypatterns.html" class="xref" title="Install Horizontal Discovery patterns understanding the dependencies and requirements.">Install Horizontal Discovery and set up Discovery Patterns</a>.</li>
</ul>
</div>
</section>
<section class="section" id="telecom-cisco7613-router-pattern__section_kht_wtn_zdc"><h2 id="d10924e116" class="title sectiontitle">Impacted CMDB CIs and CI Relationships (Physical Layer)</h2>
<div class="p">
<div class="table-wrap"><table count-columns="2" class="table frame-all" id="telecom-cisco7613-router-pattern__table_kgl_g5n_zdc"><caption></caption><colgroup><col style="width:50%"/><col style="width:50%"/></colgroup><thead class="thead">
<tr class="row">
<th class="entry colsep-1 rowsep-1" id="telecom-cisco7613-router-pattern__table_kgl_g5n_zdc__entry__1">CIs</th>
<th class="entry colsep-1 rowsep-1" id="telecom-cisco7613-router-pattern__table_kgl_g5n_zdc__entry__2">CI Relationships</th>
</tr>
</thead><tbody class="tbody">
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="telecom-cisco7613-router-pattern__table_kgl_g5n_zdc__entry__1">IP Router CI</td>
<td class="entry colsep-1 rowsep-1" headers="telecom-cisco7613-router-pattern__table_kgl_g5n_zdc__entry__2">
<p class="p">IP Router Device is represented by the IP Router CI.</p>
<p class="p">Table name: <strong class="ph b">cmdb_ci_ip_router</strong></p>
<p class="p">IP Router CI contains Slots or Network Interfaces.</p>
</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="telecom-cisco7613-router-pattern__table_kgl_g5n_zdc__entry__1">Slot CI</td>
<td class="entry colsep-1 rowsep-1" headers="telecom-cisco7613-router-pattern__table_kgl_g5n_zdc__entry__2">
<p class="p">Slots are represented by the Slot CI.</p>
<p class="p">Table name: <strong class="ph b">cmdb_ci_container_slot</strong></p>
<p class="p">Slot is contained by the IP Router.</p>
<p class="p">Slot CI contains the Interface Card.</p>
</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="telecom-cisco7613-router-pattern__table_kgl_g5n_zdc__entry__1">Subslot CI</td>
<td class="entry colsep-1 rowsep-1" headers="telecom-cisco7613-router-pattern__table_kgl_g5n_zdc__entry__2">
<p class="p">Subslots are represented by the Subslot CI.</p>
<p class="p">Table name: <strong class="ph b">cmdb_ci_container_subslot</strong></p>
<p class="p">Subslot is contained by Interface Card CI.</p>
<p class="p">Subslot CI contains the Interface Card CI.</p>
</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="telecom-cisco7613-router-pattern__table_kgl_g5n_zdc__entry__1">Interface Card CI</td>
<td class="entry colsep-1 rowsep-1" headers="telecom-cisco7613-router-pattern__table_kgl_g5n_zdc__entry__2">
<p class="p">Different types of cards are represented by the Interface Card CI.</p>
<p class="p">Fan and Power Supply Units are also represented by the Card CI.</p>
<p class="p">Table name: <strong class="ph b">cmdb_ci_interface_card</strong></p>
<p class="p">Interface Cards are contained by Slots or Subslots.</p>
<p class="p">Interface Cards can contain Network Interface or Subslots.</p>
</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="telecom-cisco7613-router-pattern__table_kgl_g5n_zdc__entry__1">Network Interface CI</td>
<td class="entry colsep-1 rowsep-1" headers="telecom-cisco7613-router-pattern__table_kgl_g5n_zdc__entry__2">
<p class="p">Any type of Network Interface is represented by the Network Interface CI.</p>
<p class="p">Table name: <strong class="ph b">cmdb_ci_ni_interface</strong></p>
<p class="p">Network Interface is contained by Interface Card, IP Router.</p>
</td>
</tr>
</tbody></table></div>
</div>
</section>
</div>
</article></article></main></body></article> | {
"attachments": {
"all_attachments": null,
"topic_attachments": []
},
"available_languages": [
"enus"
],
"breadcrumbs": [
{
"title": "Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html"
},
{
"title": "Exploring Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/exploring-tsom.html"
},
{
"title": "Telecom Visibility",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/tsom-visibility.html"
},
{
"title": "Telecom Discovery",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/exploring-telecom-discovery.html"
},
{
"title": "Direct Discovery using Discovery Patterns",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/telecom-discovery-using-telecommunication-discovery-pattern.html"
}
],
"breadcrumbs_html": "<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops\">Zurich Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html\">Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/exploring-tsom.html\">Exploring Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/tsom-visibility.html\">Telecom Visibility</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/exploring-telecom-discovery.html\">Telecom Discovery</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/telecom-discovery-using-telecommunication-discovery-pattern.html\">Direct Discovery using Discovery Patterns</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<span class=\"active\">Telecom Cisco 7613 Router Pattern</span>",
"bundle_id": "zurich-telecom-service-ops",
"bundle_key": 2733,
"bundle_landing_page": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html",
"bundle_subtitle": null,
"bundle_title": "Zurich Telecommunications Service Operations Management",
"canonical_link": null,
"dates": {
"Added on": "2025-08-02T00:48:08.794016Z",
"Created on": "2024-12-06T00:00:00Z",
"Initial upload": "2025-07-30T22:24:33.519043Z",
"Updated on": "2025-07-31T00:00:00Z"
},
"dislike_url": "https://servicenow-be-prod.servicenow.com/dislike/55686941",
"dislikes": 0,
"es_archived_content": false,
"is_in_fav": false,
"is_liked": null,
"is_watched": false,
"keywords": [
" zurich zurich"
],
"labels": [
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "zurich",
"navtitle": "Zurich",
"outputclasses": [],
"subjectHeadId": "versions",
"subjectheadNavtitle": "Versions",
"visibility": "show-facet"
},
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "tsom",
"navtitle": "Telecommunications Service Operations Management",
"outputclasses": [],
"subjectHeadId": "products",
"subjectheadNavtitle": "Products",
"visibility": "show-facet"
}
],
"labels_text": "Versions > Zurich; Products > CRM and Industry Products > Telecommunications Media and Technology Assurance > Telecommunications Service Operations Management",
"like_url": "https://servicenow-be-prod.servicenow.com/like/55686941",
"likes": 0,
"metadata": {
"AI Search": null,
"AI Search Assist": null,
"Application Insights": null,
"Capabilities": null,
"Code Signing": null,
"Contextual Search": null,
"DC.contributor": null,
"DC.coverage": null,
"DC.creator": "ServiceNow",
"DC.date.created": "2024-12-06T11:49:46+05:30",
"DC.date.modified": "2025-07-31",
"DC.format": "HTML5",
"DC.identifier": "telecom-cisco7613-router-pattern",
"DC.language": null,
"DC.relation": null,
"DC.rights.owner": "(C) Copyright 2025",
"DC.subject": null,
"DC.type": "dita",
"Data Discovery": null,
"Data Policy": null,
"Data Privacy": null,
"Discovery": null,
"External Content for AI Search": null,
"Field Administration": null,
"Field Normalization": null,
"Key Management Framework": null,
"Localization Framework": null,
"Now Platform": null,
"PlatSec": null,
"Platform": null,
"Platform Administration": null,
"Platform Performance": null,
"Platform Privacy": null,
"Proactive Triggers": null,
"Process Optimization": null,
"RN doc editing record number": null,
"Search Administration": null,
"Secrets Management": null,
"ServiceNow AI Platform": null,
"State Model": null,
"Subscription Management": null,
"Task Communications Management": null,
"Timeline Visualizations": null,
"User Administration": null,
"User Experience Analytics": null,
"Zing": null,
"ai-now-assist": null,
"app-name": null,
"app_route": null,
"azureapimanagemen": null,
"change-completed": null,
"change-item": null,
"change-request-id": null,
"change-request-reference": null,
"com.glide.embedded_help.category": null,
"component": null,
"copyright": "(C) Copyright 2025",
"crossroads": null,
"data": null,
"description": "The ServiceNow® Telecom Discovery application uses the Telecom Cisco 7613 Router discovery pattern to find SNMP-based Cisco 7613 in the network. Discovering some of these resources requires updating the Telecommunications Discovery Patterns (TSOM Patterns) from the ServiceNow® Store.",
"dominant_bundle": null,
"erp-canvas-video": null,
"fsm-mobile": null,
"fsm-route": null,
"fsm-sched-opt": null,
"fsm-wrk-order": null,
"genai-round-7": null,
"generator": "DITA-OT",
"glossPartOfSpeech": null,
"glossStatus": null,
"guided setup": null,
"guided tours": null,
"keywords": null,
"min-toc": null,
"mini": null,
"mini-to truec": null,
"mini-toc": "yes",
"mini_toc": null,
"minitoc": null,
"modification": null,
"now-assist-app-gen-video": null,
"order": null,
"page-type": null,
"page-type ": null,
"prodname": null,
"product": null,
"product_name": null,
"release": null,
"resourceID": null,
"roles": null,
"route_page": null,
"route_params_listId": null,
"route_params_table": null,
"route_params_type": null,
"route_type": null,
"setconfigurationproperties": null,
"topic": null,
"translation-type": "source",
"version": null,
"workflow": "Customer and Industry",
"workplace-srvc-delvry-ditamap": null
},
"page_id": "product/tmt-telecom-service-operations-mgt/concept/telecom-cisco7613-router-pattern.html",
"page_key": 55686941,
"preprocessed_PDF": "https://downloads.docs.servicenow.com/pdf/enus/servicenow-zurich-telecom-service-ops-enus.pdf",
"rating": null,
"read_time_data": {
"char_count": 2246,
"img_count": 0,
"read_time": 2,
"video_links": [
""
],
"word_count": 328
},
"related_links": [],
"search_title": null,
"title": "Telecom Cisco 7613 Router Pattern",
"topic_cluster": {
"clustered_by": {
"enabled": true,
"primary_key": "versions",
"primary_sort": "top-down",
"type": "subjecthead"
},
"clustered_labels": [
"versions"
],
"clustered_topics": [
{
"bundle_id": "yokohama-telecom-service-ops",
"clustering_title": "Yokohama",
"es_archived_content": false,
"page_id": "product/tmt-telecom-service-operations-mgt/concept/telecom-cisco7613-router-pattern.html"
}
],
"clustering_title": "Zurich"
},
"topic_html": "<article class=\"hascomments\" data-page=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/telecom-cisco7613-router-pattern.html\" id=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/telecom-cisco7613-router-pattern.html\"><body><main role=\"main\"><article role=\"article\" class=\"dita\" aria-labelledby=\"title_telecom-cisco7613-router-pattern\"><article class=\"nested0\" aria-labelledby=\"title_telecom-cisco7613-router-pattern\" id=\"telecom-cisco7613-router-pattern\">\n <h1 class=\"title topictitle1\" id=\"title_telecom-cisco7613-router-pattern\">Telecom Cisco 7613 Router Pattern</h1>\n \n \n <div class=\"body conbody\"><p class=\"shortdesc\">The <span class=\"ph\">ServiceNow®</span> Telecom Discovery application uses the Telecom Cisco 7613 Router discovery pattern to find SNMP-based Cisco 7613 in the network. Discovering some of these resources requires updating the Telecommunications\n Discovery Patterns (TSOM Patterns) from the <span class=\"ph\">ServiceNow®</span> Store.</p>\n <p class=\"p\">Telecom Discovery uses the Telecommunications Discovery Patterns to run Horizontal Discovery. This Telecommunications Discovery Pattern uses a set of SNMP requests to find, classify, and discover network elements.</p>\n <p class=\"p\">Telecom Cisco 7613 Router Pattern is part of the Telecommunications Discovery Patterns application (sn_tsom_patterns), which is part of TSOM Visibility.</p>\n <section class=\"section\" id=\"telecom-cisco7613-router-pattern__section_irz_2lk_zdc\"><h2 id=\"d10924e60\" class=\"title sectiontitle\">Request apps on the Store</h2>\n \n \n <p class=\"p\" id=\"telecom-cisco7613-router-pattern__p_c21_nfg_h1c\"><span class=\"ph\" id=\"telecom-cisco7613-router-pattern__inline-send-to-store\">Visit the <a class=\"xref true-external\" href=\"https://store.servicenow.com/sn_appstore_store.do#!/store/home\" target=\"_blank\"><span class=\"ph\">ServiceNow Store</span></a> 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 <a class=\"xref\" href=\"https://docs.servicenow.com/bundle/store-release-notes/page/release-notes/store/sn-store-release-notes.html\"><span class=\"ph\">ServiceNow Store</span> version history release notes</a>.</span></p>\n </section>\n <section class=\"section\" id=\"telecom-cisco7613-router-pattern__section_rtl_ttn_zdc\"><h2 id=\"d10924e81\" class=\"title sectiontitle\">Prerequisites</h2>\n \n <div class=\"p\">\n <ul class=\"ul\" id=\"telecom-cisco7613-router-pattern__ul_mzs_ttn_zdc\">\n <li class=\"li\">Subscription to TSOM.</li>\n <li class=\"li\">Verify that your network router devices have SNMP access.</li>\n <li class=\"li\">On the ServiceNow instance, configure SNMP credentials. For more information, see <a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept//csh\" href=\"https://servicenow-be-prod.servicenow.com/csh?topicname=c_SNMPSupportForDiscovery&version=zurich&pubname=zurich-it-operations-management\" class=\"xref\">SNMP support for Discovery</a>.</li>\n <li class=\"li\">For setting up TSOM Patterns, see <a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/task/install-horizontal-telecommunication-discoverypatterns.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/install-horizontal-telecommunication-discoverypatterns.html\" class=\"xref\" title=\"Install Horizontal Discovery patterns understanding the dependencies and requirements.\">Install Horizontal Discovery and set up Discovery Patterns</a>.</li>\n </ul>\n </div>\n </section>\n <section class=\"section\" id=\"telecom-cisco7613-router-pattern__section_kht_wtn_zdc\"><h2 id=\"d10924e116\" class=\"title sectiontitle\">Impacted CMDB CIs and CI Relationships (Physical Layer)</h2>\n \n <div class=\"p\">\n <div class=\"table-wrap\"><table count-columns=\"2\" class=\"table frame-all\" id=\"telecom-cisco7613-router-pattern__table_kgl_g5n_zdc\"><caption></caption><colgroup><col style=\"width:50%\"/><col style=\"width:50%\"/></colgroup><thead class=\"thead\">\n <tr class=\"row\">\n <th class=\"entry colsep-1 rowsep-1\" id=\"telecom-cisco7613-router-pattern__table_kgl_g5n_zdc__entry__1\">CIs</th>\n <th class=\"entry colsep-1 rowsep-1\" id=\"telecom-cisco7613-router-pattern__table_kgl_g5n_zdc__entry__2\">CI Relationships</th>\n </tr>\n </thead><tbody class=\"tbody\">\n <tr class=\"row\">\n <td class=\"entry colsep-1 rowsep-1\" headers=\"telecom-cisco7613-router-pattern__table_kgl_g5n_zdc__entry__1\">IP Router CI</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"telecom-cisco7613-router-pattern__table_kgl_g5n_zdc__entry__2\">\n <p class=\"p\">IP Router Device is represented by the IP Router CI.</p>\n <p class=\"p\">Table name: <strong class=\"ph b\">cmdb_ci_ip_router</strong></p>\n <p class=\"p\">IP Router CI contains Slots or Network Interfaces.</p>\n </td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry colsep-1 rowsep-1\" headers=\"telecom-cisco7613-router-pattern__table_kgl_g5n_zdc__entry__1\">Slot CI</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"telecom-cisco7613-router-pattern__table_kgl_g5n_zdc__entry__2\">\n <p class=\"p\">Slots are represented by the Slot CI.</p>\n <p class=\"p\">Table name: <strong class=\"ph b\">cmdb_ci_container_slot</strong></p>\n <p class=\"p\">Slot is contained by the IP Router.</p>\n <p class=\"p\">Slot CI contains the Interface Card.</p>\n </td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry colsep-1 rowsep-1\" headers=\"telecom-cisco7613-router-pattern__table_kgl_g5n_zdc__entry__1\">Subslot CI</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"telecom-cisco7613-router-pattern__table_kgl_g5n_zdc__entry__2\">\n <p class=\"p\">Subslots are represented by the Subslot CI.</p>\n <p class=\"p\">Table name: <strong class=\"ph b\">cmdb_ci_container_subslot</strong></p>\n <p class=\"p\">Subslot is contained by Interface Card CI.</p>\n <p class=\"p\">Subslot CI contains the Interface Card CI.</p>\n </td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry colsep-1 rowsep-1\" headers=\"telecom-cisco7613-router-pattern__table_kgl_g5n_zdc__entry__1\">Interface Card CI</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"telecom-cisco7613-router-pattern__table_kgl_g5n_zdc__entry__2\">\n <p class=\"p\">Different types of cards are represented by the Interface Card CI.</p>\n <p class=\"p\">Fan and Power Supply Units are also represented by the Card CI.</p>\n <p class=\"p\">Table name: <strong class=\"ph b\">cmdb_ci_interface_card</strong></p>\n <p class=\"p\">Interface Cards are contained by Slots or Subslots.</p>\n <p class=\"p\">Interface Cards can contain Network Interface or Subslots.</p>\n </td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry colsep-1 rowsep-1\" headers=\"telecom-cisco7613-router-pattern__table_kgl_g5n_zdc__entry__1\">Network Interface CI</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"telecom-cisco7613-router-pattern__table_kgl_g5n_zdc__entry__2\">\n <p class=\"p\">Any type of Network Interface is represented by the Network Interface CI.</p>\n <p class=\"p\">Table name: <strong class=\"ph b\">cmdb_ci_ni_interface</strong></p>\n <p class=\"p\">Network Interface is contained by Interface Card, IP Router.</p>\n </td>\n </tr>\n </tbody></table></div>\n </div>\n </section>\n </div>\n</article></article></main></body></article>",
"topic_language": "enus",
"views": 0,
"your_rating": null
} | # Telecom Cisco 7613 Router Pattern
The ServiceNow® Telecom Discovery application uses the Telecom Cisco 7613 Router discovery pattern to find SNMP-based Cisco 7613 in the network. Discovering some of these resources requires updating the Telecommunications
Discovery Patterns (TSOM Patterns) from the ServiceNow® Store.
Telecom Discovery uses the Telecommunications Discovery Patterns to run Horizontal Discovery. This Telecommunications Discovery Pattern uses a set of SNMP requests to find, classify, and discover network elements.
Telecom Cisco 7613 Router Pattern is part of the Telecommunications Discovery Patterns application (sn\_tsom\_patterns), which is part of TSOM Visibility.
## 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.
## Prerequisites
* Subscription to TSOM.
* Verify that your network router devices have SNMP access.
* On the ServiceNow instance, configure SNMP credentials. For more information, see SNMP support for Discovery.
* For setting up TSOM Patterns, see Install Horizontal Discovery and set up Discovery Patterns.
## Impacted CMDB CIs and CI Relationships (Physical Layer)
| CIs | CI Relationships |
| --- | --- |
| IP Router CI | IP Router Device is represented by the IP Router CI. Table name: **cmdb\_ci\_ip\_router** IP Router CI contains Slots or Network Interfaces. |
| Slot CI | Slots are represented by the Slot CI. Table name: **cmdb\_ci\_container\_slot** Slot is contained by the IP Router. Slot CI contains the Interface Card. |
| Subslot CI | Subslots are represented by the Subslot CI. Table name: **cmdb\_ci\_container\_subslot** Subslot is contained by Interface Card CI. Subslot CI contains the Interface Card CI. |
| Interface Card CI | Different types of cards are represented by the Interface Card CI. Fan and Power Supply Units are also represented by the Card CI. Table name: **cmdb\_ci\_interface\_card** Interface Cards are contained by Slots or Subslots. Interface Cards can contain Network Interface or Subslots. |
| Network Interface CI | Any type of Network Interface is represented by the Network Interface CI. Table name: **cmdb\_ci\_ni\_interface** Network Interface is contained by Interface Card, IP Router. |
| ---
title: Telecom Cisco 7613 Router Pattern
description: "The ServiceNow\xAE Telecom Discovery application uses the Telecom Cisco\
\ 7613 Router discovery pattern to find SNMP-based Cisco 7613 in the network. Discovering\
\ some of these resources requires updating the Telecommunications Discovery Patterns\
\ (TSOM Patterns) from the ServiceNow\xAE Store."
keywords: []
breadcrumbs:
- Telecommunications Service Operations Management
- Exploring Telecommunications Service Operations Management
- Telecom Visibility
- Telecom Discovery
- Direct Discovery using Discovery Patterns
---
# Telecom Cisco 7613 Router Pattern
The ServiceNow® Telecom Discovery application uses the Telecom Cisco 7613 Router discovery pattern to find SNMP-based Cisco 7613 in the network. Discovering some of these resources requires updating the Telecommunications
Discovery Patterns (TSOM Patterns) from the ServiceNow® Store.
Telecom Discovery uses the Telecommunications Discovery Patterns to run Horizontal Discovery. This Telecommunications Discovery Pattern uses a set of SNMP requests to find, classify, and discover network elements.
Telecom Cisco 7613 Router Pattern is part of the Telecommunications Discovery Patterns application (sn\_tsom\_patterns), which is part of TSOM Visibility.
## 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.
## Prerequisites
* Subscription to TSOM.
* Verify that your network router devices have SNMP access.
* On the ServiceNow instance, configure SNMP credentials. For more information, see SNMP support for Discovery.
* For setting up TSOM Patterns, see Install Horizontal Discovery and set up Discovery Patterns.
## Impacted CMDB CIs and CI Relationships (Physical Layer)
| CIs | CI Relationships |
| --- | --- |
| IP Router CI | IP Router Device is represented by the IP Router CI. Table name: **cmdb\_ci\_ip\_router** IP Router CI contains Slots or Network Interfaces. |
| Slot CI | Slots are represented by the Slot CI. Table name: **cmdb\_ci\_container\_slot** Slot is contained by the IP Router. Slot CI contains the Interface Card. |
| Subslot CI | Subslots are represented by the Subslot CI. Table name: **cmdb\_ci\_container\_subslot** Subslot is contained by Interface Card CI. Subslot CI contains the Interface Card CI. |
| Interface Card CI | Different types of cards are represented by the Interface Card CI. Fan and Power Supply Units are also represented by the Card CI. Table name: **cmdb\_ci\_interface\_card** Interface Cards are contained by Slots or Subslots. Interface Cards can contain Network Interface or Subslots. |
| Network Interface CI | Any type of Network Interface is represented by the Network Interface CI. Table name: **cmdb\_ci\_ni\_interface** Network Interface is contained by Interface Card, IP Router. |
|
https://www.servicenow.com/docs/en-US/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/telecom-discovery-using-service-graph-connector.html | https://servicenow-be-prod.servicenow.com/api/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/telecom-discovery-using-service-graph-connector.html | 2025-08-02 | daily | 0.5 | 268.xml | en-US | zurich-telecom-service-ops | product/tmt-telecom-service-operations-mgt/concept/telecom-discovery-using-service-graph-connector.html | zurich | Indirect Discovery using Service Graph Connectors | ServiceNow Telecom Discovery using Service Graph Connectors (SGCs) enables you to seamlessly integrate network infrastructure data from external management systems—such as EMS, NMS, and SDN Controllers—into the Configuration Management Database (CMDB). | [] | [
"Telecommunications Service Operations Management",
"Exploring Telecommunications Service Operations Management",
"Telecom Visibility",
"Telecom Discovery"
] | <article class="hascomments" data-page="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/telecom-discovery-using-service-graph-connector.html" id="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/telecom-discovery-using-service-graph-connector.html"><body id="telecom-discovery-using-service-graph-connector"><main role="main"><article role="article" class="dita" id="telecom-discovery-using-service-graph-connector" aria-labelledby="title_telecom-discovery-using-service-graph-connector">
<h1 class="title topictitle1" id="title_telecom-discovery-using-service-graph-connector">Indirect Discovery using Service Graph Connectors</h1>
<div class="body conbody"><p class="shortdesc">ServiceNow Telecom Discovery using Service Graph Connectors (SGCs) enables you to seamlessly integrate network infrastructure data from external management systems—such as EMS, NMS, and SDN Controllers—into the Configuration
Management Database (CMDB).</p>
<p class="p">This approach helps Communication Service Providers (CSPs) maintain a current and accurate view of their multivendor telecom network resources, services, and configurations.</p>
<div class="p">By leveraging predefined connectors and robust data transformation tools, you can unify your inventory across domains and ensure that the CMDB and Telecom Network Inventory (TNI) reflect real-time network insights aligned with your
telecom data model.<div class="note note note_note"><span class="note__title">Note:</span> Telecom Service Graph Connectors are part of the TSOM Visibility subscription and extend the capabilities of the standard Service Graph Connector framework.</div></div>
<section class="section" id="telecom-discovery-using-service-graph-connector__section_p43_q4p_vfc"><h2 id="d9034e50" class="title sectiontitle">Service Graph Connector overview</h2>
<p class="p">With Telecom SGC, you can:</p>
<ul class="ul" id="telecom-discovery-using-service-graph-connector__ul_clm_r4p_vfc">
<li class="li">Ingest data from EMS/NMS/Controllers using northbound REST APIs.</li>
<li class="li">Automatically populate and update CMDB and TNI records with enriched, telecom-aligned data.</li>
<li class="li">Reconcile incoming data with existing CI records using the Identification and Reconciliation Engine (IRE).</li>
<li class="li">Generate TNI entity records automatically when the TNI plugin is installed.</li>
<li class="li">Support discrepancy detection and remediation as part of Telecom Discrepancy Identification & Reconciliation.</li>
<li class="li">Use low-code tools to configure, test, and manage your integrations end-to-end.</li>
</ul>
</section>
<section class="section" id="telecom-discovery-using-service-graph-connector__section_pxz_t4p_vfc"><h2 id="d9034e81" class="title sectiontitle">Architecture overview</h2>
<div class="p">Telecom Service Graph Connectors rely on a modular and scalable architecture:<div class="table-wrap"><table count-columns="2" class="table frame-all" id="telecom-discovery-using-service-graph-connector__table_nvz_34q_vfc"><caption><span class="table--title-label">Table 1. </span><span class="title">Key components of Service Graph Connector</span></caption><colgroup><col style="width:50%"/><col style="width:50%"/></colgroup><thead class="thead">
<tr class="row">
<th class="entry colsep-1 rowsep-1" id="telecom-discovery-using-service-graph-connector__table_nvz_34q_vfc__entry__1">Component</th>
<th class="entry colsep-1 rowsep-1" id="telecom-discovery-using-service-graph-connector__table_nvz_34q_vfc__entry__2">Role</th>
</tr>
</thead><tbody class="tbody">
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="telecom-discovery-using-service-graph-connector__table_nvz_34q_vfc__entry__1">Service Graph Connector</td>
<td class="entry colsep-1 rowsep-1" headers="telecom-discovery-using-service-graph-connector__table_nvz_34q_vfc__entry__2">Defines the integration logic to extract and stage data from EMS/NMS systems (for example, Nokia Altiplano or Nokia NSP).</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="telecom-discovery-using-service-graph-connector__table_nvz_34q_vfc__entry__1">MID Server</td>
<td class="entry colsep-1 rowsep-1" headers="telecom-discovery-using-service-graph-connector__table_nvz_34q_vfc__entry__2">Acts as a secure bridge between your ServiceNow instance and the external network system. <p class="p">For more information, see <a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/concept//csh" href="https://servicenow-be-prod.servicenow.com/csh?topicname=integrationhub-etl&version=zurich&pubname=zurich-servicenow-platform" class="xref">IntegrationHub ETL</a>.</p></td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="telecom-discovery-using-service-graph-connector__table_nvz_34q_vfc__entry__1">IntegrationHub ETL (3.2)</td>
<td class="entry colsep-1 rowsep-1" headers="telecom-discovery-using-service-graph-connector__table_nvz_34q_vfc__entry__2">Provides a guided UI for creating, testing, and managing ETL transform maps.<p class="p">For more information, see <a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/concept//csh" href="https://servicenow-be-prod.servicenow.com/csh?topicname=mid-server-landing&version=zurich&pubname=zurich-servicenow-platform" class="xref">MID Server</a>.</p></td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="telecom-discovery-using-service-graph-connector__table_nvz_34q_vfc__entry__1">Robust Transform Engine (RTE)</td>
<td class="entry colsep-1 rowsep-1" headers="telecom-discovery-using-service-graph-connector__table_nvz_34q_vfc__entry__2">Transforms staged source data into CMDB-compliant records using defined ETL logic. <p class="p">For more information, see <a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/concept//csh" href="https://servicenow-be-prod.servicenow.com/csh?topicname=create-robust-import-set-transformer&version=zurich&pubname=zurich-integrate-applications" class="xref">Create a robust import set transformer</a>.</p></td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="telecom-discovery-using-service-graph-connector__table_nvz_34q_vfc__entry__1">Identification and Reconciliation Engine (IRE)</td>
<td class="entry colsep-1 rowsep-1" headers="telecom-discovery-using-service-graph-connector__table_nvz_34q_vfc__entry__2">Ensures data consistency and prevents duplicates by identifying and reconciling CIs.<p class="p">For more information, see the <a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/concept//csh" href="https://servicenow-be-prod.servicenow.com/csh?topicname=c_CMDBIdentifyandReconcile&version=zurich&pubname=zurich-servicenow-platform" class="xref">CMDB Identification and Reconciliation (IRE)</a>.</p></td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="telecom-discovery-using-service-graph-connector__table_nvz_34q_vfc__entry__1">CMDB/TNI</td>
<td class="entry colsep-1 rowsep-1" headers="telecom-discovery-using-service-graph-connector__table_nvz_34q_vfc__entry__2">Stores structured, accurate telecom infrastructure data for visibility and downstream processes.</td>
</tr>
</tbody></table></div></div>
</section>
<section class="section" id="telecom-discovery-using-service-graph-connector__section_nng_1pt_vfc"><h2 id="d9034e196" class="title sectiontitle">Supported Service Graph Connectors</h2>
<div class="p">
<ul class="ul" id="telecom-discovery-using-service-graph-connector__ul_f4l_bpt_vfc">
<li class="li">Nokia Altiplano SGC (sn_sgc_altiplano_connector): Integrates with the Nokia Altiplano Access Network SDN Controller via REST APIs.</li>
</ul>
<div class="note note note_note"><span class="note__title">Note:</span> The connector can coexist with IT and Cloud Service Graph Connectors (e.g., for servers, monitoring tools, IoT, etc.).</div>
</div>
</section>
<section class="section" id="telecom-discovery-using-service-graph-connector__section_tsr_wpt_vfc"><h2 id="d9034e215" class="title sectiontitle">Key benefits</h2>
<div class="p">
<ul class="ul" id="telecom-discovery-using-service-graph-connector__ul_fr2_xpt_vfc">
<li class="li">Fast time to value – Use predefined, supported connectors that require minimal configuration.</li>
<li class="li">Multivendor support – Integrate with various management platforms across access, core, and transport networks.</li>
<li class="li">Model-aligned visibility – Ensure telecom-specific hierarchy and relationships are accurately modeled in the CMDB.</li>
<li class="li">Discrepancy detection ready – Feed network data directly into Telecom Discrepancy Identification & Reconciliation for CMDB compliance.</li>
<li class="li">Scalable integration – Leverage ServiceNow’s proven integration framework built for performance and extensibility.</li>
</ul>
</div>
</section>
<section class="section" id="telecom-discovery-using-service-graph-connector__section_v2r_zsf_12c"><h2 id="d9034e242" class="title sectiontitle">Telecom Network Inventory (TNI) data model</h2>
<p class="p">Telecom SGCs include logic to ensure compatibility with the Telecom Network Inventory (TNI) data model:</p>
<ul class="ul" id="telecom-discovery-using-service-graph-connector__ul_t3w_3qt_vfc">
<li class="li">When the TNI plugin is installed, each discovered network element automatically includes a TNI entity record.</li>
<li class="li">A <code class="ph codeph">tni_entity</code> is created alongside its corresponding <code class="ph codeph">cmdb_ci</code> record, using system-generated payload mappings (e.g., <code class="ph codeph">inventory_category</code>).</li>
<li class="li">This ensures consistency across operational and planning systems.</li>
</ul>
<div class="p">If TNI is installed, a payload like the following one will be added to the IRE payload for each item (with inventory_category populated based on the className):<pre class="prettyprint language-plaintext"><code class="pre codeblock language-plaintext">related = [{
"className": "tni_entity",
"values": {
"inventory_category": ""
}
}];
</code></pre>As a result, the discovered CI is in both the cmdb_ci and tni_entity tables.</div>
</section>
</div>
<nav role="navigation"></nav><nav role="navigation" class="tasksNavigation"></nav><nav role="navigation" class="related-links"><div class="col-md-4"><dt>Related concepts</dt><dd><ul><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/concept/service-graph-connector-for-nokia-altiplano.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/service-graph-connector-for-nokia-altiplano.html" class="link" title="The Service Graph Connector for Nokia Altiplano offers a telecom-aware integration that brings real-time network inventory from the Nokia Altiplano Access Network SDN Controller into your ServiceNow CMDB.">Telecom Discovery via Nokia Altiplano</a></li></ul></dd></div></nav>
</article></main></body></article> | {
"attachments": {
"all_attachments": null,
"topic_attachments": []
},
"available_languages": [
"enus"
],
"breadcrumbs": [
{
"title": "Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html"
},
{
"title": "Exploring Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/exploring-tsom.html"
},
{
"title": "Telecom Visibility",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/tsom-visibility.html"
},
{
"title": "Telecom Discovery",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/exploring-telecom-discovery.html"
}
],
"breadcrumbs_html": "<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops\">Zurich Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html\">Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/exploring-tsom.html\">Exploring Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/tsom-visibility.html\">Telecom Visibility</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/exploring-telecom-discovery.html\">Telecom Discovery</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<span class=\"active\">Indirect Discovery using Service Graph Connectors</span>",
"bundle_id": "zurich-telecom-service-ops",
"bundle_key": 2733,
"bundle_landing_page": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html",
"bundle_subtitle": null,
"bundle_title": "Zurich Telecommunications Service Operations Management",
"canonical_link": null,
"dates": {
"Added on": "2025-08-02T00:48:08.794016Z",
"Created on": "2024-12-06T00:00:00Z",
"Initial upload": "2025-07-30T22:24:33.519043Z",
"Updated on": "2025-07-31T00:00:00Z"
},
"dislike_url": "https://servicenow-be-prod.servicenow.com/dislike/55686942",
"dislikes": 0,
"es_archived_content": false,
"is_in_fav": false,
"is_liked": null,
"is_watched": false,
"keywords": [
" zurich zurich"
],
"labels": [
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "zurich",
"navtitle": "Zurich",
"outputclasses": [],
"subjectHeadId": "versions",
"subjectheadNavtitle": "Versions",
"visibility": "show-facet"
},
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "tsom",
"navtitle": "Telecommunications Service Operations Management",
"outputclasses": [],
"subjectHeadId": "products",
"subjectheadNavtitle": "Products",
"visibility": "show-facet"
}
],
"labels_text": "Versions > Zurich; Products > CRM and Industry Products > Telecommunications Media and Technology Assurance > Telecommunications Service Operations Management",
"like_url": "https://servicenow-be-prod.servicenow.com/like/55686942",
"likes": 0,
"metadata": {
"AI Search": null,
"AI Search Assist": null,
"Application Insights": null,
"Capabilities": null,
"Code Signing": null,
"Contextual Search": null,
"DC.contributor": null,
"DC.coverage": null,
"DC.creator": "ServiceNow",
"DC.date.created": "2024-12-06T10:54:03+05:30",
"DC.date.modified": "2025-07-31",
"DC.format": "HTML5",
"DC.identifier": "telecom-discovery-using-service-graph-connector",
"DC.language": null,
"DC.relation": "service-graph-connector-for-nokia-altiplano.html",
"DC.rights.owner": "(C) Copyright 2025",
"DC.subject": null,
"DC.type": "concept",
"Data Discovery": null,
"Data Policy": null,
"Data Privacy": null,
"Discovery": null,
"External Content for AI Search": null,
"Field Administration": null,
"Field Normalization": null,
"Key Management Framework": null,
"Localization Framework": null,
"Now Platform": null,
"PlatSec": null,
"Platform": null,
"Platform Administration": null,
"Platform Performance": null,
"Platform Privacy": null,
"Proactive Triggers": null,
"Process Optimization": null,
"RN doc editing record number": null,
"Search Administration": null,
"Secrets Management": null,
"ServiceNow AI Platform": null,
"State Model": null,
"Subscription Management": null,
"Task Communications Management": null,
"Timeline Visualizations": null,
"User Administration": null,
"User Experience Analytics": null,
"Zing": null,
"ai-now-assist": null,
"app-name": null,
"app_route": null,
"azureapimanagemen": null,
"change-completed": null,
"change-item": null,
"change-request-id": null,
"change-request-reference": null,
"com.glide.embedded_help.category": null,
"component": null,
"copyright": "(C) Copyright 2025",
"crossroads": null,
"data": null,
"description": "ServiceNow Telecom Discovery using Service Graph Connectors (SGCs) enables you to seamlessly integrate network infrastructure data from external management systems—such as EMS, NMS, and SDN Controllers—into the Configuration Management Database (CMDB).",
"dominant_bundle": null,
"erp-canvas-video": null,
"fsm-mobile": null,
"fsm-route": null,
"fsm-sched-opt": null,
"fsm-wrk-order": null,
"genai-round-7": null,
"generator": "DITA-OT",
"glossPartOfSpeech": null,
"glossStatus": null,
"guided setup": null,
"guided tours": null,
"keywords": null,
"min-toc": null,
"mini": null,
"mini-to truec": null,
"mini-toc": "yes",
"mini_toc": null,
"minitoc": null,
"modification": null,
"now-assist-app-gen-video": null,
"order": null,
"page-type": null,
"page-type ": null,
"prodname": null,
"product": null,
"product_name": null,
"release": null,
"resourceID": null,
"roles": null,
"route_page": null,
"route_params_listId": null,
"route_params_table": null,
"route_params_type": null,
"route_type": null,
"setconfigurationproperties": null,
"topic": null,
"translation-type": "source",
"version": null,
"workflow": "Customer and Industry",
"workplace-srvc-delvry-ditamap": null
},
"page_id": "product/tmt-telecom-service-operations-mgt/concept/telecom-discovery-using-service-graph-connector.html",
"page_key": 55686942,
"preprocessed_PDF": "https://downloads.docs.servicenow.com/pdf/enus/servicenow-zurich-telecom-service-ops-enus.pdf",
"rating": null,
"read_time_data": {
"char_count": 4228,
"img_count": 0,
"read_time": 3,
"video_links": [
""
],
"word_count": 566
},
"related_links": [
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "The Service Graph Connector for Nokia Altiplano offers a telecom-aware integration that brings real-time network inventory from the Nokia Altiplano Access Network SDN Controller into your ServiceNow CMDB.",
"title": "Telecom Discovery via Nokia Altiplano",
"topic": "/product/tmt-telecom-service-operations-mgt/concept/service-graph-connector-for-nokia-altiplano.html",
"type": "concept",
"url": null
}
],
"search_title": null,
"title": "Indirect Discovery using Service Graph Connectors",
"topic_cluster": {
"clustered_by": {
"enabled": true,
"primary_key": "versions",
"primary_sort": "top-down",
"type": "subjecthead"
},
"clustered_labels": [
"versions"
],
"clustered_topics": [
{
"bundle_id": "yokohama-telecom-service-ops",
"clustering_title": "Yokohama",
"es_archived_content": false,
"page_id": "product/tmt-telecom-service-operations-mgt/concept/telecom-discovery-using-service-graph-connector.html"
}
],
"clustering_title": "Zurich"
},
"topic_html": "<article class=\"hascomments\" data-page=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/telecom-discovery-using-service-graph-connector.html\" id=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/telecom-discovery-using-service-graph-connector.html\"><body id=\"telecom-discovery-using-service-graph-connector\"><main role=\"main\"><article role=\"article\" class=\"dita\" id=\"telecom-discovery-using-service-graph-connector\" aria-labelledby=\"title_telecom-discovery-using-service-graph-connector\">\n <h1 class=\"title topictitle1\" id=\"title_telecom-discovery-using-service-graph-connector\">Indirect Discovery using Service Graph Connectors</h1>\n \n \n <div class=\"body conbody\"><p class=\"shortdesc\">ServiceNow Telecom Discovery using Service Graph Connectors (SGCs) enables you to seamlessly integrate network infrastructure data from external management systems—such as EMS, NMS, and SDN Controllers—into the Configuration\n Management Database (CMDB).</p>\n <p class=\"p\">This approach helps Communication Service Providers (CSPs) maintain a current and accurate view of their multivendor telecom network resources, services, and configurations.</p>\n <div class=\"p\">By leveraging predefined connectors and robust data transformation tools, you can unify your inventory across domains and ensure that the CMDB and Telecom Network Inventory (TNI) reflect real-time network insights aligned with your\n telecom data model.<div class=\"note note note_note\"><span class=\"note__title\">Note:</span> Telecom Service Graph Connectors are part of the TSOM Visibility subscription and extend the capabilities of the standard Service Graph Connector framework.</div></div>\n <section class=\"section\" id=\"telecom-discovery-using-service-graph-connector__section_p43_q4p_vfc\"><h2 id=\"d9034e50\" class=\"title sectiontitle\">Service Graph Connector overview</h2>\n \n <p class=\"p\">With Telecom SGC, you can:</p>\n <ul class=\"ul\" id=\"telecom-discovery-using-service-graph-connector__ul_clm_r4p_vfc\">\n <li class=\"li\">Ingest data from EMS/NMS/Controllers using northbound REST APIs.</li>\n <li class=\"li\">Automatically populate and update CMDB and TNI records with enriched, telecom-aligned data.</li>\n <li class=\"li\">Reconcile incoming data with existing CI records using the Identification and Reconciliation Engine (IRE).</li>\n <li class=\"li\">Generate TNI entity records automatically when the TNI plugin is installed.</li>\n <li class=\"li\">Support discrepancy detection and remediation as part of Telecom Discrepancy Identification & Reconciliation.</li>\n <li class=\"li\">Use low-code tools to configure, test, and manage your integrations end-to-end.</li>\n </ul>\n </section>\n <section class=\"section\" id=\"telecom-discovery-using-service-graph-connector__section_pxz_t4p_vfc\"><h2 id=\"d9034e81\" class=\"title sectiontitle\">Architecture overview</h2>\n \n <div class=\"p\">Telecom Service Graph Connectors rely on a modular and scalable architecture:<div class=\"table-wrap\"><table count-columns=\"2\" class=\"table frame-all\" id=\"telecom-discovery-using-service-graph-connector__table_nvz_34q_vfc\"><caption><span class=\"table--title-label\">Table 1. </span><span class=\"title\">Key components of Service Graph Connector</span></caption><colgroup><col style=\"width:50%\"/><col style=\"width:50%\"/></colgroup><thead class=\"thead\">\n <tr class=\"row\">\n <th class=\"entry colsep-1 rowsep-1\" id=\"telecom-discovery-using-service-graph-connector__table_nvz_34q_vfc__entry__1\">Component</th>\n <th class=\"entry colsep-1 rowsep-1\" id=\"telecom-discovery-using-service-graph-connector__table_nvz_34q_vfc__entry__2\">Role</th>\n </tr>\n </thead><tbody class=\"tbody\">\n <tr class=\"row\">\n <td class=\"entry colsep-1 rowsep-1\" headers=\"telecom-discovery-using-service-graph-connector__table_nvz_34q_vfc__entry__1\">Service Graph Connector</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"telecom-discovery-using-service-graph-connector__table_nvz_34q_vfc__entry__2\">Defines the integration logic to extract and stage data from EMS/NMS systems (for example, Nokia Altiplano or Nokia NSP).</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry colsep-1 rowsep-1\" headers=\"telecom-discovery-using-service-graph-connector__table_nvz_34q_vfc__entry__1\">MID Server</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"telecom-discovery-using-service-graph-connector__table_nvz_34q_vfc__entry__2\">Acts as a secure bridge between your ServiceNow instance and the external network system. <p class=\"p\">For more information, see <a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept//csh\" href=\"https://servicenow-be-prod.servicenow.com/csh?topicname=integrationhub-etl&version=zurich&pubname=zurich-servicenow-platform\" class=\"xref\">IntegrationHub ETL</a>.</p></td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry colsep-1 rowsep-1\" headers=\"telecom-discovery-using-service-graph-connector__table_nvz_34q_vfc__entry__1\">IntegrationHub ETL (3.2)</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"telecom-discovery-using-service-graph-connector__table_nvz_34q_vfc__entry__2\">Provides a guided UI for creating, testing, and managing ETL transform maps.<p class=\"p\">For more information, see <a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept//csh\" href=\"https://servicenow-be-prod.servicenow.com/csh?topicname=mid-server-landing&version=zurich&pubname=zurich-servicenow-platform\" class=\"xref\">MID Server</a>.</p></td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry colsep-1 rowsep-1\" headers=\"telecom-discovery-using-service-graph-connector__table_nvz_34q_vfc__entry__1\">Robust Transform Engine (RTE)</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"telecom-discovery-using-service-graph-connector__table_nvz_34q_vfc__entry__2\">Transforms staged source data into CMDB-compliant records using defined ETL logic. <p class=\"p\">For more information, see <a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept//csh\" href=\"https://servicenow-be-prod.servicenow.com/csh?topicname=create-robust-import-set-transformer&version=zurich&pubname=zurich-integrate-applications\" class=\"xref\">Create a robust import set transformer</a>.</p></td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry colsep-1 rowsep-1\" headers=\"telecom-discovery-using-service-graph-connector__table_nvz_34q_vfc__entry__1\">Identification and Reconciliation Engine (IRE)</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"telecom-discovery-using-service-graph-connector__table_nvz_34q_vfc__entry__2\">Ensures data consistency and prevents duplicates by identifying and reconciling CIs.<p class=\"p\">For more information, see the <a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept//csh\" href=\"https://servicenow-be-prod.servicenow.com/csh?topicname=c_CMDBIdentifyandReconcile&version=zurich&pubname=zurich-servicenow-platform\" class=\"xref\">CMDB Identification and Reconciliation (IRE)</a>.</p></td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry colsep-1 rowsep-1\" headers=\"telecom-discovery-using-service-graph-connector__table_nvz_34q_vfc__entry__1\">CMDB/TNI</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"telecom-discovery-using-service-graph-connector__table_nvz_34q_vfc__entry__2\">Stores structured, accurate telecom infrastructure data for visibility and downstream processes.</td>\n </tr>\n </tbody></table></div></div>\n </section>\n <section class=\"section\" id=\"telecom-discovery-using-service-graph-connector__section_nng_1pt_vfc\"><h2 id=\"d9034e196\" class=\"title sectiontitle\">Supported Service Graph Connectors</h2>\n \n <div class=\"p\">\n <ul class=\"ul\" id=\"telecom-discovery-using-service-graph-connector__ul_f4l_bpt_vfc\">\n <li class=\"li\">Nokia Altiplano SGC (sn_sgc_altiplano_connector): Integrates with the Nokia Altiplano Access Network SDN Controller via REST APIs.</li>\n \n </ul>\n <div class=\"note note note_note\"><span class=\"note__title\">Note:</span> The connector can coexist with IT and Cloud Service Graph Connectors (e.g., for servers, monitoring tools, IoT, etc.).</div>\n </div>\n </section>\n <section class=\"section\" id=\"telecom-discovery-using-service-graph-connector__section_tsr_wpt_vfc\"><h2 id=\"d9034e215\" class=\"title sectiontitle\">Key benefits</h2>\n \n <div class=\"p\">\n <ul class=\"ul\" id=\"telecom-discovery-using-service-graph-connector__ul_fr2_xpt_vfc\">\n <li class=\"li\">Fast time to value – Use predefined, supported connectors that require minimal configuration.</li>\n <li class=\"li\">Multivendor support – Integrate with various management platforms across access, core, and transport networks.</li>\n <li class=\"li\">Model-aligned visibility – Ensure telecom-specific hierarchy and relationships are accurately modeled in the CMDB.</li>\n <li class=\"li\">Discrepancy detection ready – Feed network data directly into Telecom Discrepancy Identification & Reconciliation for CMDB compliance.</li>\n <li class=\"li\">Scalable integration – Leverage ServiceNow’s proven integration framework built for performance and extensibility.</li>\n </ul>\n </div>\n </section>\n <section class=\"section\" id=\"telecom-discovery-using-service-graph-connector__section_v2r_zsf_12c\"><h2 id=\"d9034e242\" class=\"title sectiontitle\">Telecom Network Inventory (TNI) data model</h2>\n \n <p class=\"p\">Telecom SGCs include logic to ensure compatibility with the Telecom Network Inventory (TNI) data model:</p>\n <ul class=\"ul\" id=\"telecom-discovery-using-service-graph-connector__ul_t3w_3qt_vfc\">\n <li class=\"li\">When the TNI plugin is installed, each discovered network element automatically includes a TNI entity record.</li>\n <li class=\"li\">A <code class=\"ph codeph\">tni_entity</code> is created alongside its corresponding <code class=\"ph codeph\">cmdb_ci</code> record, using system-generated payload mappings (e.g., <code class=\"ph codeph\">inventory_category</code>).</li>\n <li class=\"li\">This ensures consistency across operational and planning systems.</li>\n </ul>\n <div class=\"p\">If TNI is installed, a payload like the following one will be added to the IRE payload for each item (with inventory_category populated based on the className):<pre class=\"prettyprint language-plaintext\"><code class=\"pre codeblock language-plaintext\">related = [{\n "className": "tni_entity",\n "values": {\n "inventory_category": ""\n }\n }];\n</code></pre>As a result, the discovered CI is in both the cmdb_ci and tni_entity tables.</div>\n </section>\n </div>\n <nav role=\"navigation\"></nav><nav role=\"navigation\" class=\"tasksNavigation\"></nav><nav role=\"navigation\" class=\"related-links\"><div class=\"col-md-4\"><dt>Related concepts</dt><dd><ul><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept/service-graph-connector-for-nokia-altiplano.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/service-graph-connector-for-nokia-altiplano.html\" class=\"link\" title=\"The Service Graph Connector for Nokia Altiplano offers a telecom-aware integration that brings real-time network inventory from the Nokia Altiplano Access Network SDN Controller into your ServiceNow CMDB.\">Telecom Discovery via Nokia Altiplano</a></li></ul></dd></div></nav>\n</article></main></body></article>",
"topic_language": "enus",
"views": 0,
"your_rating": null
} | # Indirect Discovery using Service Graph Connectors
ServiceNow Telecom Discovery using Service Graph Connectors (SGCs) enables you to seamlessly integrate network infrastructure data from external management systems—such as EMS, NMS, and SDN Controllers—into the Configuration
Management Database (CMDB).
This approach helps Communication Service Providers (CSPs) maintain a current and accurate view of their multivendor telecom network resources, services, and configurations.
By leveraging predefined connectors and robust data transformation tools, you can unify your inventory across domains and ensure that the CMDB and Telecom Network Inventory (TNI) reflect real-time network insights aligned with your
telecom data model.Note: Telecom Service Graph Connectors are part of the TSOM Visibility subscription and extend the capabilities of the standard Service Graph Connector framework.
## Service Graph Connector overview
With Telecom SGC, you can:
* Ingest data from EMS/NMS/Controllers using northbound REST APIs.
* Automatically populate and update CMDB and TNI records with enriched, telecom-aligned data.
* Reconcile incoming data with existing CI records using the Identification and Reconciliation Engine (IRE).
* Generate TNI entity records automatically when the TNI plugin is installed.
* Support discrepancy detection and remediation as part of Telecom Discrepancy Identification & Reconciliation.
* Use low-code tools to configure, test, and manage your integrations end-to-end.
## Architecture overview
Telecom Service Graph Connectors rely on a modular and scalable architecture:
Table 1. Key components of Service Graph Connector
| Component | Role |
| --- | --- |
| Service Graph Connector | Defines the integration logic to extract and stage data from EMS/NMS systems (for example, Nokia Altiplano or Nokia NSP). |
| MID Server | Acts as a secure bridge between your ServiceNow instance and the external network system. For more information, see IntegrationHub ETL. |
| IntegrationHub ETL (3.2) | Provides a guided UI for creating, testing, and managing ETL transform maps. For more information, see MID Server. |
| Robust Transform Engine (RTE) | Transforms staged source data into CMDB-compliant records using defined ETL logic. For more information, see Create a robust import set transformer. |
| Identification and Reconciliation Engine (IRE) | Ensures data consistency and prevents duplicates by identifying and reconciling CIs. For more information, see the CMDB Identification and Reconciliation (IRE). |
| CMDB/TNI | Stores structured, accurate telecom infrastructure data for visibility and downstream processes. |
## Supported Service Graph Connectors
* Nokia Altiplano SGC (sn\_sgc\_altiplano\_connector): Integrates with the Nokia Altiplano Access Network SDN Controller via REST APIs.
Note: The connector can coexist with IT and Cloud Service Graph Connectors (e.g., for servers, monitoring tools, IoT, etc.).
## Key benefits
* Fast time to value – Use predefined, supported connectors that require minimal configuration.
* Multivendor support – Integrate with various management platforms across access, core, and transport networks.
* Model-aligned visibility – Ensure telecom-specific hierarchy and relationships are accurately modeled in the CMDB.
* Discrepancy detection ready – Feed network data directly into Telecom Discrepancy Identification & Reconciliation for CMDB compliance.
* Scalable integration – Leverage ServiceNow’s proven integration framework built for performance and extensibility.
## Telecom Network Inventory (TNI) data model
Telecom SGCs include logic to ensure compatibility with the Telecom Network Inventory (TNI) data model:
* When the TNI plugin is installed, each discovered network element automatically includes a TNI entity record.
* A `tni_entity` is created alongside its corresponding `cmdb_ci` record, using system-generated payload mappings (e.g., `inventory_category`).
* This ensures consistency across operational and planning systems.
If TNI is installed, a payload like the following one will be added to the IRE payload for each item (with inventory\_category populated based on the className):
```None
related = [{
"className": "tni_entity",
"values": {
"inventory_category": ""
}
}];
```
As a result, the discovered CI is in both the cmdb\_ci and tni\_entity tables.
| ---
title: Indirect Discovery using Service Graph Connectors
description: "ServiceNow Telecom Discovery using Service Graph Connectors (SGCs) enables\
\ you to seamlessly integrate network infrastructure data from external management\
\ systems\u2014such as EMS, NMS, and SDN Controllers\u2014into the Configuration\
\ Management Database (CMDB)."
keywords: []
breadcrumbs:
- Telecommunications Service Operations Management
- Exploring Telecommunications Service Operations Management
- Telecom Visibility
- Telecom Discovery
---
# Indirect Discovery using Service Graph Connectors
ServiceNow Telecom Discovery using Service Graph Connectors (SGCs) enables you to seamlessly integrate network infrastructure data from external management systems—such as EMS, NMS, and SDN Controllers—into the Configuration
Management Database (CMDB).
This approach helps Communication Service Providers (CSPs) maintain a current and accurate view of their multivendor telecom network resources, services, and configurations.
By leveraging predefined connectors and robust data transformation tools, you can unify your inventory across domains and ensure that the CMDB and Telecom Network Inventory (TNI) reflect real-time network insights aligned with your
telecom data model.Note: Telecom Service Graph Connectors are part of the TSOM Visibility subscription and extend the capabilities of the standard Service Graph Connector framework.
## Service Graph Connector overview
With Telecom SGC, you can:
* Ingest data from EMS/NMS/Controllers using northbound REST APIs.
* Automatically populate and update CMDB and TNI records with enriched, telecom-aligned data.
* Reconcile incoming data with existing CI records using the Identification and Reconciliation Engine (IRE).
* Generate TNI entity records automatically when the TNI plugin is installed.
* Support discrepancy detection and remediation as part of Telecom Discrepancy Identification & Reconciliation.
* Use low-code tools to configure, test, and manage your integrations end-to-end.
## Architecture overview
Telecom Service Graph Connectors rely on a modular and scalable architecture:
Table 1. Key components of Service Graph Connector
| Component | Role |
| --- | --- |
| Service Graph Connector | Defines the integration logic to extract and stage data from EMS/NMS systems (for example, Nokia Altiplano or Nokia NSP). |
| MID Server | Acts as a secure bridge between your ServiceNow instance and the external network system. For more information, see IntegrationHub ETL. |
| IntegrationHub ETL (3.2) | Provides a guided UI for creating, testing, and managing ETL transform maps. For more information, see MID Server. |
| Robust Transform Engine (RTE) | Transforms staged source data into CMDB-compliant records using defined ETL logic. For more information, see Create a robust import set transformer. |
| Identification and Reconciliation Engine (IRE) | Ensures data consistency and prevents duplicates by identifying and reconciling CIs. For more information, see the CMDB Identification and Reconciliation (IRE). |
| CMDB/TNI | Stores structured, accurate telecom infrastructure data for visibility and downstream processes. |
## Supported Service Graph Connectors
* Nokia Altiplano SGC (sn\_sgc\_altiplano\_connector): Integrates with the Nokia Altiplano Access Network SDN Controller via REST APIs.
Note: The connector can coexist with IT and Cloud Service Graph Connectors (e.g., for servers, monitoring tools, IoT, etc.).
## Key benefits
* Fast time to value – Use predefined, supported connectors that require minimal configuration.
* Multivendor support – Integrate with various management platforms across access, core, and transport networks.
* Model-aligned visibility – Ensure telecom-specific hierarchy and relationships are accurately modeled in the CMDB.
* Discrepancy detection ready – Feed network data directly into Telecom Discrepancy Identification & Reconciliation for CMDB compliance.
* Scalable integration – Leverage ServiceNow’s proven integration framework built for performance and extensibility.
## Telecom Network Inventory (TNI) data model
Telecom SGCs include logic to ensure compatibility with the Telecom Network Inventory (TNI) data model:
* When the TNI plugin is installed, each discovered network element automatically includes a TNI entity record.
* A `tni_entity` is created alongside its corresponding `cmdb_ci` record, using system-generated payload mappings (e.g., `inventory_category`).
* This ensures consistency across operational and planning systems.
If TNI is installed, a payload like the following one will be added to the IRE payload for each item (with inventory\_category populated based on the className):
```None
related = [{
"className": "tni_entity",
"values": {
"inventory_category": ""
}
}];
```
As a result, the discovered CI is in both the cmdb\_ci and tni\_entity tables.
|
https://www.servicenow.com/docs/en-US/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/telecom-discovery-using-telecommunication-discovery-pattern.html | https://servicenow-be-prod.servicenow.com/api/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/telecom-discovery-using-telecommunication-discovery-pattern.html | 2025-08-02 | daily | 0.5 | 268.xml | en-US | zurich-telecom-service-ops | product/tmt-telecom-service-operations-mgt/concept/telecom-discovery-using-telecommunication-discovery-pattern.html | zurich | Direct Discovery using Discovery Patterns | The Telecommunications Discovery Patterns plugin (also known as TSOM Patterns) extends ServiceNow AI Platform Telecom Discovery to support direct discovery of standalone network elements—such as routers and switches—without relying on traditional network management systems. These patterns enable Communication Service Providers | [] | [
"Telecommunications Service Operations Management",
"Exploring Telecommunications Service Operations Management",
"Telecom Visibility",
"Telecom Discovery"
] | <article class="hascomments" data-page="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/telecom-discovery-using-telecommunication-discovery-pattern.html" id="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/telecom-discovery-using-telecommunication-discovery-pattern.html"><body id="telecom-discovery-using-telecommunication-discovery-pattern"><main role="main"><article role="article" class="dita" id="telecom-discovery-using-telecommunication-discovery-pattern" aria-labelledby="title_telecom-discovery-using-telecommunication-discovery-pattern">
<h1 class="title topictitle1" id="title_telecom-discovery-using-telecommunication-discovery-pattern">Direct Discovery using Discovery Patterns</h1>
<div class="body conbody"><p class="shortdesc">The Telecommunications Discovery Patterns plugin (also known as TSOM Patterns) extends <span class="ph">ServiceNow AI Platform</span> Telecom Discovery to support direct discovery of standalone network elements—such as routers and switches—without relying on traditional network management systems. These patterns enable Communication Service
Providers (CSPs) to identify and map multivendor xNFs using protocols like SNMP and CLI, with support for NETCONF.</p>
<p class="p">Telecommunications Discovery Patterns provide a powerful, pattern-based approach to discover and manage telecom network resources directly from network elements. These patterns are especially valuable for discovering standalone xNFs
(such as routers and switches) that are not managed through traditional EMS/NMS systems.</p>
<div class="p">This capability enhances visibility across telecom infrastructures and ensures that both vendor-neutral and vendor-specific device data is captured and reflected in the CMDB and Telecom Network Inventory (TNI), following the TNI data
model.<div class="note note note_note"><span class="note__title">Note:</span> Telecommunications Discovery Patterns are part of the TSOM Visibility subscription and are available as a customer-visible plugin from the ServiceNow Store.</div></div>
<section class="section" id="telecom-discovery-using-telecommunication-discovery-pattern__section_jpv_n5y_5fc"><h2 id="d4908e53" class="title sectiontitle">Key capabilities</h2>
<div class="p">
<ul class="ul" id="telecom-discovery-using-telecommunication-discovery-pattern__ul_xhc_q5y_5fc">
<li class="li">Direct Network Element Discovery<ul class="ul" id="telecom-discovery-using-telecommunication-discovery-pattern__ul_xzp_1z2_wfc">
<li class="li">Use SNMP, CLI, and NETCONF to communicate directly with physical network elements.</li>
<li class="li">Discover physical network inventory such as interface cards, slots, ports, and devices without relying on EMS/NMS mediation.</li>
</ul></li>
<li class="li">Automated CI Mapping and CMDB Integration<ul class="ul" id="telecom-discovery-using-telecommunication-discovery-pattern__ul_yzp_1z2_wfc">
<li class="li">Discovered data is automatically mapped to telecom-aligned Configuration Item (CI) classes.</li>
<li class="li">Integrates directly with the Identification and Reconciliation Engine (IRE) to ensure accurate, non-duplicate CI records in the CMDB and Telecom Network Inventory (TNI).</li>
</ul></li>
<li class="li">CMDB Accuracy and Compliance<ul class="ul" id="telecom-discovery-using-telecommunication-discovery-pattern__ul_zzp_1z2_wfc">
<li class="li">Patterns trigger CMDB Compliance Certification Audits to detect mismatches or outdated records.</li>
<li class="li">Supports discrepancy identification and remediation, helping maintain data integrity.</li>
</ul></li>
<li class="li">Low-Code Pattern Customization: Extend or customize discovery patterns using low-code pattern designers to meet your specific network architecture and business needs.</li>
</ul>
</div>
</section>
<section class="section" id="telecom-discovery-using-telecommunication-discovery-pattern__section_sn4_55y_5fc"><h2 id="d4908e101" class="title sectiontitle">How it works</h2>
<p class="p">Telecommunications Discovery Patterns are executed through Horizontal Discovery using the Nebula Discovery Language (NDL). A pattern is a sequence of steps that:</p>
<ol class="ol" id="telecom-discovery-using-telecommunication-discovery-pattern__ol_tny_v5y_5fc">
<li class="li">Establishes a connection to a target device.</li>
<li class="li">Executes commands using SNMP, CLI, or both.</li>
<li class="li">Extracts CI attributes and relationships.</li>
<li class="li">Sends results to IRE for reconciliation and insertion into the CMDB and TNI.</li>
</ol>
<p class="p">The discovery logic follows the TNI data model, which restructures complex CI relationships (e.g., card-on-card scenarios) to align with telecom modeling best practices. For example, If a child card is discovered inside a parent
card, Telecom Discovery synthesizes a subslot to insert the child, avoiding an invalid card-on-card configuration.</p>
</section>
<section class="section" id="telecom-discovery-using-telecommunication-discovery-pattern__section_r4g_45j_zdc"><h2 id="d4908e128" class="title sectiontitle">Architecture using Horizontal Discovery and Telecommunications Discovery Patterns</h2>
<p class="p">The following infographic is an example of the implementation for standalone SNMP or/and CLI xNFs.<img src="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/../images/telecom-discovery-reconciliation-pattern.png?_LANG=enus" class="image" id="telecom-discovery-using-telecommunication-discovery-pattern__image_xnj_w43_b2c" alt="discovery and telecommunications discovery pattern."/></p>
</section>
<section class="section" id="telecom-discovery-using-telecommunication-discovery-pattern__section_rtw_hvj_zdc"><h2 id="d4908e143" class="title sectiontitle">Horizontal Discovery Application</h2>
<p class="p">The Horizontal Discovery application in ServiceNow is a versatile and highly scalable discovery engine designed to operate effectively across network, IT, and cloud environments, collecting data across multiple layers to provide a
holistic view of the infrastructure.</p>
<p class="p">For more information, see <a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/concept//csh" href="https://servicenow-be-prod.servicenow.com/csh?topicname=disco-process-flow-patterns&version=zurich&pubname=zurich-it-operations-management" class="xref">Horizontal discovery process flow with patterns</a>.</p>
</section>
<section class="section" id="telecom-discovery-using-telecommunication-discovery-pattern__section_jxg_qvj_zdc"><h2 id="d4908e159" class="title sectiontitle">Supported discovery patterns</h2>
<p class="p">A pattern is a sequence of commands designed to detect attributes of a configuration item (CI) and its outbound connections. Telecom Discovery provides a set of preconfigured Patterns that cover a wide range of network elements. <span class="ph">ServiceNow</span> offers several out-of-the-box (OOB) TSOM patterns, including:</p>
<ul class="ul" id="telecom-discovery-using-telecommunication-discovery-pattern__ul_jcv_1xy_5fc">
<li class="li">Telecom Router Pattern – Generic SNMP-based router discovery.</li>
<li class="li">Telecom Cisco 7613 Router Pattern – For Cisco 7613 routers using SNMP.</li>
<li class="li">Telecom Juniper MX SSH Router Pattern – SNMP + CLI discovery of Juniper MX routers.</li>
<li class="li">Telecom Cisco Switch Pattern – SNMP-based Cisco switch discovery.</li>
<li class="li">Telecom Switch Pattern – SNMP-based generic switch discovery.</li>
</ul>
</section>
<section class="section" id="telecom-discovery-using-telecommunication-discovery-pattern__section_apd_kyy_5fc"><h2 id="d4908e189" class="title sectiontitle">TNI entity creation</h2>
<p class="p">If your instance has the <strong class="ph b">Telecom Network Inventory (TNI)</strong> plugin installed:</p>
<ul class="ul" id="telecom-discovery-using-telecommunication-discovery-pattern__ul_y2w_lyy_5fc">
<li class="li">Every discovered CI automatically results in a TNI entity record.</li>
<li class="li">The IRE payload includes mapping to both <code class="ph codeph">cmdb_ci</code> and <code class="ph codeph">tni_entity</code> tables.</li>
</ul>
<p class="p">This ensures seamless alignment between operational and inventory systems, which is essential for order fulfillment, assurance, and network planning.</p>
</section>
<section class="section" id="telecom-discovery-using-telecommunication-discovery-pattern__section_o4r_cwj_zdc"><h2 id="d4908e219" class="title sectiontitle"><span class="ph">MID Server</span></h2>
<p class="p"><span class="ph">MID Server</span> is a Java application that runs as a Windows service or UNIX daemon on a server within your local network. The <span class="ph">ServiceNow®</span>
<span class="ph">MID Server</span> facilitates communication and data transfer between a ServiceNow instance and external applications, data sources, and services.</p>
<p class="p">For more information, see <a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/concept//csh" href="https://servicenow-be-prod.servicenow.com/csh?topicname=mid-server-landing&version=zurich&pubname=zurich-servicenow-platform" class="xref">MID Server</a>.</p>
</section>
<section class="section" id="telecom-discovery-using-telecommunication-discovery-pattern__section_mx4_swj_zdc"><h2 id="d4908e245" class="title sectiontitle">Identification & Reconciliation Engine (IRE)</h2>
<p class="p">IRE offers a centralized framework for identifying and reconciling data from multiple sources. It verifies the integrity of the CMDB and some non-CMDB tables when various data sources are used to create or update CI records.</p>
</section>
</div>
<nav role="navigation"></nav><nav role="navigation" class="tasksNavigation"></nav><nav role="navigation" class="related-links"><div class="col-md-4"><dt>Related tasks</dt><dd><ul><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/task/install-horizontal-telecommunication-discoverypatterns.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/install-horizontal-telecommunication-discoverypatterns.html" class="link" title="Install Horizontal Discovery patterns understanding the dependencies and requirements.">Install Horizontal Discovery and set up Discovery Patterns</a></li></ul></dd></div></nav>
</article></main></body></article> | {
"attachments": {
"all_attachments": null,
"topic_attachments": []
},
"available_languages": [
"enus"
],
"breadcrumbs": [
{
"title": "Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html"
},
{
"title": "Exploring Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/exploring-tsom.html"
},
{
"title": "Telecom Visibility",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/tsom-visibility.html"
},
{
"title": "Telecom Discovery",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/exploring-telecom-discovery.html"
}
],
"breadcrumbs_html": "<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops\">Zurich Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html\">Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/exploring-tsom.html\">Exploring Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/tsom-visibility.html\">Telecom Visibility</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/exploring-telecom-discovery.html\">Telecom Discovery</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<span class=\"active\">Direct Discovery using Discovery Patterns</span>",
"bundle_id": "zurich-telecom-service-ops",
"bundle_key": 2733,
"bundle_landing_page": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html",
"bundle_subtitle": null,
"bundle_title": "Zurich Telecommunications Service Operations Management",
"canonical_link": null,
"dates": {
"Added on": "2025-08-02T00:48:08.794016Z",
"Created on": "2024-12-06T00:00:00Z",
"Initial upload": "2025-07-30T22:24:33.519043Z",
"Updated on": "2025-07-31T00:00:00Z"
},
"dislike_url": "https://servicenow-be-prod.servicenow.com/dislike/55686943",
"dislikes": 0,
"es_archived_content": false,
"is_in_fav": false,
"is_liked": null,
"is_watched": false,
"keywords": [
" zurich zurich"
],
"labels": [
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "zurich",
"navtitle": "Zurich",
"outputclasses": [],
"subjectHeadId": "versions",
"subjectheadNavtitle": "Versions",
"visibility": "show-facet"
},
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "tsom",
"navtitle": "Telecommunications Service Operations Management",
"outputclasses": [],
"subjectHeadId": "products",
"subjectheadNavtitle": "Products",
"visibility": "show-facet"
}
],
"labels_text": "Versions > Zurich; Products > CRM and Industry Products > Telecommunications Media and Technology Assurance > Telecommunications Service Operations Management",
"like_url": "https://servicenow-be-prod.servicenow.com/like/55686943",
"likes": 0,
"metadata": {
"AI Search": null,
"AI Search Assist": null,
"Application Insights": null,
"Capabilities": null,
"Code Signing": null,
"Contextual Search": null,
"DC.contributor": null,
"DC.coverage": null,
"DC.creator": "ServiceNow",
"DC.date.created": "2024-12-06T10:53:06+05:30",
"DC.date.modified": "2025-07-31",
"DC.format": "HTML5",
"DC.identifier": "telecom-discovery-using-telecommunication-discovery-pattern",
"DC.language": null,
"DC.relation": "../task/install-horizontal-telecommunication-discoverypatterns.html",
"DC.rights.owner": "(C) Copyright 2025",
"DC.subject": null,
"DC.type": "concept",
"Data Discovery": null,
"Data Policy": null,
"Data Privacy": null,
"Discovery": null,
"External Content for AI Search": null,
"Field Administration": null,
"Field Normalization": null,
"Key Management Framework": null,
"Localization Framework": null,
"Now Platform": null,
"PlatSec": null,
"Platform": null,
"Platform Administration": null,
"Platform Performance": null,
"Platform Privacy": null,
"Proactive Triggers": null,
"Process Optimization": null,
"RN doc editing record number": null,
"Search Administration": null,
"Secrets Management": null,
"ServiceNow AI Platform": null,
"State Model": null,
"Subscription Management": null,
"Task Communications Management": null,
"Timeline Visualizations": null,
"User Administration": null,
"User Experience Analytics": null,
"Zing": null,
"ai-now-assist": null,
"app-name": null,
"app_route": null,
"azureapimanagemen": null,
"change-completed": null,
"change-item": null,
"change-request-id": null,
"change-request-reference": null,
"com.glide.embedded_help.category": null,
"component": null,
"copyright": "(C) Copyright 2025",
"crossroads": null,
"data": null,
"description": "The Telecommunications Discovery Patterns plugin (also known as TSOM Patterns) extends ServiceNow AI Platform Telecom Discovery to support direct discovery of standalone network elements—such as routers and switches—without relying on traditional network management systems. These patterns enable Communication Service Providers",
"dominant_bundle": null,
"erp-canvas-video": null,
"fsm-mobile": null,
"fsm-route": null,
"fsm-sched-opt": null,
"fsm-wrk-order": null,
"genai-round-7": null,
"generator": "DITA-OT",
"glossPartOfSpeech": null,
"glossStatus": null,
"guided setup": null,
"guided tours": null,
"keywords": null,
"min-toc": null,
"mini": null,
"mini-to truec": null,
"mini-toc": "yes",
"mini_toc": null,
"minitoc": null,
"modification": null,
"now-assist-app-gen-video": null,
"order": null,
"page-type": null,
"page-type ": null,
"prodname": null,
"product": null,
"product_name": null,
"release": null,
"resourceID": null,
"roles": null,
"route_page": null,
"route_params_listId": null,
"route_params_table": null,
"route_params_type": null,
"route_type": null,
"setconfigurationproperties": null,
"topic": null,
"translation-type": "source",
"version": null,
"workflow": "Customer and Industry",
"workplace-srvc-delvry-ditamap": null
},
"page_id": "product/tmt-telecom-service-operations-mgt/concept/telecom-discovery-using-telecommunication-discovery-pattern.html",
"page_key": 55686943,
"preprocessed_PDF": "https://downloads.docs.servicenow.com/pdf/enus/servicenow-zurich-telecom-service-ops-enus.pdf",
"rating": null,
"read_time_data": {
"char_count": 5064,
"img_count": 1,
"read_time": 3,
"video_links": [
""
],
"word_count": 699
},
"related_links": [
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "Install Horizontal Discovery patterns understanding the dependencies and requirements.",
"title": "Install Horizontal Discovery and set up Discovery Patterns",
"topic": "/product/tmt-telecom-service-operations-mgt/task/install-horizontal-telecommunication-discoverypatterns.html",
"type": "task",
"url": null
}
],
"search_title": null,
"title": "Direct Discovery using Discovery Patterns",
"topic_cluster": {
"clustered_by": {
"enabled": true,
"primary_key": "versions",
"primary_sort": "top-down",
"type": "subjecthead"
},
"clustered_labels": [
"versions"
],
"clustered_topics": [
{
"bundle_id": "yokohama-telecom-service-ops",
"clustering_title": "Yokohama",
"es_archived_content": false,
"page_id": "product/tmt-telecom-service-operations-mgt/concept/telecom-discovery-using-telecommunication-discovery-pattern.html"
}
],
"clustering_title": "Zurich"
},
"topic_html": "<article class=\"hascomments\" data-page=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/telecom-discovery-using-telecommunication-discovery-pattern.html\" id=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/telecom-discovery-using-telecommunication-discovery-pattern.html\"><body id=\"telecom-discovery-using-telecommunication-discovery-pattern\"><main role=\"main\"><article role=\"article\" class=\"dita\" id=\"telecom-discovery-using-telecommunication-discovery-pattern\" aria-labelledby=\"title_telecom-discovery-using-telecommunication-discovery-pattern\">\n <h1 class=\"title topictitle1\" id=\"title_telecom-discovery-using-telecommunication-discovery-pattern\">Direct Discovery using Discovery Patterns</h1>\n \n \n <div class=\"body conbody\"><p class=\"shortdesc\">The Telecommunications Discovery Patterns plugin (also known as TSOM Patterns) extends <span class=\"ph\">ServiceNow AI Platform</span> Telecom Discovery to support direct discovery of standalone network elements—such as routers and switches—without relying on traditional network management systems. These patterns enable Communication Service\n Providers (CSPs) to identify and map multivendor xNFs using protocols like SNMP and CLI, with support for NETCONF.</p>\n <p class=\"p\">Telecommunications Discovery Patterns provide a powerful, pattern-based approach to discover and manage telecom network resources directly from network elements. These patterns are especially valuable for discovering standalone xNFs\n (such as routers and switches) that are not managed through traditional EMS/NMS systems.</p>\n <div class=\"p\">This capability enhances visibility across telecom infrastructures and ensures that both vendor-neutral and vendor-specific device data is captured and reflected in the CMDB and Telecom Network Inventory (TNI), following the TNI data\n model.<div class=\"note note note_note\"><span class=\"note__title\">Note:</span> Telecommunications Discovery Patterns are part of the TSOM Visibility subscription and are available as a customer-visible plugin from the ServiceNow Store.</div></div>\n <section class=\"section\" id=\"telecom-discovery-using-telecommunication-discovery-pattern__section_jpv_n5y_5fc\"><h2 id=\"d4908e53\" class=\"title sectiontitle\">Key capabilities</h2>\n \n <div class=\"p\">\n <ul class=\"ul\" id=\"telecom-discovery-using-telecommunication-discovery-pattern__ul_xhc_q5y_5fc\">\n <li class=\"li\">Direct Network Element Discovery<ul class=\"ul\" id=\"telecom-discovery-using-telecommunication-discovery-pattern__ul_xzp_1z2_wfc\">\n <li class=\"li\">Use SNMP, CLI, and NETCONF to communicate directly with physical network elements.</li>\n <li class=\"li\">Discover physical network inventory such as interface cards, slots, ports, and devices without relying on EMS/NMS mediation.</li>\n </ul></li>\n <li class=\"li\">Automated CI Mapping and CMDB Integration<ul class=\"ul\" id=\"telecom-discovery-using-telecommunication-discovery-pattern__ul_yzp_1z2_wfc\">\n <li class=\"li\">Discovered data is automatically mapped to telecom-aligned Configuration Item (CI) classes.</li>\n <li class=\"li\">Integrates directly with the Identification and Reconciliation Engine (IRE) to ensure accurate, non-duplicate CI records in the CMDB and Telecom Network Inventory (TNI).</li>\n </ul></li>\n <li class=\"li\">CMDB Accuracy and Compliance<ul class=\"ul\" id=\"telecom-discovery-using-telecommunication-discovery-pattern__ul_zzp_1z2_wfc\">\n <li class=\"li\">Patterns trigger CMDB Compliance Certification Audits to detect mismatches or outdated records.</li>\n <li class=\"li\">Supports discrepancy identification and remediation, helping maintain data integrity.</li>\n </ul></li>\n <li class=\"li\">Low-Code Pattern Customization: Extend or customize discovery patterns using low-code pattern designers to meet your specific network architecture and business needs.</li>\n </ul>\n </div>\n </section>\n <section class=\"section\" id=\"telecom-discovery-using-telecommunication-discovery-pattern__section_sn4_55y_5fc\"><h2 id=\"d4908e101\" class=\"title sectiontitle\">How it works</h2>\n \n <p class=\"p\">Telecommunications Discovery Patterns are executed through Horizontal Discovery using the Nebula Discovery Language (NDL). A pattern is a sequence of steps that:</p>\n <ol class=\"ol\" id=\"telecom-discovery-using-telecommunication-discovery-pattern__ol_tny_v5y_5fc\">\n <li class=\"li\">Establishes a connection to a target device.</li>\n <li class=\"li\">Executes commands using SNMP, CLI, or both.</li>\n <li class=\"li\">Extracts CI attributes and relationships.</li>\n <li class=\"li\">Sends results to IRE for reconciliation and insertion into the CMDB and TNI.</li>\n </ol>\n <p class=\"p\">The discovery logic follows the TNI data model, which restructures complex CI relationships (e.g., card-on-card scenarios) to align with telecom modeling best practices. For example, If a child card is discovered inside a parent\n card, Telecom Discovery synthesizes a subslot to insert the child, avoiding an invalid card-on-card configuration.</p>\n </section>\n <section class=\"section\" id=\"telecom-discovery-using-telecommunication-discovery-pattern__section_r4g_45j_zdc\"><h2 id=\"d4908e128\" class=\"title sectiontitle\">Architecture using Horizontal Discovery and Telecommunications Discovery Patterns</h2>\n \n <p class=\"p\">The following infographic is an example of the implementation for standalone SNMP or/and CLI xNFs.<img src=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/../images/telecom-discovery-reconciliation-pattern.png?_LANG=enus\" class=\"image\" id=\"telecom-discovery-using-telecommunication-discovery-pattern__image_xnj_w43_b2c\" alt=\"discovery and telecommunications discovery pattern.\"/></p>\n </section>\n <section class=\"section\" id=\"telecom-discovery-using-telecommunication-discovery-pattern__section_rtw_hvj_zdc\"><h2 id=\"d4908e143\" class=\"title sectiontitle\">Horizontal Discovery Application</h2>\n \n <p class=\"p\">The Horizontal Discovery application in ServiceNow is a versatile and highly scalable discovery engine designed to operate effectively across network, IT, and cloud environments, collecting data across multiple layers to provide a\n holistic view of the infrastructure.</p>\n <p class=\"p\">For more information, see <a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept//csh\" href=\"https://servicenow-be-prod.servicenow.com/csh?topicname=disco-process-flow-patterns&version=zurich&pubname=zurich-it-operations-management\" class=\"xref\">Horizontal discovery process flow with patterns</a>.</p>\n </section>\n <section class=\"section\" id=\"telecom-discovery-using-telecommunication-discovery-pattern__section_jxg_qvj_zdc\"><h2 id=\"d4908e159\" class=\"title sectiontitle\">Supported discovery patterns</h2>\n \n <p class=\"p\">A pattern is a sequence of commands designed to detect attributes of a configuration item (CI) and its outbound connections. Telecom Discovery provides a set of preconfigured Patterns that cover a wide range of network elements. <span class=\"ph\">ServiceNow</span> offers several out-of-the-box (OOB) TSOM patterns, including:</p>\n <ul class=\"ul\" id=\"telecom-discovery-using-telecommunication-discovery-pattern__ul_jcv_1xy_5fc\">\n <li class=\"li\">Telecom Router Pattern – Generic SNMP-based router discovery.</li>\n <li class=\"li\">Telecom Cisco 7613 Router Pattern – For Cisco 7613 routers using SNMP.</li>\n <li class=\"li\">Telecom Juniper MX SSH Router Pattern – SNMP + CLI discovery of Juniper MX routers.</li>\n <li class=\"li\">Telecom Cisco Switch Pattern – SNMP-based Cisco switch discovery.</li>\n <li class=\"li\">Telecom Switch Pattern – SNMP-based generic switch discovery.</li>\n </ul>\n </section>\n <section class=\"section\" id=\"telecom-discovery-using-telecommunication-discovery-pattern__section_apd_kyy_5fc\"><h2 id=\"d4908e189\" class=\"title sectiontitle\">TNI entity creation</h2>\n \n <p class=\"p\">If your instance has the <strong class=\"ph b\">Telecom Network Inventory (TNI)</strong> plugin installed:</p>\n <ul class=\"ul\" id=\"telecom-discovery-using-telecommunication-discovery-pattern__ul_y2w_lyy_5fc\">\n <li class=\"li\">Every discovered CI automatically results in a TNI entity record.</li>\n <li class=\"li\">The IRE payload includes mapping to both <code class=\"ph codeph\">cmdb_ci</code> and <code class=\"ph codeph\">tni_entity</code> tables.</li>\n </ul>\n <p class=\"p\">This ensures seamless alignment between operational and inventory systems, which is essential for order fulfillment, assurance, and network planning.</p>\n </section>\n <section class=\"section\" id=\"telecom-discovery-using-telecommunication-discovery-pattern__section_o4r_cwj_zdc\"><h2 id=\"d4908e219\" class=\"title sectiontitle\"><span class=\"ph\">MID Server</span></h2>\n \n <p class=\"p\"><span class=\"ph\">MID Server</span> is a Java application that runs as a Windows service or UNIX daemon on a server within your local network. The <span class=\"ph\">ServiceNow®</span>\n <span class=\"ph\">MID Server</span> facilitates communication and data transfer between a ServiceNow instance and external applications, data sources, and services.</p>\n <p class=\"p\">For more information, see <a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept//csh\" href=\"https://servicenow-be-prod.servicenow.com/csh?topicname=mid-server-landing&version=zurich&pubname=zurich-servicenow-platform\" class=\"xref\">MID Server</a>.</p>\n </section>\n <section class=\"section\" id=\"telecom-discovery-using-telecommunication-discovery-pattern__section_mx4_swj_zdc\"><h2 id=\"d4908e245\" class=\"title sectiontitle\">Identification & Reconciliation Engine (IRE)</h2>\n \n <p class=\"p\">IRE offers a centralized framework for identifying and reconciling data from multiple sources. It verifies the integrity of the CMDB and some non-CMDB tables when various data sources are used to create or update CI records.</p>\n </section>\n </div>\n <nav role=\"navigation\"></nav><nav role=\"navigation\" class=\"tasksNavigation\"></nav><nav role=\"navigation\" class=\"related-links\"><div class=\"col-md-4\"><dt>Related tasks</dt><dd><ul><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/task/install-horizontal-telecommunication-discoverypatterns.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/install-horizontal-telecommunication-discoverypatterns.html\" class=\"link\" title=\"Install Horizontal Discovery patterns understanding the dependencies and requirements.\">Install Horizontal Discovery and set up Discovery Patterns</a></li></ul></dd></div></nav>\n</article></main></body></article>",
"topic_language": "enus",
"views": 0,
"your_rating": null
} | # Direct Discovery using Discovery Patterns
The Telecommunications Discovery Patterns plugin (also known as TSOM Patterns) extends ServiceNow AI Platform Telecom Discovery to support direct discovery of standalone network elements—such as routers and switches—without relying on traditional network management systems. These patterns enable Communication Service
Providers (CSPs) to identify and map multivendor xNFs using protocols like SNMP and CLI, with support for NETCONF.
Telecommunications Discovery Patterns provide a powerful, pattern-based approach to discover and manage telecom network resources directly from network elements. These patterns are especially valuable for discovering standalone xNFs
(such as routers and switches) that are not managed through traditional EMS/NMS systems.
This capability enhances visibility across telecom infrastructures and ensures that both vendor-neutral and vendor-specific device data is captured and reflected in the CMDB and Telecom Network Inventory (TNI), following the TNI data
model.Note: Telecommunications Discovery Patterns are part of the TSOM Visibility subscription and are available as a customer-visible plugin from the ServiceNow Store.
## Key capabilities
* Direct Network Element Discovery
+ Use SNMP, CLI, and NETCONF to communicate directly with physical network elements.
+ Discover physical network inventory such as interface cards, slots, ports, and devices without relying on EMS/NMS mediation.
* Automated CI Mapping and CMDB Integration
+ Discovered data is automatically mapped to telecom-aligned Configuration Item (CI) classes.
+ Integrates directly with the Identification and Reconciliation Engine (IRE) to ensure accurate, non-duplicate CI records in the CMDB and Telecom Network Inventory (TNI).
* CMDB Accuracy and Compliance
+ Patterns trigger CMDB Compliance Certification Audits to detect mismatches or outdated records.
+ Supports discrepancy identification and remediation, helping maintain data integrity.
* Low-Code Pattern Customization: Extend or customize discovery patterns using low-code pattern designers to meet your specific network architecture and business needs.
## How it works
Telecommunications Discovery Patterns are executed through Horizontal Discovery using the Nebula Discovery Language (NDL). A pattern is a sequence of steps that:
1. Establishes a connection to a target device.
2. Executes commands using SNMP, CLI, or both.
3. Extracts CI attributes and relationships.
4. Sends results to IRE for reconciliation and insertion into the CMDB and TNI.
The discovery logic follows the TNI data model, which restructures complex CI relationships (e.g., card-on-card scenarios) to align with telecom modeling best practices. For example, If a child card is discovered inside a parent
card, Telecom Discovery synthesizes a subslot to insert the child, avoiding an invalid card-on-card configuration.
## Architecture using Horizontal Discovery and Telecommunications Discovery Patterns
The following infographic is an example of the implementation for standalone SNMP or/and CLI xNFs.
## Horizontal Discovery Application
The Horizontal Discovery application in ServiceNow is a versatile and highly scalable discovery engine designed to operate effectively across network, IT, and cloud environments, collecting data across multiple layers to provide a
holistic view of the infrastructure.
For more information, see Horizontal discovery process flow with patterns.
## Supported discovery patterns
A pattern is a sequence of commands designed to detect attributes of a configuration item (CI) and its outbound connections. Telecom Discovery provides a set of preconfigured Patterns that cover a wide range of network elements. ServiceNow offers several out-of-the-box (OOB) TSOM patterns, including:
* Telecom Router Pattern – Generic SNMP-based router discovery.
* Telecom Cisco 7613 Router Pattern – For Cisco 7613 routers using SNMP.
* Telecom Juniper MX SSH Router Pattern – SNMP + CLI discovery of Juniper MX routers.
* Telecom Cisco Switch Pattern – SNMP-based Cisco switch discovery.
* Telecom Switch Pattern – SNMP-based generic switch discovery.
## TNI entity creation
If your instance has the **Telecom Network Inventory (TNI)** plugin installed:
* Every discovered CI automatically results in a TNI entity record.
* The IRE payload includes mapping to both `cmdb_ci` and `tni_entity` tables.
This ensures seamless alignment between operational and inventory systems, which is essential for order fulfillment, assurance, and network planning.
## MID Server
MID Server is a Java application that runs as a Windows service or UNIX daemon on a server within your local network. The ServiceNow®
MID Server facilitates communication and data transfer between a ServiceNow instance and external applications, data sources, and services.
For more information, see MID Server.
## Identification & Reconciliation Engine (IRE)
IRE offers a centralized framework for identifying and reconciling data from multiple sources. It verifies the integrity of the CMDB and some non-CMDB tables when various data sources are used to create or update CI records.
| ---
title: Direct Discovery using Discovery Patterns
description: "The Telecommunications Discovery Patterns plugin (also known as TSOM\
\ Patterns) extends ServiceNow AI Platform Telecom Discovery to support direct discovery\
\ of standalone network elements\u2014such as routers and switches\u2014without\
\ relying on traditional network management systems. These patterns enable Communication\
\ Service Providers"
keywords: []
breadcrumbs:
- Telecommunications Service Operations Management
- Exploring Telecommunications Service Operations Management
- Telecom Visibility
- Telecom Discovery
---
# Direct Discovery using Discovery Patterns
The Telecommunications Discovery Patterns plugin (also known as TSOM Patterns) extends ServiceNow AI Platform Telecom Discovery to support direct discovery of standalone network elements—such as routers and switches—without relying on traditional network management systems. These patterns enable Communication Service
Providers (CSPs) to identify and map multivendor xNFs using protocols like SNMP and CLI, with support for NETCONF.
Telecommunications Discovery Patterns provide a powerful, pattern-based approach to discover and manage telecom network resources directly from network elements. These patterns are especially valuable for discovering standalone xNFs
(such as routers and switches) that are not managed through traditional EMS/NMS systems.
This capability enhances visibility across telecom infrastructures and ensures that both vendor-neutral and vendor-specific device data is captured and reflected in the CMDB and Telecom Network Inventory (TNI), following the TNI data
model.Note: Telecommunications Discovery Patterns are part of the TSOM Visibility subscription and are available as a customer-visible plugin from the ServiceNow Store.
## Key capabilities
* Direct Network Element Discovery
+ Use SNMP, CLI, and NETCONF to communicate directly with physical network elements.
+ Discover physical network inventory such as interface cards, slots, ports, and devices without relying on EMS/NMS mediation.
* Automated CI Mapping and CMDB Integration
+ Discovered data is automatically mapped to telecom-aligned Configuration Item (CI) classes.
+ Integrates directly with the Identification and Reconciliation Engine (IRE) to ensure accurate, non-duplicate CI records in the CMDB and Telecom Network Inventory (TNI).
* CMDB Accuracy and Compliance
+ Patterns trigger CMDB Compliance Certification Audits to detect mismatches or outdated records.
+ Supports discrepancy identification and remediation, helping maintain data integrity.
* Low-Code Pattern Customization: Extend or customize discovery patterns using low-code pattern designers to meet your specific network architecture and business needs.
## How it works
Telecommunications Discovery Patterns are executed through Horizontal Discovery using the Nebula Discovery Language (NDL). A pattern is a sequence of steps that:
1. Establishes a connection to a target device.
2. Executes commands using SNMP, CLI, or both.
3. Extracts CI attributes and relationships.
4. Sends results to IRE for reconciliation and insertion into the CMDB and TNI.
The discovery logic follows the TNI data model, which restructures complex CI relationships (e.g., card-on-card scenarios) to align with telecom modeling best practices. For example, If a child card is discovered inside a parent
card, Telecom Discovery synthesizes a subslot to insert the child, avoiding an invalid card-on-card configuration.
## Architecture using Horizontal Discovery and Telecommunications Discovery Patterns
The following infographic is an example of the implementation for standalone SNMP or/and CLI xNFs.
## Horizontal Discovery Application
The Horizontal Discovery application in ServiceNow is a versatile and highly scalable discovery engine designed to operate effectively across network, IT, and cloud environments, collecting data across multiple layers to provide a
holistic view of the infrastructure.
For more information, see Horizontal discovery process flow with patterns.
## Supported discovery patterns
A pattern is a sequence of commands designed to detect attributes of a configuration item (CI) and its outbound connections. Telecom Discovery provides a set of preconfigured Patterns that cover a wide range of network elements. ServiceNow offers several out-of-the-box (OOB) TSOM patterns, including:
* Telecom Router Pattern – Generic SNMP-based router discovery.
* Telecom Cisco 7613 Router Pattern – For Cisco 7613 routers using SNMP.
* Telecom Juniper MX SSH Router Pattern – SNMP + CLI discovery of Juniper MX routers.
* Telecom Cisco Switch Pattern – SNMP-based Cisco switch discovery.
* Telecom Switch Pattern – SNMP-based generic switch discovery.
## TNI entity creation
If your instance has the **Telecom Network Inventory (TNI)** plugin installed:
* Every discovered CI automatically results in a TNI entity record.
* The IRE payload includes mapping to both `cmdb_ci` and `tni_entity` tables.
This ensures seamless alignment between operational and inventory systems, which is essential for order fulfillment, assurance, and network planning.
## MID Server
MID Server is a Java application that runs as a Windows service or UNIX daemon on a server within your local network. The ServiceNow®
MID Server facilitates communication and data transfer between a ServiceNow instance and external applications, data sources, and services.
For more information, see MID Server.
## Identification & Reconciliation Engine (IRE)
IRE offers a centralized framework for identifying and reconciling data from multiple sources. It verifies the integrity of the CMDB and some non-CMDB tables when various data sources are used to create or update CI records.
|
https://www.servicenow.com/docs/en-US/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/telecommunications-api-notification.html | https://servicenow-be-prod.servicenow.com/api/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/telecommunications-api-notification.html | 2025-08-02 | daily | 0.5 | 268.xml | en-US | zurich-telecom-service-ops | product/tmt-telecom-service-operations-mgt/concept/telecommunications-api-notification.html | zurich | External event management via Telecommunications API notifications | Use the Telecommunications API notification to receive the external events that occurring in the customer network system so that you can promptly respond to them in the ServiceNow. | [] | [
"Telecommunications Service Operations Management",
"Exploring Telecommunications Service Operations Management"
] | <article class="hascomments" data-page="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/telecommunications-api-notification.html" id="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/telecommunications-api-notification.html"><body id="telecommunications-api-notification"><main role="main"><article role="article" class="dita" id="telecommunications-api-notification" aria-labelledby="title_telecommunications-api-notification">
<h1 class="title topictitle1" id="title_telecommunications-api-notification">External event management via Telecommunications API notifications</h1>
<div class="body conbody"><p class="shortdesc">Use the Telecommunications API notification to receive the external events that occurring in the customer network system so that you can promptly respond to them in the <span class="ph">ServiceNow</span>.</p>
<section class="section" id="telecommunications-api-notification__section_wyw_yy1_dzb"><h2 id="d4069e42" class="title sectiontitle">Introduction to Telecommunications API notification</h2>
<p class="p">Telecommunications API notification is a feature available in the Telecommunications Alarm Management Open API application. The Telecommunications API notification enables <span class="ph">ServiceNow</span> to receive the incoming notifications that occurring in the external network system and responds to them in a timely manner. It enables the broadcasting of events to the external systems through
platform capabilities by eliminating the need for point to point connections.</p>
<p class="p">Telecommunications API notification receives incoming notifications from the external systems that are subscribed on your network. When the notifications are received from the external system, you can create the events for the
responses by using the <span class="ph">Event Management</span> application. Based on the collected information, the <span class="ph">Event Management</span> provides dashboards showing a consolidated view of all service-impact events.</p>
</section>
<section class="section" id="telecommunications-api-notification__section_qv3_1z1_dzb"><h2 id="d4069e63" class="title sectiontitle">Telecommunications API notification data model</h2>
<p class="p">The following diagram shows the components in the data model for the Telecommunications API notification.</p>
<figure class="fig fignone" id="telecommunications-api-notification__fig_y1g_yh3_dzb"><figcaption><span class="fig--title-label">Figure 1. </span>API notification data model</figcaption>
<img src="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/../images/telcomm-api-notification-data-model.png?_LANG=enus" class="image" id="telecommunications-api-notification__image_sjr_x33_dzb" alt="Infographic showing the components in the Telecommunications API notification data model. For the description, see the following texts."/>
</figure>
<div class="p">The Telecommunications API notification enables <span class="ph">ServiceNow</span> to receive incoming notifications through the event-driven architectures such as the Publisher/Subscriber (Pub/Sub) subscription model, Hermes, and Kafka Stream Connect. While cloud customers have
the flexibility to select between both architectures, on-premise customers are limited to using their own Kafka or Pub/Sub subscription model.<ul class="ul" id="telecommunications-api-notification__ul_g3w_3b3_dzb">
<li class="li">To learn more about Stream connect for Apache Kafka Stream, see <a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/concept//csh" href="https://servicenow-be-prod.servicenow.com/csh?topicname=stream-connect-apache-kafka&version=zurich&pubname=zurich-integrate-applications" class="xref">Using Stream Connect for Apache Kafka</a>.</li>
<li class="li">To learn more about Hermes Messaging Service, see <a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/concept//csh" href="https://servicenow-be-prod.servicenow.com/csh?topicname=hermes-messaging-service&version=zurich&pubname=zurich-servicenow-platform" class="xref">Hermes Messaging Service</a>.</li>
</ul></div>
<p class="p">In the Pub/Sub model, incoming notifications are categorized into topics. You use <span class="ph">ServiceNow</span> to publish the incoming notifications to these topics, and subscribers (customers) have the flexibility to select the topics to which they want to subscribe. This process enables subscribers to
select only those messages that align with their interests. For example, if there are 10 topics for incoming messages from the external system, a customer can opt to subscribe to two of them based on their requirement. Consequently,
when notifications are received from the external system, events are generated specifically for the two topics to which the customer has subscribed.</p>
</section>
</div>
<nav role="navigation"></nav><nav role="navigation" class="tasksNavigation"></nav><nav role="navigation" class="related-links"><div class="col-md-4"><dt>Related concepts</dt><dd><ul><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/concept/configuring-telecommunications-api-notifications.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/configuring-telecommunications-api-notifications.html" class="link" title="Configure the Telecommunications API notification in the ServiceNow instance.">Configuring Telecommunications API notifications</a></li></ul></dd></div><div class="col-md-4"><dt>Related reference</dt><dd><ul><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/reference/alarm-management-user-roles.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/reference/alarm-management-user-roles.html" class="link" title="Administrators can assign user roles to grant access to the API notification database tables. The following standard roles for the Topic [sn_api_notif_mgmt_topic] and Topic Subscription [sn_api_notif_mgmt_subscription] tables are included in the ServiceNow system.">System components installed with Telecommunications API notifications</a></li></ul></dd></div></nav>
</article></main></body></article> | {
"attachments": {
"all_attachments": null,
"topic_attachments": []
},
"available_languages": [
"enus"
],
"breadcrumbs": [
{
"title": "Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html"
},
{
"title": "Exploring Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/exploring-tsom.html"
}
],
"breadcrumbs_html": "<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops\">Zurich Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html\">Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/exploring-tsom.html\">Exploring Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<span class=\"active\">External event management via Telecommunications API notifications</span>",
"bundle_id": "zurich-telecom-service-ops",
"bundle_key": 2733,
"bundle_landing_page": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html",
"bundle_subtitle": null,
"bundle_title": "Zurich Telecommunications Service Operations Management",
"canonical_link": null,
"dates": {
"Added on": "2025-08-02T00:48:08.794016Z",
"Created on": "2023-10-16T00:00:00Z",
"Initial upload": "2025-07-30T22:24:33.519043Z",
"Updated on": "2025-07-31T00:00:00Z"
},
"dislike_url": "https://servicenow-be-prod.servicenow.com/dislike/55686947",
"dislikes": 0,
"es_archived_content": false,
"is_in_fav": false,
"is_liked": null,
"is_watched": false,
"keywords": [
" zurich zurich"
],
"labels": [
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "zurich",
"navtitle": "Zurich",
"outputclasses": [],
"subjectHeadId": "versions",
"subjectheadNavtitle": "Versions",
"visibility": "show-facet"
},
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "tsom",
"navtitle": "Telecommunications Service Operations Management",
"outputclasses": [],
"subjectHeadId": "products",
"subjectheadNavtitle": "Products",
"visibility": "show-facet"
}
],
"labels_text": "Versions > Zurich; Products > CRM and Industry Products > Telecommunications Media and Technology Assurance > Telecommunications Service Operations Management",
"like_url": "https://servicenow-be-prod.servicenow.com/like/55686947",
"likes": 0,
"metadata": {
"AI Search": null,
"AI Search Assist": null,
"Application Insights": null,
"Capabilities": null,
"Code Signing": null,
"Contextual Search": null,
"DC.contributor": null,
"DC.coverage": null,
"DC.creator": "ServiceNow",
"DC.date.created": "2023-10-16T14:02:59+05:30",
"DC.date.modified": "2025-07-31",
"DC.format": "HTML5",
"DC.identifier": "telecommunications-api-notification",
"DC.language": null,
"DC.relation": "configuring-telecommunications-api-notifications.html",
"DC.rights.owner": "(C) Copyright 2025",
"DC.subject": null,
"DC.type": "concept",
"Data Discovery": null,
"Data Policy": null,
"Data Privacy": null,
"Discovery": null,
"External Content for AI Search": null,
"Field Administration": null,
"Field Normalization": null,
"Key Management Framework": null,
"Localization Framework": null,
"Now Platform": null,
"PlatSec": null,
"Platform": null,
"Platform Administration": null,
"Platform Performance": null,
"Platform Privacy": null,
"Proactive Triggers": null,
"Process Optimization": null,
"RN doc editing record number": null,
"Search Administration": null,
"Secrets Management": null,
"ServiceNow AI Platform": null,
"State Model": null,
"Subscription Management": null,
"Task Communications Management": null,
"Timeline Visualizations": null,
"User Administration": null,
"User Experience Analytics": null,
"Zing": null,
"ai-now-assist": null,
"app-name": null,
"app_route": null,
"azureapimanagemen": null,
"change-completed": null,
"change-item": null,
"change-request-id": null,
"change-request-reference": null,
"com.glide.embedded_help.category": null,
"component": null,
"copyright": "(C) Copyright 2025",
"crossroads": null,
"data": null,
"description": "Use the Telecommunications API notification to receive the external events that occurring in the customer network system so that you can promptly respond to them in the ServiceNow.",
"dominant_bundle": null,
"erp-canvas-video": null,
"fsm-mobile": null,
"fsm-route": null,
"fsm-sched-opt": null,
"fsm-wrk-order": null,
"genai-round-7": null,
"generator": "DITA-OT",
"glossPartOfSpeech": null,
"glossStatus": null,
"guided setup": null,
"guided tours": null,
"keywords": null,
"min-toc": null,
"mini": null,
"mini-to truec": null,
"mini-toc": "yes",
"mini_toc": null,
"minitoc": null,
"modification": null,
"now-assist-app-gen-video": null,
"order": null,
"page-type": null,
"page-type ": null,
"prodname": null,
"product": null,
"product_name": null,
"release": null,
"resourceID": null,
"roles": null,
"route_page": null,
"route_params_listId": null,
"route_params_table": null,
"route_params_type": null,
"route_type": null,
"setconfigurationproperties": null,
"topic": null,
"translation-type": "source",
"version": null,
"workflow": "Customer and Industry",
"workplace-srvc-delvry-ditamap": null
},
"page_id": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-api-notification.html",
"page_key": 55686947,
"preprocessed_PDF": "https://downloads.docs.servicenow.com/pdf/enus/servicenow-zurich-telecom-service-ops-enus.pdf",
"rating": null,
"read_time_data": {
"char_count": 2574,
"img_count": 1,
"read_time": 2,
"video_links": [
""
],
"word_count": 360
},
"related_links": [
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "Configure the Telecommunications API notification in the ServiceNow instance.",
"title": "Configuring Telecommunications API notifications",
"topic": "/product/tmt-telecom-service-operations-mgt/concept/configuring-telecommunications-api-notifications.html",
"type": "concept",
"url": null
},
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "Administrators can assign user roles to grant access to the API notification database tables. The following standard roles for the Topic [sn_api_notif_mgmt_topic] and Topic Subscription [sn_api_notif_mgmt_subscription] tables are included in the ServiceNow system.",
"title": "System components installed with Telecommunications API notifications",
"topic": "/product/tmt-telecom-service-operations-mgt/reference/alarm-management-user-roles.html",
"type": "reference",
"url": null
}
],
"search_title": null,
"title": "External event management via Telecommunications API notifications",
"topic_cluster": {
"clustered_by": {
"enabled": true,
"primary_key": "versions",
"primary_sort": "top-down",
"type": "subjecthead"
},
"clustered_labels": [
"versions"
],
"clustered_topics": [
{
"bundle_id": "yokohama-telecom-service-ops",
"clustering_title": "Yokohama",
"es_archived_content": false,
"page_id": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-api-notification.html"
},
{
"bundle_id": "xanadu-telecom-service-ops",
"clustering_title": "Xanadu",
"es_archived_content": false,
"page_id": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-api-notification.html"
},
{
"bundle_id": "washingtondc-telecom-service-ops",
"clustering_title": "Washington DC",
"es_archived_content": false,
"page_id": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-api-notification.html"
},
{
"bundle_id": "vancouver-telecom-service-ops",
"clustering_title": "Vancouver",
"es_archived_content": false,
"page_id": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-api-notification.html"
}
],
"clustering_title": "Zurich"
},
"topic_html": "<article class=\"hascomments\" data-page=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/telecommunications-api-notification.html\" id=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/telecommunications-api-notification.html\"><body id=\"telecommunications-api-notification\"><main role=\"main\"><article role=\"article\" class=\"dita\" id=\"telecommunications-api-notification\" aria-labelledby=\"title_telecommunications-api-notification\">\n <h1 class=\"title topictitle1\" id=\"title_telecommunications-api-notification\">External event management via Telecommunications API notifications</h1>\n \n \n <div class=\"body conbody\"><p class=\"shortdesc\">Use the Telecommunications API notification to receive the external events that occurring in the customer network system so that you can promptly respond to them in the <span class=\"ph\">ServiceNow</span>.</p>\n <section class=\"section\" id=\"telecommunications-api-notification__section_wyw_yy1_dzb\"><h2 id=\"d4069e42\" class=\"title sectiontitle\">Introduction to Telecommunications API notification</h2>\n \n <p class=\"p\">Telecommunications API notification is a feature available in the Telecommunications Alarm Management Open API application. The Telecommunications API notification enables <span class=\"ph\">ServiceNow</span> to receive the incoming notifications that occurring in the external network system and responds to them in a timely manner. It enables the broadcasting of events to the external systems through\n platform capabilities by eliminating the need for point to point connections.</p>\n <p class=\"p\">Telecommunications API notification receives incoming notifications from the external systems that are subscribed on your network. When the notifications are received from the external system, you can create the events for the\n responses by using the <span class=\"ph\">Event Management</span> application. Based on the collected information, the <span class=\"ph\">Event Management</span> provides dashboards showing a consolidated view of all service-impact events.</p>\n </section>\n <section class=\"section\" id=\"telecommunications-api-notification__section_qv3_1z1_dzb\"><h2 id=\"d4069e63\" class=\"title sectiontitle\">Telecommunications API notification data model</h2>\n \n <p class=\"p\">The following diagram shows the components in the data model for the Telecommunications API notification.</p>\n <figure class=\"fig fignone\" id=\"telecommunications-api-notification__fig_y1g_yh3_dzb\"><figcaption><span class=\"fig--title-label\">Figure 1. </span>API notification data model</figcaption>\n \n <img src=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/../images/telcomm-api-notification-data-model.png?_LANG=enus\" class=\"image\" id=\"telecommunications-api-notification__image_sjr_x33_dzb\" alt=\"Infographic showing the components in the Telecommunications API notification data model. For the description, see the following texts.\"/>\n </figure>\n \n <div class=\"p\">The Telecommunications API notification enables <span class=\"ph\">ServiceNow</span> to receive incoming notifications through the event-driven architectures such as the Publisher/Subscriber (Pub/Sub) subscription model, Hermes, and Kafka Stream Connect. While cloud customers have\n the flexibility to select between both architectures, on-premise customers are limited to using their own Kafka or Pub/Sub subscription model.<ul class=\"ul\" id=\"telecommunications-api-notification__ul_g3w_3b3_dzb\">\n <li class=\"li\">To learn more about Stream connect for Apache Kafka Stream, see <a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept//csh\" href=\"https://servicenow-be-prod.servicenow.com/csh?topicname=stream-connect-apache-kafka&version=zurich&pubname=zurich-integrate-applications\" class=\"xref\">Using Stream Connect for Apache Kafka</a>.</li>\n <li class=\"li\">To learn more about Hermes Messaging Service, see <a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept//csh\" href=\"https://servicenow-be-prod.servicenow.com/csh?topicname=hermes-messaging-service&version=zurich&pubname=zurich-servicenow-platform\" class=\"xref\">Hermes Messaging Service</a>.</li>\n </ul></div>\n <p class=\"p\">In the Pub/Sub model, incoming notifications are categorized into topics. You use <span class=\"ph\">ServiceNow</span> to publish the incoming notifications to these topics, and subscribers (customers) have the flexibility to select the topics to which they want to subscribe. This process enables subscribers to\n select only those messages that align with their interests. For example, if there are 10 topics for incoming messages from the external system, a customer can opt to subscribe to two of them based on their requirement. Consequently,\n when notifications are received from the external system, events are generated specifically for the two topics to which the customer has subscribed.</p>\n </section>\n </div>\n <nav role=\"navigation\"></nav><nav role=\"navigation\" class=\"tasksNavigation\"></nav><nav role=\"navigation\" class=\"related-links\"><div class=\"col-md-4\"><dt>Related concepts</dt><dd><ul><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept/configuring-telecommunications-api-notifications.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/configuring-telecommunications-api-notifications.html\" class=\"link\" title=\"Configure the Telecommunications API notification in the ServiceNow instance.\">Configuring Telecommunications API notifications</a></li></ul></dd></div><div class=\"col-md-4\"><dt>Related reference</dt><dd><ul><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/reference/alarm-management-user-roles.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/reference/alarm-management-user-roles.html\" class=\"link\" title=\"Administrators can assign user roles to grant access to the API notification database tables. The following standard roles for the Topic [sn_api_notif_mgmt_topic] and Topic Subscription [sn_api_notif_mgmt_subscription] tables are included in the ServiceNow system.\">System components installed with Telecommunications API notifications</a></li></ul></dd></div></nav>\n</article></main></body></article>",
"topic_language": "enus",
"views": 0,
"your_rating": null
} | # External event management via Telecommunications API notifications
Use the Telecommunications API notification to receive the external events that occurring in the customer network system so that you can promptly respond to them in the ServiceNow.
## Introduction to Telecommunications API notification
Telecommunications API notification is a feature available in the Telecommunications Alarm Management Open API application. The Telecommunications API notification enables ServiceNow to receive the incoming notifications that occurring in the external network system and responds to them in a timely manner. It enables the broadcasting of events to the external systems through
platform capabilities by eliminating the need for point to point connections.
Telecommunications API notification receives incoming notifications from the external systems that are subscribed on your network. When the notifications are received from the external system, you can create the events for the
responses by using the Event Management application. Based on the collected information, the Event Management provides dashboards showing a consolidated view of all service-impact events.
## Telecommunications API notification data model
The following diagram shows the components in the data model for the Telecommunications API notification.
Figure 1. API notification data model
The Telecommunications API notification enables ServiceNow to receive incoming notifications through the event-driven architectures such as the Publisher/Subscriber (Pub/Sub) subscription model, Hermes, and Kafka Stream Connect. While cloud customers have
the flexibility to select between both architectures, on-premise customers are limited to using their own Kafka or Pub/Sub subscription model.
* To learn more about Stream connect for Apache Kafka Stream, see Using Stream Connect for Apache Kafka.
* To learn more about Hermes Messaging Service, see Hermes Messaging Service.
In the Pub/Sub model, incoming notifications are categorized into topics. You use ServiceNow to publish the incoming notifications to these topics, and subscribers (customers) have the flexibility to select the topics to which they want to subscribe. This process enables subscribers to
select only those messages that align with their interests. For example, if there are 10 topics for incoming messages from the external system, a customer can opt to subscribe to two of them based on their requirement. Consequently,
when notifications are received from the external system, events are generated specifically for the two topics to which the customer has subscribed.
| ---
title: External event management via Telecommunications API notifications
description: Use the Telecommunications API notification to receive the external events
that occurring in the customer network system so that you can promptly respond to
them in the ServiceNow.
keywords: []
breadcrumbs:
- Telecommunications Service Operations Management
- Exploring Telecommunications Service Operations Management
---
# External event management via Telecommunications API notifications
Use the Telecommunications API notification to receive the external events that occurring in the customer network system so that you can promptly respond to them in the ServiceNow.
## Introduction to Telecommunications API notification
Telecommunications API notification is a feature available in the Telecommunications Alarm Management Open API application. The Telecommunications API notification enables ServiceNow to receive the incoming notifications that occurring in the external network system and responds to them in a timely manner. It enables the broadcasting of events to the external systems through
platform capabilities by eliminating the need for point to point connections.
Telecommunications API notification receives incoming notifications from the external systems that are subscribed on your network. When the notifications are received from the external system, you can create the events for the
responses by using the Event Management application. Based on the collected information, the Event Management provides dashboards showing a consolidated view of all service-impact events.
## Telecommunications API notification data model
The following diagram shows the components in the data model for the Telecommunications API notification.
Figure 1. API notification data model
The Telecommunications API notification enables ServiceNow to receive incoming notifications through the event-driven architectures such as the Publisher/Subscriber (Pub/Sub) subscription model, Hermes, and Kafka Stream Connect. While cloud customers have
the flexibility to select between both architectures, on-premise customers are limited to using their own Kafka or Pub/Sub subscription model.
* To learn more about Stream connect for Apache Kafka Stream, see Using Stream Connect for Apache Kafka.
* To learn more about Hermes Messaging Service, see Hermes Messaging Service.
In the Pub/Sub model, incoming notifications are categorized into topics. You use ServiceNow to publish the incoming notifications to these topics, and subscribers (customers) have the flexibility to select the topics to which they want to subscribe. This process enables subscribers to
select only those messages that align with their interests. For example, if there are 10 topics for incoming messages from the external system, a customer can opt to subscribe to two of them based on their requirement. Consequently,
when notifications are received from the external system, events are generated specifically for the two topics to which the customer has subscribed.
|
https://www.servicenow.com/docs/en-US/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/tsom-visibility-vs--itom-visibility.html | https://servicenow-be-prod.servicenow.com/api/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/tsom-visibility-vs--itom-visibility.html | 2025-08-02 | daily | 0.5 | 268.xml | en-US | zurich-telecom-service-ops | product/tmt-telecom-service-operations-mgt/concept/tsom-visibility-vs--itom-visibility.html | zurich | Telecom Visibility vs. ITOM Visibility | As telecom networks evolve and become more hybrid and complex, visibility into infrastructure is more critical than ever. To meet the unique needs of different environments, ServiceNow AI Platform offers two purpose-built visibility solutions: ITOM Visibility and Telecom Visibility. | [] | [
"Telecommunications Service Operations Management",
"Exploring Telecommunications Service Operations Management",
"Telecom Visibility"
] | <article class="hascomments" data-page="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/tsom-visibility-vs--itom-visibility.html" id="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/tsom-visibility-vs--itom-visibility.html"><body id="tsom-visibility-vs--itom-visibility"><main role="main"><article role="article" class="dita" id="tsom-visibility-vs--itom-visibility" aria-labelledby="title_tsom-visibility-vs--itom-visibility">
<h1 class="title topictitle1" id="title_tsom-visibility-vs--itom-visibility">Telecom Visibility vs. ITOM Visibility</h1>
<div class="body conbody"><p class="shortdesc">As telecom networks evolve and become more hybrid and complex, visibility into infrastructure is more critical than ever. To meet the unique needs of different environments, <span class="ph">ServiceNow AI Platform</span> offers two purpose-built visibility solutions: ITOM Visibility and Telecom Visibility.</p>
<p class="p">While they’re built on the same foundation, each is tailored to serve a different world—ITOM for traditional IT infrastructure and TSOM for telecom networks.</p>
<p class="p">Both ITOM Visibility and Telecom Visibility are built on the same underlying capabilities of the ServiceNow Discovery engine, Identification and Reconciliation Engine (IRE), and CMDB. They both provide:</p>
<ul class="ul" id="tsom-visibility-vs--itom-visibility__ul_e3x_rl4_tfc">
<li class="li">Agent-based and agentless discovery.</li>
<li class="li">Horizontal and pattern-based discovery.</li>
<li class="li">Reconciliation of discovered data into CMDB.</li>
<li class="li">Dependency mapping and CI relationship creation.</li>
<li class="li">Integration with the Discovery Admin Workspace and CMDB 360.</li>
</ul>
<p class="p">Despite this shared architecture, the scope, use cases, and data models they serve are different.</p>
<section class="section" id="tsom-visibility-vs--itom-visibility__section_o42_tl4_tfc"><h2 id="d2629e72" class="title sectiontitle">Key differences between TSOM and ITOM Visibility</h2>
<div class="p">
<div class="table-wrap"><table count-columns="3" class="table frame-all" id="tsom-visibility-vs--itom-visibility__table_rgn_vl4_tfc"><caption><span class="table--title-label">Table 1. </span><span class="title">Telecom Visibility vs. ITOM Visibility</span></caption><colgroup><col style="width:33.33333333333333%"/><col style="width:33.33333333333333%"/><col style="width:33.33333333333333%"/></colgroup><thead class="thead">
<tr class="row">
<th class="entry colsep-1 rowsep-1" id="tsom-visibility-vs--itom-visibility__table_rgn_vl4_tfc__entry__1">Feature / Focus Area</th>
<th class="entry colsep-1 rowsep-1" id="tsom-visibility-vs--itom-visibility__table_rgn_vl4_tfc__entry__2">ITOM Visibility</th>
<th class="entry colsep-1 rowsep-1" id="tsom-visibility-vs--itom-visibility__table_rgn_vl4_tfc__entry__3">Telecom Visibility</th>
</tr>
</thead><tbody class="tbody">
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="tsom-visibility-vs--itom-visibility__table_rgn_vl4_tfc__entry__1">Target Environment</td>
<td class="entry colsep-1 rowsep-1" headers="tsom-visibility-vs--itom-visibility__table_rgn_vl4_tfc__entry__2">Traditional IT infrastructure (servers, applications, databases, cloud resources)</td>
<td class="entry colsep-1 rowsep-1" headers="tsom-visibility-vs--itom-visibility__table_rgn_vl4_tfc__entry__3">Telecom infrastructure (xNFs, network elements, EMS/NMS controllers)</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="tsom-visibility-vs--itom-visibility__table_rgn_vl4_tfc__entry__1">Discovery Method</td>
<td class="entry colsep-1 rowsep-1" headers="tsom-visibility-vs--itom-visibility__table_rgn_vl4_tfc__entry__2">Horizontal Discovery with IT patterns</td>
<td class="entry colsep-1 rowsep-1" headers="tsom-visibility-vs--itom-visibility__table_rgn_vl4_tfc__entry__3">Horizontal Discovery with Telecommunications Discovery Patterns (SNMP/CLI) and Service Graph Connectors for telecom</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="tsom-visibility-vs--itom-visibility__table_rgn_vl4_tfc__entry__1">CMDB Model</td>
<td class="entry colsep-1 rowsep-1" headers="tsom-visibility-vs--itom-visibility__table_rgn_vl4_tfc__entry__2">ITOM CMDB classes (for example, Windows Server, Application, Network Adapter)</td>
<td class="entry colsep-1 rowsep-1" headers="tsom-visibility-vs--itom-visibility__table_rgn_vl4_tfc__entry__3">Telecom-aware CMDB classes and Telecom Network Inventory (TNI) (for example, Interface Cards, Slots, LAGs, Subslots, VLANs)</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="tsom-visibility-vs--itom-visibility__table_rgn_vl4_tfc__entry__1">Plugins required</td>
<td class="entry colsep-1 rowsep-1" headers="tsom-visibility-vs--itom-visibility__table_rgn_vl4_tfc__entry__2">com.snc.discovery and com.snc.itom.visibility</td>
<td class="entry colsep-1 rowsep-1" headers="tsom-visibility-vs--itom-visibility__table_rgn_vl4_tfc__entry__3">sn_tsom_core, sn_tsom_patterns, and telecom-specific SGC plugins (for example, sn_sgc_altiplano_connector)</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="tsom-visibility-vs--itom-visibility__table_rgn_vl4_tfc__entry__1">Use Case Focus</td>
<td class="entry colsep-1 rowsep-1" headers="tsom-visibility-vs--itom-visibility__table_rgn_vl4_tfc__entry__2">Application dependency mapping, service modeling, cloud infrastructure discovery</td>
<td class="entry colsep-1 rowsep-1" headers="tsom-visibility-vs--itom-visibility__table_rgn_vl4_tfc__entry__3">Telecom network inventory discovery, reconciliation, autonomous network operations</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="tsom-visibility-vs--itom-visibility__table_rgn_vl4_tfc__entry__1">Discrepancy Handling</td>
<td class="entry colsep-1 rowsep-1" headers="tsom-visibility-vs--itom-visibility__table_rgn_vl4_tfc__entry__2">General IRE reconciliation rules</td>
<td class="entry colsep-1 rowsep-1" headers="tsom-visibility-vs--itom-visibility__table_rgn_vl4_tfc__entry__3">Telecom-specific discrepancy identification and reconciliation (for example, hierarchy mismatches, attribute-level conflicts)</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="tsom-visibility-vs--itom-visibility__table_rgn_vl4_tfc__entry__1">Vendor Data Ingestion</td>
<td class="entry colsep-1 rowsep-1" headers="tsom-visibility-vs--itom-visibility__table_rgn_vl4_tfc__entry__2">Primarily via discovery patterns</td>
<td class="entry colsep-1 rowsep-1" headers="tsom-visibility-vs--itom-visibility__table_rgn_vl4_tfc__entry__3">Strong emphasis on northbound API integrations using SGCs (EMS/NMS/controllers)</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="tsom-visibility-vs--itom-visibility__table_rgn_vl4_tfc__entry__1">Network Types Supported</td>
<td class="entry colsep-1 rowsep-1" headers="tsom-visibility-vs--itom-visibility__table_rgn_vl4_tfc__entry__2">Enterprise networks, datacenters, cloud</td>
<td class="entry colsep-1 rowsep-1" headers="tsom-visibility-vs--itom-visibility__table_rgn_vl4_tfc__entry__3">Multi-vendor, multi-domain telecom networks (RAN, Core, Transport, Access)</td>
</tr>
</tbody></table></div>
</div>
</section>
<section class="section" id="tsom-visibility-vs--itom-visibility__section_wr1_cm4_tfc"><h2 id="d2629e212" class="title sectiontitle">Infographic</h2>
<p class="p">The following infographic helps you understand the differences between TSOM and ITOM Visibility. <img src="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/../images/telecom-discovery.png?_LANG=enus" class="image" id="tsom-visibility-vs--itom-visibility__image_n5m_5m3_b2c" alt="Infographic that shows the differences between ITOM Visibility and Telecom Visibility."/></p>
</section>
<section class="section" id="tsom-visibility-vs--itom-visibility__section_xfk_fm4_tfc"><h2 id="d2629e226" class="title sectiontitle">Key benefits</h2>
<p class="p">Use ITOM Visibility when:</p>
<ul class="ul" id="tsom-visibility-vs--itom-visibility__ul_pgj_gm4_tfc">
<li class="li">You’re discovering IT infrastructure components (for example, Windows servers, cloud VMs, databases, load balancers).</li>
<li class="li">Your primary goals include service mapping, operational resilience, or cloud optimization.</li>
<li class="li">You’re focusing on ITSM, ITOM, or DevOps use cases.</li>
</ul>
<p class="p">Use Telecom Visibility when:</p>
<ul class="ul" id="tsom-visibility-vs--itom-visibility__ul_qgj_gm4_tfc">
<li class="li">You’re discovering telecom network infrastructure, including devices not managed by traditional IT systems.</li>
<li class="li">You are dealing with telecom-specific network hierarchies like cards, ports, subslots, and LAGs.</li>
<li class="li">You rely on EMS/NMS/controllers as authoritative data sources.</li>
<li class="li">You need discrepancy detection and reconciliation tailored for telecom inventory models.</li>
<li class="li">You are aligning with TM Forum standards, supporting autonomous network operations, or enabling closed-loop assurance.</li>
</ul>
</section>
<section class="section" id="tsom-visibility-vs--itom-visibility__section_sjy_gm4_tfc"><h2 id="d2629e268" class="title sectiontitle">Examples</h2>
<div class="table-wrap"><table count-columns="3" class="table" id="tsom-visibility-vs--itom-visibility__table_z3h_3m4_tfc"><caption></caption><colgroup><col/><col/><col/></colgroup><tbody class="tbody">
<tr class="row">
<td class="entry">Use Case</td>
<td class="entry">ITOM Visibility</td>
<td class="entry">Telecom Visibility</td>
</tr>
<tr class="row">
<td class="entry">Discover a fleet of virtual machines in AWS</td>
<td class="entry">Yes</td>
<td class="entry">No</td>
</tr>
<tr class="row">
<td class="entry">Ingest router and switch data from an EMS using APIs</td>
<td class="entry">No</td>
<td class="entry">Yes</td>
</tr>
<tr class="row">
<td class="entry">Identify application-to-application dependencies</td>
<td class="entry">Yes</td>
<td class="entry">No</td>
</tr>
<tr class="row">
<td class="entry">Detect and reconcile mismatches in telecom card hierarchies</td>
<td class="entry">No</td>
<td class="entry">Yes</td>
</tr>
</tbody></table></div>
<p class="p">While ITOM Visibility and Telecom Visibility both serve to populate and maintain an accurate CMDB, they are optimized for different domains. ITOM Visibility is geared toward enterprise IT environments, while Telecom Visibility is
tailored for the specialized needs of telecom infrastructure discovery, discrepancy management, and inventory reconciliation.</p>
<p class="p">Choosing the right visibility solution—or using both in tandem—confirms that you maintain trusted, domain-specific operational visibility across both IT and telecom landscapes.</p>
</section>
</div>
</article></main></body></article> | {
"attachments": {
"all_attachments": null,
"topic_attachments": []
},
"available_languages": [
"enus"
],
"breadcrumbs": [
{
"title": "Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html"
},
{
"title": "Exploring Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/exploring-tsom.html"
},
{
"title": "Telecom Visibility",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/tsom-visibility.html"
}
],
"breadcrumbs_html": "<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops\">Zurich Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html\">Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/exploring-tsom.html\">Exploring Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/tsom-visibility.html\">Telecom Visibility</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<span class=\"active\">Telecom Visibility vs. ITOM Visibility</span>",
"bundle_id": "zurich-telecom-service-ops",
"bundle_key": 2733,
"bundle_landing_page": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html",
"bundle_subtitle": null,
"bundle_title": "Zurich Telecommunications Service Operations Management",
"canonical_link": null,
"dates": {
"Added on": "2025-08-02T00:48:08.794016Z",
"Created on": "2025-06-24T00:00:00Z",
"Initial upload": "2025-07-30T22:24:33.519043Z",
"Updated on": "2025-07-31T00:00:00Z"
},
"dislike_url": "https://servicenow-be-prod.servicenow.com/dislike/55686949",
"dislikes": 0,
"es_archived_content": false,
"is_in_fav": false,
"is_liked": null,
"is_watched": false,
"keywords": [
" zurich zurich"
],
"labels": [
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "zurich",
"navtitle": "Zurich",
"outputclasses": [],
"subjectHeadId": "versions",
"subjectheadNavtitle": "Versions",
"visibility": "show-facet"
},
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "tsom",
"navtitle": "Telecommunications Service Operations Management",
"outputclasses": [],
"subjectHeadId": "products",
"subjectheadNavtitle": "Products",
"visibility": "show-facet"
}
],
"labels_text": "Versions > Zurich; Products > CRM and Industry Products > Telecommunications Media and Technology Assurance > Telecommunications Service Operations Management",
"like_url": "https://servicenow-be-prod.servicenow.com/like/55686949",
"likes": 0,
"metadata": {
"AI Search": null,
"AI Search Assist": null,
"Application Insights": null,
"Capabilities": null,
"Code Signing": null,
"Contextual Search": null,
"DC.contributor": null,
"DC.coverage": null,
"DC.creator": "ServiceNow",
"DC.date.created": "2025-06-24T08:58:44+05:30",
"DC.date.modified": "2025-07-31",
"DC.format": "HTML5",
"DC.identifier": "tsom-visibility-vs--itom-visibility",
"DC.language": null,
"DC.relation": null,
"DC.rights.owner": "(C) Copyright 2025",
"DC.subject": null,
"DC.type": "concept",
"Data Discovery": null,
"Data Policy": null,
"Data Privacy": null,
"Discovery": null,
"External Content for AI Search": null,
"Field Administration": null,
"Field Normalization": null,
"Key Management Framework": null,
"Localization Framework": null,
"Now Platform": null,
"PlatSec": null,
"Platform": null,
"Platform Administration": null,
"Platform Performance": null,
"Platform Privacy": null,
"Proactive Triggers": null,
"Process Optimization": null,
"RN doc editing record number": null,
"Search Administration": null,
"Secrets Management": null,
"ServiceNow AI Platform": null,
"State Model": null,
"Subscription Management": null,
"Task Communications Management": null,
"Timeline Visualizations": null,
"User Administration": null,
"User Experience Analytics": null,
"Zing": null,
"ai-now-assist": null,
"app-name": null,
"app_route": null,
"azureapimanagemen": null,
"change-completed": null,
"change-item": null,
"change-request-id": null,
"change-request-reference": null,
"com.glide.embedded_help.category": null,
"component": null,
"copyright": "(C) Copyright 2025",
"crossroads": null,
"data": null,
"description": "As telecom networks evolve and become more hybrid and complex, visibility into infrastructure is more critical than ever. To meet the unique needs of different environments, ServiceNow AI Platform offers two purpose-built visibility solutions: ITOM Visibility and Telecom Visibility.",
"dominant_bundle": null,
"erp-canvas-video": null,
"fsm-mobile": null,
"fsm-route": null,
"fsm-sched-opt": null,
"fsm-wrk-order": null,
"genai-round-7": null,
"generator": "DITA-OT",
"glossPartOfSpeech": null,
"glossStatus": null,
"guided setup": null,
"guided tours": null,
"keywords": null,
"min-toc": null,
"mini": null,
"mini-to truec": null,
"mini-toc": "yes",
"mini_toc": null,
"minitoc": null,
"modification": null,
"now-assist-app-gen-video": null,
"order": null,
"page-type": null,
"page-type ": null,
"prodname": null,
"product": null,
"product_name": null,
"release": null,
"resourceID": null,
"roles": null,
"route_page": null,
"route_params_listId": null,
"route_params_table": null,
"route_params_type": null,
"route_type": null,
"setconfigurationproperties": null,
"topic": null,
"translation-type": "source",
"version": null,
"workflow": "Customer and Industry",
"workplace-srvc-delvry-ditamap": null
},
"page_id": "product/tmt-telecom-service-operations-mgt/concept/tsom-visibility-vs--itom-visibility.html",
"page_key": 55686949,
"preprocessed_PDF": "https://downloads.docs.servicenow.com/pdf/enus/servicenow-zurich-telecom-service-ops-enus.pdf",
"rating": null,
"read_time_data": {
"char_count": 4157,
"img_count": 1,
"read_time": 3,
"video_links": [
""
],
"word_count": 524
},
"related_links": [],
"search_title": null,
"title": "Telecom Visibility vs. ITOM Visibility",
"topic_cluster": {
"clustered_by": {
"enabled": true,
"primary_key": "versions",
"primary_sort": "top-down",
"type": "subjecthead"
},
"clustered_labels": [
"versions"
],
"clustered_topics": [],
"clustering_title": "Zurich"
},
"topic_html": "<article class=\"hascomments\" data-page=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/tsom-visibility-vs--itom-visibility.html\" id=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/tsom-visibility-vs--itom-visibility.html\"><body id=\"tsom-visibility-vs--itom-visibility\"><main role=\"main\"><article role=\"article\" class=\"dita\" id=\"tsom-visibility-vs--itom-visibility\" aria-labelledby=\"title_tsom-visibility-vs--itom-visibility\">\n <h1 class=\"title topictitle1\" id=\"title_tsom-visibility-vs--itom-visibility\">Telecom Visibility vs. ITOM Visibility</h1>\n \n \n <div class=\"body conbody\"><p class=\"shortdesc\">As telecom networks evolve and become more hybrid and complex, visibility into infrastructure is more critical than ever. To meet the unique needs of different environments, <span class=\"ph\">ServiceNow AI Platform</span> offers two purpose-built visibility solutions: ITOM Visibility and Telecom Visibility.</p>\n <p class=\"p\">While they’re built on the same foundation, each is tailored to serve a different world—ITOM for traditional IT infrastructure and TSOM for telecom networks.</p>\n <p class=\"p\">Both ITOM Visibility and Telecom Visibility are built on the same underlying capabilities of the ServiceNow Discovery engine, Identification and Reconciliation Engine (IRE), and CMDB. They both provide:</p>\n <ul class=\"ul\" id=\"tsom-visibility-vs--itom-visibility__ul_e3x_rl4_tfc\">\n <li class=\"li\">Agent-based and agentless discovery.</li>\n <li class=\"li\">Horizontal and pattern-based discovery.</li>\n <li class=\"li\">Reconciliation of discovered data into CMDB.</li>\n <li class=\"li\">Dependency mapping and CI relationship creation.</li>\n <li class=\"li\">Integration with the Discovery Admin Workspace and CMDB 360.</li>\n </ul>\n <p class=\"p\">Despite this shared architecture, the scope, use cases, and data models they serve are different.</p>\n <section class=\"section\" id=\"tsom-visibility-vs--itom-visibility__section_o42_tl4_tfc\"><h2 id=\"d2629e72\" class=\"title sectiontitle\">Key differences between TSOM and ITOM Visibility</h2>\n \n <div class=\"p\">\n <div class=\"table-wrap\"><table count-columns=\"3\" class=\"table frame-all\" id=\"tsom-visibility-vs--itom-visibility__table_rgn_vl4_tfc\"><caption><span class=\"table--title-label\">Table 1. </span><span class=\"title\">Telecom Visibility vs. ITOM Visibility</span></caption><colgroup><col style=\"width:33.33333333333333%\"/><col style=\"width:33.33333333333333%\"/><col style=\"width:33.33333333333333%\"/></colgroup><thead class=\"thead\">\n <tr class=\"row\">\n <th class=\"entry colsep-1 rowsep-1\" id=\"tsom-visibility-vs--itom-visibility__table_rgn_vl4_tfc__entry__1\">Feature / Focus Area</th>\n <th class=\"entry colsep-1 rowsep-1\" id=\"tsom-visibility-vs--itom-visibility__table_rgn_vl4_tfc__entry__2\">ITOM Visibility</th>\n <th class=\"entry colsep-1 rowsep-1\" id=\"tsom-visibility-vs--itom-visibility__table_rgn_vl4_tfc__entry__3\">Telecom Visibility</th>\n </tr>\n </thead><tbody class=\"tbody\">\n <tr class=\"row\">\n <td class=\"entry colsep-1 rowsep-1\" headers=\"tsom-visibility-vs--itom-visibility__table_rgn_vl4_tfc__entry__1\">Target Environment</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"tsom-visibility-vs--itom-visibility__table_rgn_vl4_tfc__entry__2\">Traditional IT infrastructure (servers, applications, databases, cloud resources)</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"tsom-visibility-vs--itom-visibility__table_rgn_vl4_tfc__entry__3\">Telecom infrastructure (xNFs, network elements, EMS/NMS controllers)</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry colsep-1 rowsep-1\" headers=\"tsom-visibility-vs--itom-visibility__table_rgn_vl4_tfc__entry__1\">Discovery Method</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"tsom-visibility-vs--itom-visibility__table_rgn_vl4_tfc__entry__2\">Horizontal Discovery with IT patterns</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"tsom-visibility-vs--itom-visibility__table_rgn_vl4_tfc__entry__3\">Horizontal Discovery with Telecommunications Discovery Patterns (SNMP/CLI) and Service Graph Connectors for telecom</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry colsep-1 rowsep-1\" headers=\"tsom-visibility-vs--itom-visibility__table_rgn_vl4_tfc__entry__1\">CMDB Model</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"tsom-visibility-vs--itom-visibility__table_rgn_vl4_tfc__entry__2\">ITOM CMDB classes (for example, Windows Server, Application, Network Adapter)</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"tsom-visibility-vs--itom-visibility__table_rgn_vl4_tfc__entry__3\">Telecom-aware CMDB classes and Telecom Network Inventory (TNI) (for example, Interface Cards, Slots, LAGs, Subslots, VLANs)</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry colsep-1 rowsep-1\" headers=\"tsom-visibility-vs--itom-visibility__table_rgn_vl4_tfc__entry__1\">Plugins required</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"tsom-visibility-vs--itom-visibility__table_rgn_vl4_tfc__entry__2\">com.snc.discovery and com.snc.itom.visibility</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"tsom-visibility-vs--itom-visibility__table_rgn_vl4_tfc__entry__3\">sn_tsom_core, sn_tsom_patterns, and telecom-specific SGC plugins (for example, sn_sgc_altiplano_connector)</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry colsep-1 rowsep-1\" headers=\"tsom-visibility-vs--itom-visibility__table_rgn_vl4_tfc__entry__1\">Use Case Focus</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"tsom-visibility-vs--itom-visibility__table_rgn_vl4_tfc__entry__2\">Application dependency mapping, service modeling, cloud infrastructure discovery</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"tsom-visibility-vs--itom-visibility__table_rgn_vl4_tfc__entry__3\">Telecom network inventory discovery, reconciliation, autonomous network operations</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry colsep-1 rowsep-1\" headers=\"tsom-visibility-vs--itom-visibility__table_rgn_vl4_tfc__entry__1\">Discrepancy Handling</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"tsom-visibility-vs--itom-visibility__table_rgn_vl4_tfc__entry__2\">General IRE reconciliation rules</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"tsom-visibility-vs--itom-visibility__table_rgn_vl4_tfc__entry__3\">Telecom-specific discrepancy identification and reconciliation (for example, hierarchy mismatches, attribute-level conflicts)</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry colsep-1 rowsep-1\" headers=\"tsom-visibility-vs--itom-visibility__table_rgn_vl4_tfc__entry__1\">Vendor Data Ingestion</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"tsom-visibility-vs--itom-visibility__table_rgn_vl4_tfc__entry__2\">Primarily via discovery patterns</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"tsom-visibility-vs--itom-visibility__table_rgn_vl4_tfc__entry__3\">Strong emphasis on northbound API integrations using SGCs (EMS/NMS/controllers)</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry colsep-1 rowsep-1\" headers=\"tsom-visibility-vs--itom-visibility__table_rgn_vl4_tfc__entry__1\">Network Types Supported</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"tsom-visibility-vs--itom-visibility__table_rgn_vl4_tfc__entry__2\">Enterprise networks, datacenters, cloud</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"tsom-visibility-vs--itom-visibility__table_rgn_vl4_tfc__entry__3\">Multi-vendor, multi-domain telecom networks (RAN, Core, Transport, Access)</td>\n </tr>\n </tbody></table></div>\n </div>\n </section>\n <section class=\"section\" id=\"tsom-visibility-vs--itom-visibility__section_wr1_cm4_tfc\"><h2 id=\"d2629e212\" class=\"title sectiontitle\">Infographic</h2>\n \n <p class=\"p\">The following infographic helps you understand the differences between TSOM and ITOM Visibility. <img src=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/../images/telecom-discovery.png?_LANG=enus\" class=\"image\" id=\"tsom-visibility-vs--itom-visibility__image_n5m_5m3_b2c\" alt=\"Infographic that shows the differences between ITOM Visibility and Telecom Visibility.\"/></p>\n </section>\n <section class=\"section\" id=\"tsom-visibility-vs--itom-visibility__section_xfk_fm4_tfc\"><h2 id=\"d2629e226\" class=\"title sectiontitle\">Key benefits</h2>\n \n <p class=\"p\">Use ITOM Visibility when:</p>\n <ul class=\"ul\" id=\"tsom-visibility-vs--itom-visibility__ul_pgj_gm4_tfc\">\n <li class=\"li\">You’re discovering IT infrastructure components (for example, Windows servers, cloud VMs, databases, load balancers).</li>\n <li class=\"li\">Your primary goals include service mapping, operational resilience, or cloud optimization.</li>\n <li class=\"li\">You’re focusing on ITSM, ITOM, or DevOps use cases.</li>\n </ul>\n <p class=\"p\">Use Telecom Visibility when:</p>\n <ul class=\"ul\" id=\"tsom-visibility-vs--itom-visibility__ul_qgj_gm4_tfc\">\n <li class=\"li\">You’re discovering telecom network infrastructure, including devices not managed by traditional IT systems.</li>\n <li class=\"li\">You are dealing with telecom-specific network hierarchies like cards, ports, subslots, and LAGs.</li>\n <li class=\"li\">You rely on EMS/NMS/controllers as authoritative data sources.</li>\n <li class=\"li\">You need discrepancy detection and reconciliation tailored for telecom inventory models.</li>\n <li class=\"li\">You are aligning with TM Forum standards, supporting autonomous network operations, or enabling closed-loop assurance.</li>\n </ul>\n </section>\n <section class=\"section\" id=\"tsom-visibility-vs--itom-visibility__section_sjy_gm4_tfc\"><h2 id=\"d2629e268\" class=\"title sectiontitle\">Examples</h2>\n \n <div class=\"table-wrap\"><table count-columns=\"3\" class=\"table\" id=\"tsom-visibility-vs--itom-visibility__table_z3h_3m4_tfc\"><caption></caption><colgroup><col/><col/><col/></colgroup><tbody class=\"tbody\">\n <tr class=\"row\">\n <td class=\"entry\">Use Case</td>\n <td class=\"entry\">ITOM Visibility</td>\n <td class=\"entry\">Telecom Visibility</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry\">Discover a fleet of virtual machines in AWS</td>\n <td class=\"entry\">Yes</td>\n <td class=\"entry\">No</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry\">Ingest router and switch data from an EMS using APIs</td>\n <td class=\"entry\">No</td>\n <td class=\"entry\">Yes</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry\">Identify application-to-application dependencies</td>\n <td class=\"entry\">Yes</td>\n <td class=\"entry\">No</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry\">Detect and reconcile mismatches in telecom card hierarchies</td>\n <td class=\"entry\">No</td>\n <td class=\"entry\">Yes</td>\n </tr>\n </tbody></table></div>\n <p class=\"p\">While ITOM Visibility and Telecom Visibility both serve to populate and maintain an accurate CMDB, they are optimized for different domains. ITOM Visibility is geared toward enterprise IT environments, while Telecom Visibility is\n tailored for the specialized needs of telecom infrastructure discovery, discrepancy management, and inventory reconciliation.</p>\n <p class=\"p\">Choosing the right visibility solution—or using both in tandem—confirms that you maintain trusted, domain-specific operational visibility across both IT and telecom landscapes.</p>\n </section>\n </div>\n</article></main></body></article>",
"topic_language": "enus",
"views": 0,
"your_rating": null
} | # Telecom Visibility vs. ITOM Visibility
As telecom networks evolve and become more hybrid and complex, visibility into infrastructure is more critical than ever. To meet the unique needs of different environments, ServiceNow AI Platform offers two purpose-built visibility solutions: ITOM Visibility and Telecom Visibility.
While they’re built on the same foundation, each is tailored to serve a different world—ITOM for traditional IT infrastructure and TSOM for telecom networks.
Both ITOM Visibility and Telecom Visibility are built on the same underlying capabilities of the ServiceNow Discovery engine, Identification and Reconciliation Engine (IRE), and CMDB. They both provide:
* Agent-based and agentless discovery.
* Horizontal and pattern-based discovery.
* Reconciliation of discovered data into CMDB.
* Dependency mapping and CI relationship creation.
* Integration with the Discovery Admin Workspace and CMDB 360.
Despite this shared architecture, the scope, use cases, and data models they serve are different.
## Key differences between TSOM and ITOM Visibility
Table 1. Telecom Visibility vs. ITOM Visibility
| Feature / Focus Area | ITOM Visibility | Telecom Visibility |
| --- | --- | --- |
| Target Environment | Traditional IT infrastructure (servers, applications, databases, cloud resources) | Telecom infrastructure (xNFs, network elements, EMS/NMS controllers) |
| Discovery Method | Horizontal Discovery with IT patterns | Horizontal Discovery with Telecommunications Discovery Patterns (SNMP/CLI) and Service Graph Connectors for telecom |
| CMDB Model | ITOM CMDB classes (for example, Windows Server, Application, Network Adapter) | Telecom-aware CMDB classes and Telecom Network Inventory (TNI) (for example, Interface Cards, Slots, LAGs, Subslots, VLANs) |
| Plugins required | com.snc.discovery and com.snc.itom.visibility | sn\_tsom\_core, sn\_tsom\_patterns, and telecom-specific SGC plugins (for example, sn\_sgc\_altiplano\_connector) |
| Use Case Focus | Application dependency mapping, service modeling, cloud infrastructure discovery | Telecom network inventory discovery, reconciliation, autonomous network operations |
| Discrepancy Handling | General IRE reconciliation rules | Telecom-specific discrepancy identification and reconciliation (for example, hierarchy mismatches, attribute-level conflicts) |
| Vendor Data Ingestion | Primarily via discovery patterns | Strong emphasis on northbound API integrations using SGCs (EMS/NMS/controllers) |
| Network Types Supported | Enterprise networks, datacenters, cloud | Multi-vendor, multi-domain telecom networks (RAN, Core, Transport, Access) |
## Infographic
The following infographic helps you understand the differences between TSOM and ITOM Visibility.
## Key benefits
Use ITOM Visibility when:
* You’re discovering IT infrastructure components (for example, Windows servers, cloud VMs, databases, load balancers).
* Your primary goals include service mapping, operational resilience, or cloud optimization.
* You’re focusing on ITSM, ITOM, or DevOps use cases.
Use Telecom Visibility when:
* You’re discovering telecom network infrastructure, including devices not managed by traditional IT systems.
* You are dealing with telecom-specific network hierarchies like cards, ports, subslots, and LAGs.
* You rely on EMS/NMS/controllers as authoritative data sources.
* You need discrepancy detection and reconciliation tailored for telecom inventory models.
* You are aligning with TM Forum standards, supporting autonomous network operations, or enabling closed-loop assurance.
## Examples
| Use Case | ITOM Visibility | Telecom Visibility |
| --- | --- | --- |
| Discover a fleet of virtual machines in AWS | Yes | No |
| Ingest router and switch data from an EMS using APIs | No | Yes |
| Identify application-to-application dependencies | Yes | No |
| Detect and reconcile mismatches in telecom card hierarchies | No | Yes |
While ITOM Visibility and Telecom Visibility both serve to populate and maintain an accurate CMDB, they are optimized for different domains. ITOM Visibility is geared toward enterprise IT environments, while Telecom Visibility is
tailored for the specialized needs of telecom infrastructure discovery, discrepancy management, and inventory reconciliation.
Choosing the right visibility solution—or using both in tandem—confirms that you maintain trusted, domain-specific operational visibility across both IT and telecom landscapes.
| ---
title: Telecom Visibility vs. ITOM Visibility
description: 'As telecom networks evolve and become more hybrid and complex, visibility
into infrastructure is more critical than ever. To meet the unique needs of different
environments, ServiceNow AI Platform offers two purpose-built visibility solutions:
ITOM Visibility and Telecom Visibility.'
keywords: []
breadcrumbs:
- Telecommunications Service Operations Management
- Exploring Telecommunications Service Operations Management
- Telecom Visibility
---
# Telecom Visibility vs. ITOM Visibility
As telecom networks evolve and become more hybrid and complex, visibility into infrastructure is more critical than ever. To meet the unique needs of different environments, ServiceNow AI Platform offers two purpose-built visibility solutions: ITOM Visibility and Telecom Visibility.
While they’re built on the same foundation, each is tailored to serve a different world—ITOM for traditional IT infrastructure and TSOM for telecom networks.
Both ITOM Visibility and Telecom Visibility are built on the same underlying capabilities of the ServiceNow Discovery engine, Identification and Reconciliation Engine (IRE), and CMDB. They both provide:
* Agent-based and agentless discovery.
* Horizontal and pattern-based discovery.
* Reconciliation of discovered data into CMDB.
* Dependency mapping and CI relationship creation.
* Integration with the Discovery Admin Workspace and CMDB 360.
Despite this shared architecture, the scope, use cases, and data models they serve are different.
## Key differences between TSOM and ITOM Visibility
Table 1. Telecom Visibility vs. ITOM Visibility
| Feature / Focus Area | ITOM Visibility | Telecom Visibility |
| --- | --- | --- |
| Target Environment | Traditional IT infrastructure (servers, applications, databases, cloud resources) | Telecom infrastructure (xNFs, network elements, EMS/NMS controllers) |
| Discovery Method | Horizontal Discovery with IT patterns | Horizontal Discovery with Telecommunications Discovery Patterns (SNMP/CLI) and Service Graph Connectors for telecom |
| CMDB Model | ITOM CMDB classes (for example, Windows Server, Application, Network Adapter) | Telecom-aware CMDB classes and Telecom Network Inventory (TNI) (for example, Interface Cards, Slots, LAGs, Subslots, VLANs) |
| Plugins required | com.snc.discovery and com.snc.itom.visibility | sn\_tsom\_core, sn\_tsom\_patterns, and telecom-specific SGC plugins (for example, sn\_sgc\_altiplano\_connector) |
| Use Case Focus | Application dependency mapping, service modeling, cloud infrastructure discovery | Telecom network inventory discovery, reconciliation, autonomous network operations |
| Discrepancy Handling | General IRE reconciliation rules | Telecom-specific discrepancy identification and reconciliation (for example, hierarchy mismatches, attribute-level conflicts) |
| Vendor Data Ingestion | Primarily via discovery patterns | Strong emphasis on northbound API integrations using SGCs (EMS/NMS/controllers) |
| Network Types Supported | Enterprise networks, datacenters, cloud | Multi-vendor, multi-domain telecom networks (RAN, Core, Transport, Access) |
## Infographic
The following infographic helps you understand the differences between TSOM and ITOM Visibility.
## Key benefits
Use ITOM Visibility when:
* You’re discovering IT infrastructure components (for example, Windows servers, cloud VMs, databases, load balancers).
* Your primary goals include service mapping, operational resilience, or cloud optimization.
* You’re focusing on ITSM, ITOM, or DevOps use cases.
Use Telecom Visibility when:
* You’re discovering telecom network infrastructure, including devices not managed by traditional IT systems.
* You are dealing with telecom-specific network hierarchies like cards, ports, subslots, and LAGs.
* You rely on EMS/NMS/controllers as authoritative data sources.
* You need discrepancy detection and reconciliation tailored for telecom inventory models.
* You are aligning with TM Forum standards, supporting autonomous network operations, or enabling closed-loop assurance.
## Examples
| Use Case | ITOM Visibility | Telecom Visibility |
| --- | --- | --- |
| Discover a fleet of virtual machines in AWS | Yes | No |
| Ingest router and switch data from an EMS using APIs | No | Yes |
| Identify application-to-application dependencies | Yes | No |
| Detect and reconcile mismatches in telecom card hierarchies | No | Yes |
While ITOM Visibility and Telecom Visibility both serve to populate and maintain an accurate CMDB, they are optimized for different domains. ITOM Visibility is geared toward enterprise IT environments, while Telecom Visibility is
tailored for the specialized needs of telecom infrastructure discovery, discrepancy management, and inventory reconciliation.
Choosing the right visibility solution—or using both in tandem—confirms that you maintain trusted, domain-specific operational visibility across both IT and telecom landscapes.
|
https://www.servicenow.com/docs/en-US/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/tsom-visibility.html | https://servicenow-be-prod.servicenow.com/api/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/tsom-visibility.html | 2025-08-02 | daily | 0.5 | 268.xml | en-US | zurich-telecom-service-ops | product/tmt-telecom-service-operations-mgt/concept/tsom-visibility.html | zurich | Telecom Visibility | Telecom Visibility extends the discovery and reconciliation capabilities of ITOM Visibility to meet the specific needs of telecom service providers. It enables accurate, telecom-aware network inventory by discovering real-time network data, reconciling mismatches, and maintaining a consistent telecom model in | [] | [
"Telecommunications Service Operations Management",
"Exploring Telecommunications Service Operations Management"
] | <article class="hascomments" data-page="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/tsom-visibility.html" id="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/tsom-visibility.html"><body id="tsom-visibility"><main role="main"><article role="article" class="dita" id="tsom-visibility" aria-labelledby="title_tsom-visibility">
<h1 class="title topictitle1" id="title_tsom-visibility">Telecom Visibility</h1>
<div class="body conbody"><p class="shortdesc">Telecom Visibility extends the discovery and reconciliation capabilities of ITOM Visibility to meet the specific needs of telecom service providers. It enables accurate, telecom-aware network inventory by discovering real-time
network data, reconciling mismatches, and maintaining a consistent telecom model in your CMDB and TNI (Telecommunications Network Inventory).</p>
<p class="p">Discover physical and logical network components across telecom domains, reconcile discrepancies between discovery and inventory data, and maintain a telecom-specific CMDB structure to support advanced automation and assurance use
cases.</p>
<section class="section" id="tsom-visibility__section_dch_ct2_wfc"><h2 id="d9721e45" class="title sectiontitle">Telecom Visibility overview</h2>
<p class="p">Telecom Visibility is a unified solution for discovering and managing telecom network resources. It leverages proven discovery technologies such as Horizontal Discovery, Telecommunications Discovery Patterns, and Service Graph
Connectors (SGC) to bring network data from various systems (for example, CLI/SNMP-based standalone devices or API-driven EMS/NMS/controllers) into your CMDB.</p>
<p class="p">Telecom Visibility helps communication service providers (CSPs) and telecom operators:</p>
<ul class="ul" id="tsom-visibility__ul_czg_dt2_wfc">
<li class="li">Discover and maintain telecom-specific network inventory</li>
<li class="li">Reconcile mismatches between planned/design inventory and actual network state</li>
<li class="li">Support Autonomous Network Operations (ANO), service fulfillment, and assurance workflows</li>
</ul>
</section>
<section class="section" id="tsom-visibility__section_fk2_ft2_wfc"><h2 id="d9721e69" class="title sectiontitle">Key Capabilities</h2>
<div class="p">
<div class="table-wrap"><table count-columns="2" class="table" id="tsom-visibility__table_ywx_ft2_wfc"><caption><span class="table--title-label">Table 1. </span><span class="title">Key capabilities of TSOM</span></caption><colgroup><col/><col/></colgroup><thead class="thead">
<tr class="row">
<th class="entry" id="tsom-visibility__table_ywx_ft2_wfc__entry__1">Capability</th>
<th class="entry" id="tsom-visibility__table_ywx_ft2_wfc__entry__2">Description</th>
</tr>
</thead><tbody class="tbody">
<tr class="row">
<td class="entry" headers="tsom-visibility__table_ywx_ft2_wfc__entry__1">Telecom Discovery with Patterns</td>
<td class="entry" headers="tsom-visibility__table_ywx_ft2_wfc__entry__2">Discover standalone network functions (xNFs) such as routers and switches using SNMP and CLI protocols via predefined Telecom Discovery Patterns.</td>
</tr>
<tr class="row">
<td class="entry" headers="tsom-visibility__table_ywx_ft2_wfc__entry__1">Service Graph Connector Integration</td>
<td class="entry" headers="tsom-visibility__table_ywx_ft2_wfc__entry__2">Bring inventory and configuration data from external EMS/NMS/controllers into CMDB using northbound APIs.</td>
</tr>
<tr class="row">
<td class="entry" headers="tsom-visibility__table_ywx_ft2_wfc__entry__1">Discrepancy Identification & Reconciliation</td>
<td class="entry" headers="tsom-visibility__table_ywx_ft2_wfc__entry__2">Detect and resolve mismatches between inventoried and discovered data (for example, missing CIs, model mismatches, stale entries).</td>
</tr>
<tr class="row">
<td class="entry" headers="tsom-visibility__table_ywx_ft2_wfc__entry__1">Telecom-Centric Data Modeling</td>
<td class="entry" headers="tsom-visibility__table_ywx_ft2_wfc__entry__2">Maintain structured and hierarchical telecom data including interface cards, slots, subslots, VLANs, and ports.</td>
</tr>
<tr class="row">
<td class="entry" headers="tsom-visibility__table_ywx_ft2_wfc__entry__1">CMDB Integration</td>
<td class="entry" headers="tsom-visibility__table_ywx_ft2_wfc__entry__2">Use CMDB 360 and Discovery Admin Workspace to monitor discovery sources, attribute changes, and reconciliation outcomes.</td>
</tr>
</tbody></table></div>
</div>
</section>
<section class="section" id="tsom-visibility__section_pdk_j3k_tfc"><h2 id="d9721e151" class="title sectiontitle">Applications and Plugins</h2>
<div class="p">
<ol class="ol" id="tsom-visibility__ol_nk5_b52_wfc">
<li class="li">Telecommunications Horizontal Discovery Patterns: Discovers telecom devices (xNFs) such as routers and switches using SNMP/CLI. Enables accurate inventory updates by scanning live network infrastructure. Supports vendor-specific
patterns including:<ul class="ul" id="tsom-visibility__ul_ez2_kt2_wfc">
<li class="li">Cisco (ASR1K, 7613, Nexus 9000, Nexus 3548)</li>
<li class="li">Juniper (MX80, MX104, MX240, MX460)</li>
</ul></li>
<li class="li">Service Graph Connectors (SGCs) for TSOM: Prebuilt integrations with EMS/NMS/controllers to import inventory data via APIs. Supports:<ul class="ul" id="tsom-visibility__ul_gz2_kt2_wfc">
<li class="li">Scheduled or on-demand discovery</li>
<li class="li">Multi-instance configurations</li>
<li class="li">Integration with systems like Nokia Altiplano (GPON networks)</li>
</ul></li>
<li class="li">Telecom Visibility Plugin: Provides shared logic and foundational components for both discovery and discrepancy reconciliation. Ensures:<ul class="ul" id="tsom-visibility__ul_iz2_kt2_wfc">
<li class="li">Consistent behavior across TSOM workflows</li>
<li class="li">Reusable components for reconciliation and remediation</li>
</ul></li>
<li class="li">CMDB CI Class Models for Telecom (Required version: 1.69.0): Extends the CMDB to include telecom-specific classes and relationships, including:<ul class="ul" id="tsom-visibility__ul_jbb_252_wfc">
<li class="li">Interface cards</li>
<li class="li">Slots and subslots</li>
<li class="li">Network interfaces</li>
</ul></li>
</ol>
</div>
</section>
<section class="section" id="tsom-visibility__section_njm_ydk_b2c"><h2 id="d9721e213" class="title sectiontitle">Telecom Visibility architecture</h2>
<p class="p">Telecom Visibility combines direct and indirect discovery methods:</p>
<ul class="ul" id="tsom-visibility__ul_hmm_352_wfc">
<li class="li">Direct Discovery using SNMP/CLI (for example, standalone routers/switches)</li>
<li class="li">Indirect Discovery using APIs from EMS/NMS/controllers (for example, Nokia Altiplano)</li>
</ul>
<p class="p">These feed into the CMDB and TNI, which then support decision-making, automation, and network operations. The following infographic demonstrates the architecture of Telecom Visibility. <img src="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/../images/telecom-discovery-discrepancy-identification-reconciliation.png?_LANG=enus" class="image" id="tsom-visibility__image_zbs_c2k_b2c" alt="Telecom Visibility architecture."/></p>
</section>
<section class="section" id="tsom-visibility__section_pfz_n52_wfc"><h2 id="d9721e240" class="title sectiontitle">Use Cases</h2>
<div class="p">
<div class="table-wrap"><table count-columns="2" class="table" id="tsom-visibility__table_ayj_452_wfc"><caption><span class="table--title-label">Table 2. </span><span class="title">Telecom Visibility use cases</span></caption><colgroup><col/><col/></colgroup><thead class="thead">
<tr class="row">
<th class="entry" id="tsom-visibility__table_ayj_452_wfc__entry__1">Use Case</th>
<th class="entry" id="tsom-visibility__table_ayj_452_wfc__entry__2">Outcome</th>
</tr>
</thead><tbody class="tbody">
<tr class="row">
<td class="entry" headers="tsom-visibility__table_ayj_452_wfc__entry__1">Autonomous Network Operations</td>
<td class="entry" headers="tsom-visibility__table_ayj_452_wfc__entry__2">Reliable network inventory supports AI/ML-driven automation.</td>
</tr>
<tr class="row">
<td class="entry" headers="tsom-visibility__table_ayj_452_wfc__entry__1">Service Fulfillment</td>
<td class="entry" headers="tsom-visibility__table_ayj_452_wfc__entry__2">Accurate CMDB/TNI ensures order accuracy and rapid provisioning.</td>
</tr>
<tr class="row">
<td class="entry" headers="tsom-visibility__table_ayj_452_wfc__entry__1">Service Assurance</td>
<td class="entry" headers="tsom-visibility__table_ayj_452_wfc__entry__2">Reconciled inventory reduces troubleshooting time and increases uptime.</td>
</tr>
<tr class="row">
<td class="entry" headers="tsom-visibility__table_ayj_452_wfc__entry__1">Audit & Compliance</td>
<td class="entry" headers="tsom-visibility__table_ayj_452_wfc__entry__2">Discovery Admin Workspace and CMDB 360 support audit readiness and traceability.</td>
</tr>
</tbody></table></div>
</div>
</section>
<section class="section" id="tsom-visibility__section_gfc_jkk_tfc"><h2 id="d9721e313" class="title sectiontitle">Key personas</h2>
<div class="p">Telecom Visibility is used by: <ul class="ul" id="tsom-visibility__ul_hys_kkk_tfc">
<li class="li">Network and infrastructure teams: Discover and manage real-time network resource data across vendors and technologies.</li>
<li class="li">Inventory and fulfillment teams: Maintain an accurate and complete CMDB/TNI to support service fulfillment, order management, and provisioning.</li>
<li class="li">Platform administrators: Configure plugins, manage discovery sources, validate reconciliation rules, and monitor discovery performance.</li>
</ul></div>
</section>
<section class="section" id="tsom-visibility__section_b5x_r52_wfc"><h2 id="d9721e333" class="title sectiontitle">Monitoring tools</h2>
<p class="p">Discovery Admin Workspace - Central console to:</p>
<ul class="ul" id="tsom-visibility__ul_c5x_r52_wfc">
<li class="li">Monitor discovery tasks</li>
<li class="li">Validate reconciliation processes</li>
<li class="li">Tune schedules and view diagnostics</li>
</ul>
<div class="p">CMDB 360 - Visualize:<ul class="ul" id="tsom-visibility__ul_e5x_r52_wfc">
<li class="li">Attribute-level update history</li>
<li class="li">Source attribution</li>
<li class="li">Reconciliation rules in action</li>
</ul></div>
</section>
<section class="section" id="tsom-visibility__section_x2x_bv2_wfc"><h2 id="d9721e368" class="title sectiontitle">Key benefits</h2>
<div class="p">
<div class="table-wrap"><table count-columns="2" class="table" id="tsom-visibility__table_cw4_cv2_wfc"><caption><span class="table--title-label">Table 3. </span><span class="title">Key benefits of Telecom Visibility</span></caption><colgroup><col/><col/></colgroup><thead class="thead">
<tr class="row">
<th class="entry" id="tsom-visibility__table_cw4_cv2_wfc__entry__1">Feature</th>
<th class="entry" id="tsom-visibility__table_cw4_cv2_wfc__entry__2">Benefit</th>
</tr>
</thead><tbody class="tbody">
<tr class="row">
<td class="entry" headers="tsom-visibility__table_cw4_cv2_wfc__entry__1">CLI/SNMP Discovery</td>
<td class="entry" headers="tsom-visibility__table_cw4_cv2_wfc__entry__2">Expands network coverage without relying on external APIs.</td>
</tr>
<tr class="row">
<td class="entry" headers="tsom-visibility__table_cw4_cv2_wfc__entry__1">Nokia Altiplano Integration</td>
<td class="entry" headers="tsom-visibility__table_cw4_cv2_wfc__entry__2">Supports GPON network discovery across multiple controller instances.</td>
</tr>
<tr class="row">
<td class="entry" headers="tsom-visibility__table_cw4_cv2_wfc__entry__1">Discrepancy Reconciliation</td>
<td class="entry" headers="tsom-visibility__table_cw4_cv2_wfc__entry__2">Keeps inventory clean, actionable, and aligned with real network state.</td>
</tr>
</tbody></table></div>
</div>
</section>
</div>
<nav role="navigation"></nav><nav role="navigation" class="tasksNavigation"></nav><nav role="navigation" class="related-links"><div class="col-md-4"><dt>Related tasks</dt><dd><ul><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/task/configuring-tsom-visibility.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/configuring-tsom-visibility.html" class="link" title="Telecom Visibility provides foundational capabilities that support both Telecom Discovery and Telecom Discrepancy Identification & Reconciliation. It includes shared logic, enhanced CI class models, and Identification and Reconciliation Engine (IRE) updates tailored for telecom network elements.">Set up Telecom Visibility</a></li></ul></dd></div><div class="col-md-4"><dt>Related topics</dt><dd><ul><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/concept//csh" href="https://servicenow-be-prod.servicenow.com/csh?topicname=discovery-admin-workspace&version=zurich&pubname=zurich-it-operations-management" class="link">Discovery Admin Workspace</a></li></ul></dd></div></nav>
</article></main></body></article> | {
"attachments": {
"all_attachments": null,
"topic_attachments": []
},
"available_languages": [
"enus"
],
"breadcrumbs": [
{
"title": "Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html"
},
{
"title": "Exploring Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/exploring-tsom.html"
}
],
"breadcrumbs_html": "<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops\">Zurich Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html\">Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/exploring-tsom.html\">Exploring Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<span class=\"active\">Telecom Visibility</span>",
"bundle_id": "zurich-telecom-service-ops",
"bundle_key": 2733,
"bundle_landing_page": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html",
"bundle_subtitle": null,
"bundle_title": "Zurich Telecommunications Service Operations Management",
"canonical_link": null,
"dates": {
"Added on": "2025-08-02T00:48:08.794016Z",
"Created on": "2025-01-17T00:00:00Z",
"Initial upload": "2025-07-30T22:24:33.519043Z",
"Updated on": "2025-07-31T00:00:00Z"
},
"dislike_url": "https://servicenow-be-prod.servicenow.com/dislike/55686950",
"dislikes": 0,
"es_archived_content": false,
"is_in_fav": false,
"is_liked": null,
"is_watched": false,
"keywords": [
" zurich zurich"
],
"labels": [
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "zurich",
"navtitle": "Zurich",
"outputclasses": [],
"subjectHeadId": "versions",
"subjectheadNavtitle": "Versions",
"visibility": "show-facet"
},
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "tsom",
"navtitle": "Telecommunications Service Operations Management",
"outputclasses": [],
"subjectHeadId": "products",
"subjectheadNavtitle": "Products",
"visibility": "show-facet"
}
],
"labels_text": "Versions > Zurich; Products > CRM and Industry Products > Telecommunications Media and Technology Assurance > Telecommunications Service Operations Management",
"like_url": "https://servicenow-be-prod.servicenow.com/like/55686950",
"likes": 0,
"metadata": {
"AI Search": null,
"AI Search Assist": null,
"Application Insights": null,
"Capabilities": null,
"Code Signing": null,
"Contextual Search": null,
"DC.contributor": null,
"DC.coverage": null,
"DC.creator": "ServiceNow",
"DC.date.created": "2025-01-17T12:16:21+05:30",
"DC.date.modified": "2025-07-31",
"DC.format": "HTML5",
"DC.identifier": "tsom-visibility",
"DC.language": null,
"DC.relation": "../task/configuring-tsom-visibility.html",
"DC.rights.owner": "(C) Copyright 2025",
"DC.subject": null,
"DC.type": "concept",
"Data Discovery": null,
"Data Policy": null,
"Data Privacy": null,
"Discovery": null,
"External Content for AI Search": null,
"Field Administration": null,
"Field Normalization": null,
"Key Management Framework": null,
"Localization Framework": null,
"Now Platform": null,
"PlatSec": null,
"Platform": null,
"Platform Administration": null,
"Platform Performance": null,
"Platform Privacy": null,
"Proactive Triggers": null,
"Process Optimization": null,
"RN doc editing record number": null,
"Search Administration": null,
"Secrets Management": null,
"ServiceNow AI Platform": null,
"State Model": null,
"Subscription Management": null,
"Task Communications Management": null,
"Timeline Visualizations": null,
"User Administration": null,
"User Experience Analytics": null,
"Zing": null,
"ai-now-assist": null,
"app-name": null,
"app_route": null,
"azureapimanagemen": null,
"change-completed": null,
"change-item": null,
"change-request-id": null,
"change-request-reference": null,
"com.glide.embedded_help.category": null,
"component": null,
"copyright": "(C) Copyright 2025",
"crossroads": null,
"data": null,
"description": "Telecom Visibility extends the discovery and reconciliation capabilities of ITOM Visibility to meet the specific needs of telecom service providers. It enables accurate, telecom-aware network inventory by discovering real-time network data, reconciling mismatches, and maintaining a consistent telecom model in",
"dominant_bundle": null,
"erp-canvas-video": null,
"fsm-mobile": null,
"fsm-route": null,
"fsm-sched-opt": null,
"fsm-wrk-order": null,
"genai-round-7": null,
"generator": "DITA-OT",
"glossPartOfSpeech": null,
"glossStatus": null,
"guided setup": null,
"guided tours": null,
"keywords": null,
"min-toc": null,
"mini": null,
"mini-to truec": null,
"mini-toc": "yes",
"mini_toc": null,
"minitoc": null,
"modification": null,
"now-assist-app-gen-video": null,
"order": null,
"page-type": null,
"page-type ": null,
"prodname": null,
"product": null,
"product_name": null,
"release": null,
"resourceID": null,
"roles": null,
"route_page": null,
"route_params_listId": null,
"route_params_table": null,
"route_params_type": null,
"route_type": null,
"setconfigurationproperties": null,
"topic": null,
"translation-type": "source",
"version": null,
"workflow": "Customer and Industry",
"workplace-srvc-delvry-ditamap": null
},
"page_id": "product/tmt-telecom-service-operations-mgt/concept/tsom-visibility.html",
"page_key": 55686950,
"preprocessed_PDF": "https://downloads.docs.servicenow.com/pdf/enus/servicenow-zurich-telecom-service-ops-enus.pdf",
"rating": null,
"read_time_data": {
"char_count": 5088,
"img_count": 1,
"read_time": 3,
"video_links": [
""
],
"word_count": 622
},
"related_links": [
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "Telecom Visibility provides foundational capabilities that support both Telecom Discovery and Telecom Discrepancy Identification & Reconciliation. It includes shared logic, enhanced CI class models, and Identification and Reconciliation Engine (IRE) updates tailored for telecom network elements.",
"title": "Set up Telecom Visibility",
"topic": "/product/tmt-telecom-service-operations-mgt/task/configuring-tsom-visibility.html",
"type": "task",
"url": null
},
{
"bundle": null,
"role": null,
"scope": "external",
"shortDes": null,
"title": "Discovery Admin Workspace",
"topic": null,
"type": null,
"url": "https://docs.servicenow.com/csh?topicname=discovery-admin-workspace&version=zurich&pubname=zurich-it-operations-management"
}
],
"search_title": null,
"title": "Telecom Visibility",
"topic_cluster": {
"clustered_by": {
"enabled": true,
"primary_key": "versions",
"primary_sort": "top-down",
"type": "subjecthead"
},
"clustered_labels": [
"versions"
],
"clustered_topics": [
{
"bundle_id": "yokohama-telecom-service-ops",
"clustering_title": "Yokohama",
"es_archived_content": false,
"page_id": "product/tmt-telecom-service-operations-mgt/concept/tsom-visibility.html"
}
],
"clustering_title": "Zurich"
},
"topic_html": "<article class=\"hascomments\" data-page=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/tsom-visibility.html\" id=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/tsom-visibility.html\"><body id=\"tsom-visibility\"><main role=\"main\"><article role=\"article\" class=\"dita\" id=\"tsom-visibility\" aria-labelledby=\"title_tsom-visibility\">\n <h1 class=\"title topictitle1\" id=\"title_tsom-visibility\">Telecom Visibility</h1>\n \n \n <div class=\"body conbody\"><p class=\"shortdesc\">Telecom Visibility extends the discovery and reconciliation capabilities of ITOM Visibility to meet the specific needs of telecom service providers. It enables accurate, telecom-aware network inventory by discovering real-time\n network data, reconciling mismatches, and maintaining a consistent telecom model in your CMDB and TNI (Telecommunications Network Inventory).</p>\n <p class=\"p\">Discover physical and logical network components across telecom domains, reconcile discrepancies between discovery and inventory data, and maintain a telecom-specific CMDB structure to support advanced automation and assurance use\n cases.</p>\n <section class=\"section\" id=\"tsom-visibility__section_dch_ct2_wfc\"><h2 id=\"d9721e45\" class=\"title sectiontitle\">Telecom Visibility overview</h2>\n \n <p class=\"p\">Telecom Visibility is a unified solution for discovering and managing telecom network resources. It leverages proven discovery technologies such as Horizontal Discovery, Telecommunications Discovery Patterns, and Service Graph\n Connectors (SGC) to bring network data from various systems (for example, CLI/SNMP-based standalone devices or API-driven EMS/NMS/controllers) into your CMDB.</p>\n <p class=\"p\">Telecom Visibility helps communication service providers (CSPs) and telecom operators:</p>\n <ul class=\"ul\" id=\"tsom-visibility__ul_czg_dt2_wfc\">\n <li class=\"li\">Discover and maintain telecom-specific network inventory</li>\n <li class=\"li\">Reconcile mismatches between planned/design inventory and actual network state</li>\n <li class=\"li\">Support Autonomous Network Operations (ANO), service fulfillment, and assurance workflows</li>\n </ul>\n </section>\n <section class=\"section\" id=\"tsom-visibility__section_fk2_ft2_wfc\"><h2 id=\"d9721e69\" class=\"title sectiontitle\">Key Capabilities</h2>\n \n <div class=\"p\">\n <div class=\"table-wrap\"><table count-columns=\"2\" class=\"table\" id=\"tsom-visibility__table_ywx_ft2_wfc\"><caption><span class=\"table--title-label\">Table 1. </span><span class=\"title\">Key capabilities of TSOM</span></caption><colgroup><col/><col/></colgroup><thead class=\"thead\">\n <tr class=\"row\">\n <th class=\"entry\" id=\"tsom-visibility__table_ywx_ft2_wfc__entry__1\">Capability</th>\n <th class=\"entry\" id=\"tsom-visibility__table_ywx_ft2_wfc__entry__2\">Description</th>\n </tr>\n </thead><tbody class=\"tbody\">\n <tr class=\"row\">\n <td class=\"entry\" headers=\"tsom-visibility__table_ywx_ft2_wfc__entry__1\">Telecom Discovery with Patterns</td>\n <td class=\"entry\" headers=\"tsom-visibility__table_ywx_ft2_wfc__entry__2\">Discover standalone network functions (xNFs) such as routers and switches using SNMP and CLI protocols via predefined Telecom Discovery Patterns.</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry\" headers=\"tsom-visibility__table_ywx_ft2_wfc__entry__1\">Service Graph Connector Integration</td>\n <td class=\"entry\" headers=\"tsom-visibility__table_ywx_ft2_wfc__entry__2\">Bring inventory and configuration data from external EMS/NMS/controllers into CMDB using northbound APIs.</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry\" headers=\"tsom-visibility__table_ywx_ft2_wfc__entry__1\">Discrepancy Identification & Reconciliation</td>\n <td class=\"entry\" headers=\"tsom-visibility__table_ywx_ft2_wfc__entry__2\">Detect and resolve mismatches between inventoried and discovered data (for example, missing CIs, model mismatches, stale entries).</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry\" headers=\"tsom-visibility__table_ywx_ft2_wfc__entry__1\">Telecom-Centric Data Modeling</td>\n <td class=\"entry\" headers=\"tsom-visibility__table_ywx_ft2_wfc__entry__2\">Maintain structured and hierarchical telecom data including interface cards, slots, subslots, VLANs, and ports.</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry\" headers=\"tsom-visibility__table_ywx_ft2_wfc__entry__1\">CMDB Integration</td>\n <td class=\"entry\" headers=\"tsom-visibility__table_ywx_ft2_wfc__entry__2\">Use CMDB 360 and Discovery Admin Workspace to monitor discovery sources, attribute changes, and reconciliation outcomes.</td>\n </tr>\n </tbody></table></div>\n </div>\n </section>\n <section class=\"section\" id=\"tsom-visibility__section_pdk_j3k_tfc\"><h2 id=\"d9721e151\" class=\"title sectiontitle\">Applications and Plugins</h2>\n \n <div class=\"p\">\n <ol class=\"ol\" id=\"tsom-visibility__ol_nk5_b52_wfc\">\n <li class=\"li\">Telecommunications Horizontal Discovery Patterns: Discovers telecom devices (xNFs) such as routers and switches using SNMP/CLI. Enables accurate inventory updates by scanning live network infrastructure. Supports vendor-specific\n patterns including:<ul class=\"ul\" id=\"tsom-visibility__ul_ez2_kt2_wfc\">\n <li class=\"li\">Cisco (ASR1K, 7613, Nexus 9000, Nexus 3548)</li>\n <li class=\"li\">Juniper (MX80, MX104, MX240, MX460)</li>\n </ul></li>\n <li class=\"li\">Service Graph Connectors (SGCs) for TSOM: Prebuilt integrations with EMS/NMS/controllers to import inventory data via APIs. Supports:<ul class=\"ul\" id=\"tsom-visibility__ul_gz2_kt2_wfc\">\n <li class=\"li\">Scheduled or on-demand discovery</li>\n <li class=\"li\">Multi-instance configurations</li>\n <li class=\"li\">Integration with systems like Nokia Altiplano (GPON networks)</li>\n </ul></li>\n <li class=\"li\">Telecom Visibility Plugin: Provides shared logic and foundational components for both discovery and discrepancy reconciliation. Ensures:<ul class=\"ul\" id=\"tsom-visibility__ul_iz2_kt2_wfc\">\n <li class=\"li\">Consistent behavior across TSOM workflows</li>\n <li class=\"li\">Reusable components for reconciliation and remediation</li>\n </ul></li>\n <li class=\"li\">CMDB CI Class Models for Telecom (Required version: 1.69.0): Extends the CMDB to include telecom-specific classes and relationships, including:<ul class=\"ul\" id=\"tsom-visibility__ul_jbb_252_wfc\">\n <li class=\"li\">Interface cards</li>\n <li class=\"li\">Slots and subslots</li>\n <li class=\"li\">Network interfaces</li>\n </ul></li>\n </ol>\n </div>\n </section>\n <section class=\"section\" id=\"tsom-visibility__section_njm_ydk_b2c\"><h2 id=\"d9721e213\" class=\"title sectiontitle\">Telecom Visibility architecture</h2>\n \n <p class=\"p\">Telecom Visibility combines direct and indirect discovery methods:</p>\n <ul class=\"ul\" id=\"tsom-visibility__ul_hmm_352_wfc\">\n <li class=\"li\">Direct Discovery using SNMP/CLI (for example, standalone routers/switches)</li>\n <li class=\"li\">Indirect Discovery using APIs from EMS/NMS/controllers (for example, Nokia Altiplano)</li>\n </ul>\n <p class=\"p\">These feed into the CMDB and TNI, which then support decision-making, automation, and network operations. The following infographic demonstrates the architecture of Telecom Visibility. <img src=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/../images/telecom-discovery-discrepancy-identification-reconciliation.png?_LANG=enus\" class=\"image\" id=\"tsom-visibility__image_zbs_c2k_b2c\" alt=\"Telecom Visibility architecture.\"/></p>\n </section>\n <section class=\"section\" id=\"tsom-visibility__section_pfz_n52_wfc\"><h2 id=\"d9721e240\" class=\"title sectiontitle\">Use Cases</h2>\n \n <div class=\"p\">\n <div class=\"table-wrap\"><table count-columns=\"2\" class=\"table\" id=\"tsom-visibility__table_ayj_452_wfc\"><caption><span class=\"table--title-label\">Table 2. </span><span class=\"title\">Telecom Visibility use cases</span></caption><colgroup><col/><col/></colgroup><thead class=\"thead\">\n <tr class=\"row\">\n <th class=\"entry\" id=\"tsom-visibility__table_ayj_452_wfc__entry__1\">Use Case</th>\n <th class=\"entry\" id=\"tsom-visibility__table_ayj_452_wfc__entry__2\">Outcome</th>\n </tr>\n </thead><tbody class=\"tbody\">\n <tr class=\"row\">\n <td class=\"entry\" headers=\"tsom-visibility__table_ayj_452_wfc__entry__1\">Autonomous Network Operations</td>\n <td class=\"entry\" headers=\"tsom-visibility__table_ayj_452_wfc__entry__2\">Reliable network inventory supports AI/ML-driven automation.</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry\" headers=\"tsom-visibility__table_ayj_452_wfc__entry__1\">Service Fulfillment</td>\n <td class=\"entry\" headers=\"tsom-visibility__table_ayj_452_wfc__entry__2\">Accurate CMDB/TNI ensures order accuracy and rapid provisioning.</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry\" headers=\"tsom-visibility__table_ayj_452_wfc__entry__1\">Service Assurance</td>\n <td class=\"entry\" headers=\"tsom-visibility__table_ayj_452_wfc__entry__2\">Reconciled inventory reduces troubleshooting time and increases uptime.</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry\" headers=\"tsom-visibility__table_ayj_452_wfc__entry__1\">Audit & Compliance</td>\n <td class=\"entry\" headers=\"tsom-visibility__table_ayj_452_wfc__entry__2\">Discovery Admin Workspace and CMDB 360 support audit readiness and traceability.</td>\n </tr>\n </tbody></table></div>\n </div>\n </section>\n <section class=\"section\" id=\"tsom-visibility__section_gfc_jkk_tfc\"><h2 id=\"d9721e313\" class=\"title sectiontitle\">Key personas</h2>\n \n <div class=\"p\">Telecom Visibility is used by: <ul class=\"ul\" id=\"tsom-visibility__ul_hys_kkk_tfc\">\n <li class=\"li\">Network and infrastructure teams: Discover and manage real-time network resource data across vendors and technologies.</li>\n <li class=\"li\">Inventory and fulfillment teams: Maintain an accurate and complete CMDB/TNI to support service fulfillment, order management, and provisioning.</li>\n <li class=\"li\">Platform administrators: Configure plugins, manage discovery sources, validate reconciliation rules, and monitor discovery performance.</li>\n </ul></div>\n </section>\n <section class=\"section\" id=\"tsom-visibility__section_b5x_r52_wfc\"><h2 id=\"d9721e333\" class=\"title sectiontitle\">Monitoring tools</h2>\n \n <p class=\"p\">Discovery Admin Workspace - Central console to:</p>\n <ul class=\"ul\" id=\"tsom-visibility__ul_c5x_r52_wfc\">\n <li class=\"li\">Monitor discovery tasks</li>\n <li class=\"li\">Validate reconciliation processes</li>\n <li class=\"li\">Tune schedules and view diagnostics</li>\n </ul>\n <div class=\"p\">CMDB 360 - Visualize:<ul class=\"ul\" id=\"tsom-visibility__ul_e5x_r52_wfc\">\n <li class=\"li\">Attribute-level update history</li>\n <li class=\"li\">Source attribution</li>\n <li class=\"li\">Reconciliation rules in action</li>\n </ul></div>\n </section>\n <section class=\"section\" id=\"tsom-visibility__section_x2x_bv2_wfc\"><h2 id=\"d9721e368\" class=\"title sectiontitle\">Key benefits</h2>\n \n <div class=\"p\">\n <div class=\"table-wrap\"><table count-columns=\"2\" class=\"table\" id=\"tsom-visibility__table_cw4_cv2_wfc\"><caption><span class=\"table--title-label\">Table 3. </span><span class=\"title\">Key benefits of Telecom Visibility</span></caption><colgroup><col/><col/></colgroup><thead class=\"thead\">\n <tr class=\"row\">\n <th class=\"entry\" id=\"tsom-visibility__table_cw4_cv2_wfc__entry__1\">Feature</th>\n <th class=\"entry\" id=\"tsom-visibility__table_cw4_cv2_wfc__entry__2\">Benefit</th>\n </tr>\n </thead><tbody class=\"tbody\">\n <tr class=\"row\">\n <td class=\"entry\" headers=\"tsom-visibility__table_cw4_cv2_wfc__entry__1\">CLI/SNMP Discovery</td>\n <td class=\"entry\" headers=\"tsom-visibility__table_cw4_cv2_wfc__entry__2\">Expands network coverage without relying on external APIs.</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry\" headers=\"tsom-visibility__table_cw4_cv2_wfc__entry__1\">Nokia Altiplano Integration</td>\n <td class=\"entry\" headers=\"tsom-visibility__table_cw4_cv2_wfc__entry__2\">Supports GPON network discovery across multiple controller instances.</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry\" headers=\"tsom-visibility__table_cw4_cv2_wfc__entry__1\">Discrepancy Reconciliation</td>\n <td class=\"entry\" headers=\"tsom-visibility__table_cw4_cv2_wfc__entry__2\">Keeps inventory clean, actionable, and aligned with real network state.</td>\n </tr>\n </tbody></table></div>\n </div>\n </section>\n </div>\n <nav role=\"navigation\"></nav><nav role=\"navigation\" class=\"tasksNavigation\"></nav><nav role=\"navigation\" class=\"related-links\"><div class=\"col-md-4\"><dt>Related tasks</dt><dd><ul><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/task/configuring-tsom-visibility.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/configuring-tsom-visibility.html\" class=\"link\" title=\"Telecom Visibility provides foundational capabilities that support both Telecom Discovery and Telecom Discrepancy Identification & Reconciliation. It includes shared logic, enhanced CI class models, and Identification and Reconciliation Engine (IRE) updates tailored for telecom network elements.\">Set up Telecom Visibility</a></li></ul></dd></div><div class=\"col-md-4\"><dt>Related topics</dt><dd><ul><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept//csh\" href=\"https://servicenow-be-prod.servicenow.com/csh?topicname=discovery-admin-workspace&version=zurich&pubname=zurich-it-operations-management\" class=\"link\">Discovery Admin Workspace</a></li></ul></dd></div></nav>\n</article></main></body></article>",
"topic_language": "enus",
"views": 0,
"your_rating": null
} | # Telecom Visibility
Telecom Visibility extends the discovery and reconciliation capabilities of ITOM Visibility to meet the specific needs of telecom service providers. It enables accurate, telecom-aware network inventory by discovering real-time
network data, reconciling mismatches, and maintaining a consistent telecom model in your CMDB and TNI (Telecommunications Network Inventory).
Discover physical and logical network components across telecom domains, reconcile discrepancies between discovery and inventory data, and maintain a telecom-specific CMDB structure to support advanced automation and assurance use
cases.
## Telecom Visibility overview
Telecom Visibility is a unified solution for discovering and managing telecom network resources. It leverages proven discovery technologies such as Horizontal Discovery, Telecommunications Discovery Patterns, and Service Graph
Connectors (SGC) to bring network data from various systems (for example, CLI/SNMP-based standalone devices or API-driven EMS/NMS/controllers) into your CMDB.
Telecom Visibility helps communication service providers (CSPs) and telecom operators:
* Discover and maintain telecom-specific network inventory
* Reconcile mismatches between planned/design inventory and actual network state
* Support Autonomous Network Operations (ANO), service fulfillment, and assurance workflows
## Key Capabilities
Table 1. Key capabilities of TSOM
| Capability | Description |
| --- | --- |
| Telecom Discovery with Patterns | Discover standalone network functions (xNFs) such as routers and switches using SNMP and CLI protocols via predefined Telecom Discovery Patterns. |
| Service Graph Connector Integration | Bring inventory and configuration data from external EMS/NMS/controllers into CMDB using northbound APIs. |
| Discrepancy Identification & Reconciliation | Detect and resolve mismatches between inventoried and discovered data (for example, missing CIs, model mismatches, stale entries). |
| Telecom-Centric Data Modeling | Maintain structured and hierarchical telecom data including interface cards, slots, subslots, VLANs, and ports. |
| CMDB Integration | Use CMDB 360 and Discovery Admin Workspace to monitor discovery sources, attribute changes, and reconciliation outcomes. |
## Applications and Plugins
1. Telecommunications Horizontal Discovery Patterns: Discovers telecom devices (xNFs) such as routers and switches using SNMP/CLI. Enables accurate inventory updates by scanning live network infrastructure. Supports vendor-specific
patterns including:
* Cisco (ASR1K, 7613, Nexus 9000, Nexus 3548)
* Juniper (MX80, MX104, MX240, MX460)
2. Service Graph Connectors (SGCs) for TSOM: Prebuilt integrations with EMS/NMS/controllers to import inventory data via APIs. Supports:
* Scheduled or on-demand discovery
* Multi-instance configurations
* Integration with systems like Nokia Altiplano (GPON networks)
3. Telecom Visibility Plugin: Provides shared logic and foundational components for both discovery and discrepancy reconciliation. Ensures:
* Consistent behavior across TSOM workflows
* Reusable components for reconciliation and remediation
4. CMDB CI Class Models for Telecom (Required version: 1.69.0): Extends the CMDB to include telecom-specific classes and relationships, including:
* Interface cards
* Slots and subslots
* Network interfaces
## Telecom Visibility architecture
Telecom Visibility combines direct and indirect discovery methods:
* Direct Discovery using SNMP/CLI (for example, standalone routers/switches)
* Indirect Discovery using APIs from EMS/NMS/controllers (for example, Nokia Altiplano)
These feed into the CMDB and TNI, which then support decision-making, automation, and network operations. The following infographic demonstrates the architecture of Telecom Visibility.
## Use Cases
Table 2. Telecom Visibility use cases
| Use Case | Outcome |
| --- | --- |
| Autonomous Network Operations | Reliable network inventory supports AI/ML-driven automation. |
| Service Fulfillment | Accurate CMDB/TNI ensures order accuracy and rapid provisioning. |
| Service Assurance | Reconciled inventory reduces troubleshooting time and increases uptime. |
| Audit & Compliance | Discovery Admin Workspace and CMDB 360 support audit readiness and traceability. |
## Key personas
Telecom Visibility is used by:
* Network and infrastructure teams: Discover and manage real-time network resource data across vendors and technologies.
* Inventory and fulfillment teams: Maintain an accurate and complete CMDB/TNI to support service fulfillment, order management, and provisioning.
* Platform administrators: Configure plugins, manage discovery sources, validate reconciliation rules, and monitor discovery performance.
## Monitoring tools
Discovery Admin Workspace - Central console to:
* Monitor discovery tasks
* Validate reconciliation processes
* Tune schedules and view diagnostics
CMDB 360 - Visualize:
* Attribute-level update history
* Source attribution
* Reconciliation rules in action
## Key benefits
Table 3. Key benefits of Telecom Visibility
| Feature | Benefit |
| --- | --- |
| CLI/SNMP Discovery | Expands network coverage without relying on external APIs. |
| Nokia Altiplano Integration | Supports GPON network discovery across multiple controller instances. |
| Discrepancy Reconciliation | Keeps inventory clean, actionable, and aligned with real network state. |
| ---
title: Telecom Visibility
description: Telecom Visibility extends the discovery and reconciliation capabilities
of ITOM Visibility to meet the specific needs of telecom service providers. It enables
accurate, telecom-aware network inventory by discovering real-time network data,
reconciling mismatches, and maintaining a consistent telecom model in
keywords: []
breadcrumbs:
- Telecommunications Service Operations Management
- Exploring Telecommunications Service Operations Management
---
# Telecom Visibility
Telecom Visibility extends the discovery and reconciliation capabilities of ITOM Visibility to meet the specific needs of telecom service providers. It enables accurate, telecom-aware network inventory by discovering real-time
network data, reconciling mismatches, and maintaining a consistent telecom model in your CMDB and TNI (Telecommunications Network Inventory).
Discover physical and logical network components across telecom domains, reconcile discrepancies between discovery and inventory data, and maintain a telecom-specific CMDB structure to support advanced automation and assurance use
cases.
## Telecom Visibility overview
Telecom Visibility is a unified solution for discovering and managing telecom network resources. It leverages proven discovery technologies such as Horizontal Discovery, Telecommunications Discovery Patterns, and Service Graph
Connectors (SGC) to bring network data from various systems (for example, CLI/SNMP-based standalone devices or API-driven EMS/NMS/controllers) into your CMDB.
Telecom Visibility helps communication service providers (CSPs) and telecom operators:
* Discover and maintain telecom-specific network inventory
* Reconcile mismatches between planned/design inventory and actual network state
* Support Autonomous Network Operations (ANO), service fulfillment, and assurance workflows
## Key Capabilities
Table 1. Key capabilities of TSOM
| Capability | Description |
| --- | --- |
| Telecom Discovery with Patterns | Discover standalone network functions (xNFs) such as routers and switches using SNMP and CLI protocols via predefined Telecom Discovery Patterns. |
| Service Graph Connector Integration | Bring inventory and configuration data from external EMS/NMS/controllers into CMDB using northbound APIs. |
| Discrepancy Identification & Reconciliation | Detect and resolve mismatches between inventoried and discovered data (for example, missing CIs, model mismatches, stale entries). |
| Telecom-Centric Data Modeling | Maintain structured and hierarchical telecom data including interface cards, slots, subslots, VLANs, and ports. |
| CMDB Integration | Use CMDB 360 and Discovery Admin Workspace to monitor discovery sources, attribute changes, and reconciliation outcomes. |
## Applications and Plugins
1. Telecommunications Horizontal Discovery Patterns: Discovers telecom devices (xNFs) such as routers and switches using SNMP/CLI. Enables accurate inventory updates by scanning live network infrastructure. Supports vendor-specific
patterns including:
* Cisco (ASR1K, 7613, Nexus 9000, Nexus 3548)
* Juniper (MX80, MX104, MX240, MX460)
2. Service Graph Connectors (SGCs) for TSOM: Prebuilt integrations with EMS/NMS/controllers to import inventory data via APIs. Supports:
* Scheduled or on-demand discovery
* Multi-instance configurations
* Integration with systems like Nokia Altiplano (GPON networks)
3. Telecom Visibility Plugin: Provides shared logic and foundational components for both discovery and discrepancy reconciliation. Ensures:
* Consistent behavior across TSOM workflows
* Reusable components for reconciliation and remediation
4. CMDB CI Class Models for Telecom (Required version: 1.69.0): Extends the CMDB to include telecom-specific classes and relationships, including:
* Interface cards
* Slots and subslots
* Network interfaces
## Telecom Visibility architecture
Telecom Visibility combines direct and indirect discovery methods:
* Direct Discovery using SNMP/CLI (for example, standalone routers/switches)
* Indirect Discovery using APIs from EMS/NMS/controllers (for example, Nokia Altiplano)
These feed into the CMDB and TNI, which then support decision-making, automation, and network operations. The following infographic demonstrates the architecture of Telecom Visibility.
## Use Cases
Table 2. Telecom Visibility use cases
| Use Case | Outcome |
| --- | --- |
| Autonomous Network Operations | Reliable network inventory supports AI/ML-driven automation. |
| Service Fulfillment | Accurate CMDB/TNI ensures order accuracy and rapid provisioning. |
| Service Assurance | Reconciled inventory reduces troubleshooting time and increases uptime. |
| Audit & Compliance | Discovery Admin Workspace and CMDB 360 support audit readiness and traceability. |
## Key personas
Telecom Visibility is used by:
* Network and infrastructure teams: Discover and manage real-time network resource data across vendors and technologies.
* Inventory and fulfillment teams: Maintain an accurate and complete CMDB/TNI to support service fulfillment, order management, and provisioning.
* Platform administrators: Configure plugins, manage discovery sources, validate reconciliation rules, and monitor discovery performance.
## Monitoring tools
Discovery Admin Workspace - Central console to:
* Monitor discovery tasks
* Validate reconciliation processes
* Tune schedules and view diagnostics
CMDB 360 - Visualize:
* Attribute-level update history
* Source attribution
* Reconciliation rules in action
## Key benefits
Table 3. Key benefits of Telecom Visibility
| Feature | Benefit |
| --- | --- |
| CLI/SNMP Discovery | Expands network coverage without relying on external APIs. |
| Nokia Altiplano Integration | Supports GPON network discovery across multiple controller instances. |
| Discrepancy Reconciliation | Keeps inventory clean, actionable, and aligned with real network state. |
|
https://www.servicenow.com/docs/en-US/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/using-telecom-discovery-patterns.html | https://servicenow-be-prod.servicenow.com/api/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/using-telecom-discovery-patterns.html | 2025-08-02 | daily | 0.5 | 268.xml | en-US | zurich-telecom-service-ops | product/tmt-telecom-service-operations-mgt/concept/using-telecom-discovery-patterns.html | zurich | Using Telecom Discovery patterns | Use Telecom Discovery patterns to identify and classify network functions (xNFs) from vendor devices such as routers, Cisco, and Juniper. Leverage pattern-based discovery to map telecom resources into the CMDB. | [] | [
"Telecommunications Service Operations Management",
"Using Telecommunications Service Operations Management"
] | <article class="hascomments" data-page="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/using-telecom-discovery-patterns.html" id="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/using-telecom-discovery-patterns.html"><body id="using-telecom-discovery-patterns"><main role="main"><article role="article" class="dita" id="using-telecom-discovery-patterns" aria-labelledby="title_using-telecom-discovery-patterns">
<h1 class="title topictitle1" id="title_using-telecom-discovery-patterns">Using Telecom Discovery patterns</h1>
<div class="body conbody"><p class="shortdesc">Use Telecom Discovery patterns to identify and classify network functions (xNFs) from vendor devices such as routers, Cisco, and Juniper. Leverage pattern-based discovery to map telecom resources into the CMDB.</p></div>
<nav role="navigation"><dt class="ullinks"></dt><dd class="ullinks"><ul class="ullinks"><li class="link ulchildlink"><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/task/classifying-xnfs-pattern-tsom-visibility.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/classifying-xnfs-pattern-tsom-visibility.html">Classifying xNFs for Telecom Router Pattern</a><p class="shortdesc">To access a full list of OIDs that will be classified.</p></li><li class="link ulchildlink"><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/task/classifying-xnfs-telecom-cisco.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/classifying-xnfs-telecom-cisco.html">Classifying xNFs for Telecom Cisco 7613 Router Pattern</a><p class="shortdesc">To access a full list of OIDs that will be classified.</p></li><li class="link ulchildlink"><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/task/classifying-xnfs-juniper-router-pattern.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/classifying-xnfs-juniper-router-pattern.html">Classifying xNFs for Telecom Juniper MX SSH Router Pattern</a><p class="shortdesc">To access a full list of OIDs that will be classified.</p></li><li class="link ulchildlink"><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/task/classifying-xnfs-cisco-switch-pattern.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/classifying-xnfs-cisco-switch-pattern.html">Classifying xNFs for Telecom Cisco Switch Pattern</a><p class="shortdesc">To access a full list of OIDs that will be classified.</p></li><li class="link ulchildlink"><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/task/classifying-xnfs-pattern-switch-pattern.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/classifying-xnfs-pattern-switch-pattern.html">Classifying xNFs for Telecom Switch Pattern</a><p class="shortdesc">To access a full list of OIDs that will be classified.</p></li></ul></dd></nav><nav role="navigation" class="tasksNavigation"></nav><nav role="navigation" class="related-links"></nav></article></main></body></article> | {
"attachments": {
"all_attachments": null,
"topic_attachments": []
},
"available_languages": [
"enus"
],
"breadcrumbs": [
{
"title": "Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html"
},
{
"title": "Using Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/using-tsom.html"
}
],
"breadcrumbs_html": "<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops\">Zurich Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html\">Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/using-tsom.html\">Using Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<span class=\"active\">Using Telecom Discovery patterns</span>",
"bundle_id": "zurich-telecom-service-ops",
"bundle_key": 2733,
"bundle_landing_page": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html",
"bundle_subtitle": null,
"bundle_title": "Zurich Telecommunications Service Operations Management",
"canonical_link": null,
"dates": {
"Added on": "2025-08-02T00:48:08.794016Z",
"Created on": "2025-07-03T00:00:00Z",
"Initial upload": "2025-07-30T22:24:33.519043Z",
"Updated on": "2025-07-31T00:00:00Z"
},
"dislike_url": "https://servicenow-be-prod.servicenow.com/dislike/55686951",
"dislikes": 0,
"es_archived_content": false,
"is_in_fav": false,
"is_liked": null,
"is_watched": false,
"keywords": [
" zurich zurich"
],
"labels": [
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "zurich",
"navtitle": "Zurich",
"outputclasses": [],
"subjectHeadId": "versions",
"subjectheadNavtitle": "Versions",
"visibility": "show-facet"
},
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "tsom",
"navtitle": "Telecommunications Service Operations Management",
"outputclasses": [],
"subjectHeadId": "products",
"subjectheadNavtitle": "Products",
"visibility": "show-facet"
}
],
"labels_text": "Versions > Zurich; Products > CRM and Industry Products > Telecommunications Media and Technology Assurance > Telecommunications Service Operations Management",
"like_url": "https://servicenow-be-prod.servicenow.com/like/55686951",
"likes": 0,
"metadata": {
"AI Search": null,
"AI Search Assist": null,
"Application Insights": null,
"Capabilities": null,
"Code Signing": null,
"Contextual Search": null,
"DC.contributor": null,
"DC.coverage": null,
"DC.creator": "ServiceNow",
"DC.date.created": "2025-07-03T20:46:29+05:30",
"DC.date.modified": "2025-07-31",
"DC.format": "HTML5",
"DC.identifier": "using-telecom-discovery-patterns",
"DC.language": null,
"DC.relation": "../../../product/tmt-telecom-service-operations-mgt/concept/using-tsom.html",
"DC.rights.owner": "(C) Copyright 2025",
"DC.subject": null,
"DC.type": "concept",
"Data Discovery": null,
"Data Policy": null,
"Data Privacy": null,
"Discovery": null,
"External Content for AI Search": null,
"Field Administration": null,
"Field Normalization": null,
"Key Management Framework": null,
"Localization Framework": null,
"Now Platform": null,
"PlatSec": null,
"Platform": null,
"Platform Administration": null,
"Platform Performance": null,
"Platform Privacy": null,
"Proactive Triggers": null,
"Process Optimization": null,
"RN doc editing record number": null,
"Search Administration": null,
"Secrets Management": null,
"ServiceNow AI Platform": null,
"State Model": null,
"Subscription Management": null,
"Task Communications Management": null,
"Timeline Visualizations": null,
"User Administration": null,
"User Experience Analytics": null,
"Zing": null,
"ai-now-assist": null,
"app-name": null,
"app_route": null,
"azureapimanagemen": null,
"change-completed": null,
"change-item": null,
"change-request-id": null,
"change-request-reference": null,
"com.glide.embedded_help.category": null,
"component": null,
"copyright": "(C) Copyright 2025",
"crossroads": null,
"data": null,
"description": "Use Telecom Discovery patterns to identify and classify network functions (xNFs) from vendor devices such as routers, Cisco, and Juniper. Leverage pattern-based discovery to map telecom resources into the CMDB.",
"dominant_bundle": null,
"erp-canvas-video": null,
"fsm-mobile": null,
"fsm-route": null,
"fsm-sched-opt": null,
"fsm-wrk-order": null,
"genai-round-7": null,
"generator": "DITA-OT",
"glossPartOfSpeech": null,
"glossStatus": null,
"guided setup": null,
"guided tours": null,
"keywords": null,
"min-toc": null,
"mini": null,
"mini-to truec": null,
"mini-toc": null,
"mini_toc": null,
"minitoc": null,
"modification": null,
"now-assist-app-gen-video": null,
"order": null,
"page-type": null,
"page-type ": null,
"prodname": null,
"product": null,
"product_name": null,
"release": null,
"resourceID": null,
"roles": null,
"route_page": null,
"route_params_listId": null,
"route_params_table": null,
"route_params_type": null,
"route_type": null,
"setconfigurationproperties": null,
"topic": null,
"translation-type": "source",
"version": null,
"workflow": "Customer and Industry",
"workplace-srvc-delvry-ditamap": null
},
"page_id": "product/tmt-telecom-service-operations-mgt/concept/using-telecom-discovery-patterns.html",
"page_key": 55686951,
"preprocessed_PDF": "https://downloads.docs.servicenow.com/pdf/enus/servicenow-zurich-telecom-service-ops-enus.pdf",
"rating": null,
"read_time_data": {
"char_count": 737,
"img_count": 0,
"read_time": 1,
"video_links": [
""
],
"word_count": 121
},
"related_links": [],
"search_title": null,
"title": "Using Telecom Discovery patterns",
"topic_cluster": {
"clustered_by": {
"enabled": true,
"primary_key": "versions",
"primary_sort": "top-down",
"type": "subjecthead"
},
"clustered_labels": [
"versions"
],
"clustered_topics": [],
"clustering_title": "Zurich"
},
"topic_html": "<article class=\"hascomments\" data-page=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/using-telecom-discovery-patterns.html\" id=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/using-telecom-discovery-patterns.html\"><body id=\"using-telecom-discovery-patterns\"><main role=\"main\"><article role=\"article\" class=\"dita\" id=\"using-telecom-discovery-patterns\" aria-labelledby=\"title_using-telecom-discovery-patterns\">\n <h1 class=\"title topictitle1\" id=\"title_using-telecom-discovery-patterns\">Using Telecom Discovery patterns</h1>\n \n \n <div class=\"body conbody\"><p class=\"shortdesc\">Use Telecom Discovery patterns to identify and classify network functions (xNFs) from vendor devices such as routers, Cisco, and Juniper. Leverage pattern-based discovery to map telecom resources into the CMDB.</p></div>\n<nav role=\"navigation\"><dt class=\"ullinks\"></dt><dd class=\"ullinks\"><ul class=\"ullinks\"><li class=\"link ulchildlink\"><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/task/classifying-xnfs-pattern-tsom-visibility.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/classifying-xnfs-pattern-tsom-visibility.html\">Classifying xNFs for Telecom Router Pattern</a><p class=\"shortdesc\">To access a full list of OIDs that will be classified.</p></li><li class=\"link ulchildlink\"><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/task/classifying-xnfs-telecom-cisco.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/classifying-xnfs-telecom-cisco.html\">Classifying xNFs for Telecom Cisco 7613 Router Pattern</a><p class=\"shortdesc\">To access a full list of OIDs that will be classified.</p></li><li class=\"link ulchildlink\"><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/task/classifying-xnfs-juniper-router-pattern.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/classifying-xnfs-juniper-router-pattern.html\">Classifying xNFs for Telecom Juniper MX SSH Router Pattern</a><p class=\"shortdesc\">To access a full list of OIDs that will be classified.</p></li><li class=\"link ulchildlink\"><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/task/classifying-xnfs-cisco-switch-pattern.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/classifying-xnfs-cisco-switch-pattern.html\">Classifying xNFs for Telecom Cisco Switch Pattern</a><p class=\"shortdesc\">To access a full list of OIDs that will be classified.</p></li><li class=\"link ulchildlink\"><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/task/classifying-xnfs-pattern-switch-pattern.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/classifying-xnfs-pattern-switch-pattern.html\">Classifying xNFs for Telecom Switch Pattern</a><p class=\"shortdesc\">To access a full list of OIDs that will be classified.</p></li></ul></dd></nav><nav role=\"navigation\" class=\"tasksNavigation\"></nav><nav role=\"navigation\" class=\"related-links\"></nav></article></main></body></article>",
"topic_language": "enus",
"views": 0,
"your_rating": null
} | # Using Telecom Discovery patterns
Use Telecom Discovery patterns to identify and classify network functions (xNFs) from vendor devices such as routers, Cisco, and Juniper. Leverage pattern-based discovery to map telecom resources into the CMDB.
| ---
title: Using Telecom Discovery patterns
description: Use Telecom Discovery patterns to identify and classify network functions
(xNFs) from vendor devices such as routers, Cisco, and Juniper. Leverage pattern-based
discovery to map telecom resources into the CMDB.
keywords: []
breadcrumbs:
- Telecommunications Service Operations Management
- Using Telecommunications Service Operations Management
---
# Using Telecom Discovery patterns
Use Telecom Discovery patterns to identify and classify network functions (xNFs) from vendor devices such as routers, Cisco, and Juniper. Leverage pattern-based discovery to map telecom resources into the CMDB.
|
https://www.servicenow.com/docs/en-US/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/using-tsom.html | https://servicenow-be-prod.servicenow.com/api/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/using-tsom.html | 2025-08-02 | daily | 0.5 | 268.xml | en-US | zurich-telecom-service-ops | product/tmt-telecom-service-operations-mgt/concept/using-tsom.html | zurich | Using Telecommunications Service Operations Management | Leverage 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. | [] | [
"Telecommunications Service Operations Management"
] | <article class="hascomments" data-page="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/using-tsom.html" id="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/using-tsom.html"><body id="using-tsom"><main role="main"><article role="article" class="dita" id="using-tsom" aria-labelledby="title_using-tsom">
<h1 class="title topictitle1" id="title_using-tsom">Using <span class="ph">Telecommunications Service Operations Management</span></h1>
<div class="body conbody"><p class="shortdesc">Leverage <span class="ph">Telecommunications Service Operations Management</span> (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.</p>
<section class="section" id="using-tsom__section_sn4_pfc_1gc"><h2 id="d11374e47" class="title sectiontitle">Common operational tasks of TSOM</h2>
<p class="p">Once TSOM is configured, you can use its capabilities to:</p>
<ul class="ul" id="using-tsom__ul_sf3_qfc_1gc">
<li class="li">Run Telecom Discrepancy audits: Identify inconsistencies in network relationships and configurations by running certification audits based on discovered data and reconciliation rules.</li>
<li class="li">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.</li>
<li class="li">Use Telecom Discovery Patterns: Apply Telecom Discovery Patterns to accurately discover and populate telecom-specific Configuration Items (CIs) and their relationships.</li>
<li class="li">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.</li>
</ul>
<p class="p">These tasks help ensure that your telecom network is continuously synchronized, accurate, and operationally visible within ServiceNow.</p>
</section>
</div>
<nav role="navigation"><dt class="ullinks"></dt><dd class="ullinks"><ul class="ullinks"><li class="link ulchildlink"><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/concept/using-telecom-discovery-patterns.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/using-telecom-discovery-patterns.html">Using Telecom Discovery patterns</a><p class="shortdesc">Use Telecom Discovery patterns to identify and classify network functions (xNFs) from vendor devices such as routers, Cisco, and Juniper. Leverage pattern-based discovery to map telecom resources into the CMDB.</p></li><li class="link ulchildlink"><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/task/run-and-verify-import-for-nokia-altiplano-service-graph-connector.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/run-and-verify-import-for-nokia-altiplano-service-graph-connector.html">Run and verify import for Nokia Altiplano Service Graph Connector</a><p class="shortdesc">Manually execute a configured import schedule for the Nokia Altiplano Service Graph Connector. You can also execute the import to validate the connector setup, run ad-hoc imports, or test newly configured connection aliases. This task helps ensure that data from Altiplano is successfully imported or updated in the CMDB.</p></li><li class="link ulchildlink"><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/concept/validating-json-payloads-using-tsom-schema-validator.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/validating-json-payloads-using-tsom-schema-validator.html">Validating JSON payloads using TSOM Schema Validator</a><p class="shortdesc">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.</p></li><li class="link ulchildlink"><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/task/run-audits.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/run-audits.html">Run Telecom Discrepancy audit</a><p class="shortdesc">The Telecom Discrepancy Audit validates the integrity of configuration items (CIs) and relationships across your telecom inventory using the CMDB Compliance framework. </p></li><li class="link ulchildlink"><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/task/use-attribute-value-discrepancy-in-cmdb-360.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/use-attribute-value-discrepancy-in-cmdb-360.html">Generate reports for attribute value discrepancies</a><p class="shortdesc">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.</p></li></ul></dd></nav><nav role="navigation" class="tasksNavigation"></nav><nav role="navigation" class="related-links"></nav></article></main></body></article> | {
"attachments": {
"all_attachments": null,
"topic_attachments": []
},
"available_languages": [
"enus"
],
"breadcrumbs": [
{
"title": "Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html"
}
],
"breadcrumbs_html": "<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops\">Zurich Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html\">Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<span class=\"active\">Using Telecommunications Service Operations Management</span>",
"bundle_id": "zurich-telecom-service-ops",
"bundle_key": 2733,
"bundle_landing_page": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html",
"bundle_subtitle": null,
"bundle_title": "Zurich Telecommunications Service Operations Management",
"canonical_link": null,
"dates": {
"Added on": "2025-08-02T00:48:08.794016Z",
"Created on": "2025-06-24T00:00:00Z",
"Initial upload": "2025-07-30T22:24:33.519043Z",
"Updated on": "2025-07-31T00:00:00Z"
},
"dislike_url": "https://servicenow-be-prod.servicenow.com/dislike/55686952",
"dislikes": 0,
"es_archived_content": false,
"is_in_fav": false,
"is_liked": null,
"is_watched": false,
"keywords": [
" zurich zurich"
],
"labels": [
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "zurich",
"navtitle": "Zurich",
"outputclasses": [],
"subjectHeadId": "versions",
"subjectheadNavtitle": "Versions",
"visibility": "show-facet"
},
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "tsom",
"navtitle": "Telecommunications Service Operations Management",
"outputclasses": [],
"subjectHeadId": "products",
"subjectheadNavtitle": "Products",
"visibility": "show-facet"
}
],
"labels_text": "Versions > Zurich; Products > CRM and Industry Products > Telecommunications Media and Technology Assurance > Telecommunications Service Operations Management",
"like_url": "https://servicenow-be-prod.servicenow.com/like/55686952",
"likes": 0,
"metadata": {
"AI Search": null,
"AI Search Assist": null,
"Application Insights": null,
"Capabilities": null,
"Code Signing": null,
"Contextual Search": null,
"DC.contributor": null,
"DC.coverage": null,
"DC.creator": "ServiceNow",
"DC.date.created": "2025-06-24T12:47:30+05:30",
"DC.date.modified": "2025-07-31",
"DC.format": "HTML5",
"DC.identifier": "using-tsom",
"DC.language": null,
"DC.relation": "../../../product/tmt-telecom-service-operations-mgt/concept/using-telecom-discovery-patterns.html",
"DC.rights.owner": "(C) Copyright 2025",
"DC.subject": null,
"DC.type": "concept",
"Data Discovery": null,
"Data Policy": null,
"Data Privacy": null,
"Discovery": null,
"External Content for AI Search": null,
"Field Administration": null,
"Field Normalization": null,
"Key Management Framework": null,
"Localization Framework": null,
"Now Platform": null,
"PlatSec": null,
"Platform": null,
"Platform Administration": null,
"Platform Performance": null,
"Platform Privacy": null,
"Proactive Triggers": null,
"Process Optimization": null,
"RN doc editing record number": null,
"Search Administration": null,
"Secrets Management": null,
"ServiceNow AI Platform": null,
"State Model": null,
"Subscription Management": null,
"Task Communications Management": null,
"Timeline Visualizations": null,
"User Administration": null,
"User Experience Analytics": null,
"Zing": null,
"ai-now-assist": null,
"app-name": null,
"app_route": null,
"azureapimanagemen": null,
"change-completed": null,
"change-item": null,
"change-request-id": null,
"change-request-reference": null,
"com.glide.embedded_help.category": null,
"component": null,
"copyright": "(C) Copyright 2025",
"crossroads": null,
"data": null,
"description": "Leverage 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.",
"dominant_bundle": null,
"erp-canvas-video": null,
"fsm-mobile": null,
"fsm-route": null,
"fsm-sched-opt": null,
"fsm-wrk-order": null,
"genai-round-7": null,
"generator": "DITA-OT",
"glossPartOfSpeech": null,
"glossStatus": null,
"guided setup": null,
"guided tours": null,
"keywords": null,
"min-toc": null,
"mini": null,
"mini-to truec": null,
"mini-toc": "yes",
"mini_toc": null,
"minitoc": null,
"modification": null,
"now-assist-app-gen-video": null,
"order": null,
"page-type": null,
"page-type ": null,
"prodname": null,
"product": null,
"product_name": null,
"release": null,
"resourceID": null,
"roles": null,
"route_page": null,
"route_params_listId": null,
"route_params_table": null,
"route_params_type": null,
"route_type": null,
"setconfigurationproperties": null,
"topic": null,
"translation-type": "source",
"version": null,
"workflow": "Customer and Industry",
"workplace-srvc-delvry-ditamap": null
},
"page_id": "product/tmt-telecom-service-operations-mgt/concept/using-tsom.html",
"page_key": 55686952,
"preprocessed_PDF": "https://downloads.docs.servicenow.com/pdf/enus/servicenow-zurich-telecom-service-ops-enus.pdf",
"rating": null,
"read_time_data": {
"char_count": 2671,
"img_count": 0,
"read_time": 2,
"video_links": [
""
],
"word_count": 366
},
"related_links": [],
"search_title": null,
"title": "Using Telecommunications Service Operations Management",
"topic_cluster": {
"clustered_by": {
"enabled": true,
"primary_key": "versions",
"primary_sort": "top-down",
"type": "subjecthead"
},
"clustered_labels": [
"versions"
],
"clustered_topics": [],
"clustering_title": "Zurich"
},
"topic_html": "<article class=\"hascomments\" data-page=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/using-tsom.html\" id=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/using-tsom.html\"><body id=\"using-tsom\"><main role=\"main\"><article role=\"article\" class=\"dita\" id=\"using-tsom\" aria-labelledby=\"title_using-tsom\">\n <h1 class=\"title topictitle1\" id=\"title_using-tsom\">Using <span class=\"ph\">Telecommunications Service Operations Management</span></h1>\n \n \n <div class=\"body conbody\"><p class=\"shortdesc\">Leverage <span class=\"ph\">Telecommunications Service Operations Management</span> (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\n accurate telecom-aware CMDB and act on real-time network insights.</p>\n <section class=\"section\" id=\"using-tsom__section_sn4_pfc_1gc\"><h2 id=\"d11374e47\" class=\"title sectiontitle\">Common operational tasks of TSOM</h2>\n \n <p class=\"p\">Once TSOM is configured, you can use its capabilities to:</p>\n <ul class=\"ul\" id=\"using-tsom__ul_sf3_qfc_1gc\">\n <li class=\"li\">Run Telecom Discrepancy audits: Identify inconsistencies in network relationships and configurations by running certification audits based on discovered data and reconciliation rules.</li>\n <li class=\"li\">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.</li>\n <li class=\"li\">Use Telecom Discovery Patterns: Apply Telecom Discovery Patterns to accurately discover and populate telecom-specific Configuration Items (CIs) and their relationships.</li>\n <li class=\"li\">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\n correct CI classes.</li>\n </ul>\n <p class=\"p\">These tasks help ensure that your telecom network is continuously synchronized, accurate, and operationally visible within ServiceNow.</p>\n </section>\n </div>\n<nav role=\"navigation\"><dt class=\"ullinks\"></dt><dd class=\"ullinks\"><ul class=\"ullinks\"><li class=\"link ulchildlink\"><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept/using-telecom-discovery-patterns.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/using-telecom-discovery-patterns.html\">Using Telecom Discovery patterns</a><p class=\"shortdesc\">Use Telecom Discovery patterns to identify and classify network functions (xNFs) from vendor devices such as routers, Cisco, and Juniper. Leverage pattern-based discovery to map telecom resources into the CMDB.</p></li><li class=\"link ulchildlink\"><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/task/run-and-verify-import-for-nokia-altiplano-service-graph-connector.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/run-and-verify-import-for-nokia-altiplano-service-graph-connector.html\">Run and verify import for Nokia Altiplano Service Graph Connector</a><p class=\"shortdesc\">Manually execute a configured import schedule for the Nokia Altiplano Service Graph Connector. You can also execute the import to validate the connector setup, run ad-hoc imports, or test newly configured connection aliases. This task helps ensure that data from Altiplano is successfully imported or updated in the CMDB.</p></li><li class=\"link ulchildlink\"><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept/validating-json-payloads-using-tsom-schema-validator.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/validating-json-payloads-using-tsom-schema-validator.html\">Validating JSON payloads using TSOM Schema Validator</a><p class=\"shortdesc\">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.</p></li><li class=\"link ulchildlink\"><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/task/run-audits.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/run-audits.html\">Run Telecom Discrepancy audit</a><p class=\"shortdesc\">The Telecom Discrepancy Audit validates the integrity of configuration items (CIs) and relationships across your telecom inventory using the CMDB Compliance framework. </p></li><li class=\"link ulchildlink\"><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/task/use-attribute-value-discrepancy-in-cmdb-360.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/use-attribute-value-discrepancy-in-cmdb-360.html\">Generate reports for attribute value discrepancies</a><p class=\"shortdesc\">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.</p></li></ul></dd></nav><nav role=\"navigation\" class=\"tasksNavigation\"></nav><nav role=\"navigation\" class=\"related-links\"></nav></article></main></body></article>",
"topic_language": "enus",
"views": 0,
"your_rating": null
} | # Using Telecommunications Service Operations Management
Leverage 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 ensure that your telecom network is continuously synchronized, accurate, and operationally visible within ServiceNow.
| ---
title: Using Telecommunications Service Operations Management
description: Leverage 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.
keywords: []
breadcrumbs:
- Telecommunications Service Operations Management
---
# Using Telecommunications Service Operations Management
Leverage 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 ensure that your telecom network is continuously synchronized, accurate, and operationally visible within ServiceNow.
|
https://www.servicenow.com/docs/en-US/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/validating-json-payloads-using-tsom-schema-validator.html | https://servicenow-be-prod.servicenow.com/api/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/validating-json-payloads-using-tsom-schema-validator.html | 2025-08-02 | daily | 0.5 | 268.xml | en-US | zurich-telecom-service-ops | product/tmt-telecom-service-operations-mgt/concept/validating-json-payloads-using-tsom-schema-validator.html | zurich | 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. | [] | [
"Telecommunications Service Operations Management",
"Using Telecommunications Service Operations Management"
] | <article class="hascomments" data-page="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/validating-json-payloads-using-tsom-schema-validator.html" id="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/validating-json-payloads-using-tsom-schema-validator.html"><body id="validating-json-payloads-using-tsom-schema-validator"><main role="main"><article role="article" class="dita" id="validating-json-payloads-using-tsom-schema-validator" aria-labelledby="title_validating-json-payloads-using-tsom-schema-validator">
<h1 class="title topictitle1" id="title_validating-json-payloads-using-tsom-schema-validator">Validating JSON payloads using TSOM Schema Validator</h1>
<div class="body conbody"><p class="shortdesc">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.</p>
<p class="p">Use this validator to check whether your JSON payloads conform to the expected schema for telco objects like Devices, Logical Connections, and Topologies before creating import sets. This pre-validation step helps to prevent schema
mismatch errors and improves debugging.</p>
<section class="section" id="validating-json-payloads-using-tsom-schema-validator__section_ukd_rk2_bgc"><h2 id="d3079e45" class="title sectiontitle">Supported schema types</h2>
<div class="p">The validator supports multiple schema types for different telco data structures:<ul class="ul" id="validating-json-payloads-using-tsom-schema-validator__ul_w31_nl2_bgc">
<li class="li">Logical Composites - Representing groupings of components: Equipment, PDUs, Fan Shelves</li>
<li class="li">Devices - Equipment and their contained components</li>
<li class="li">Logical Connections - Connections between network interfaces</li>
<li class="li">Port Relations - Relationships between network interfaces: physical, logical, lags</li>
<li class="li">Logical Connection Relations - Relationships between logical connections</li>
<li class="li">Topologies - Network topology</li>
</ul></div>
</section>
<section class="section" id="validating-json-payloads-using-tsom-schema-validator__section_ud3_sl2_bgc"><h2 id="d3079e75" class="title sectiontitle">Class structure</h2>
<div class="p">
<pre class="prettyprint language-plaintext"><code class="pre codeblock language-plaintext">let TsomSchemaValidator = Class.create();
TsomSchemaValidator.prototype = {
initialize: function() {
this.schemas = new TsomGenericSchema();
},
isValidJson: function(payload) {
// Validation logic that determines if the JSON structure is valid
// Returns boolean (true/false)
},
checkJsonValidation: function(payload) {
// Validation logic that determines if the JSON structure is valid
// Returns a JSON object containing errors (if exist)
},
type: 'TsomSchemaValidator'
};</code></pre>
</div>
</section>
<section class="section" id="validating-json-payloads-using-tsom-schema-validator__section_pld_vl2_bgc"><h2 id="d3079e87" class="title sectiontitle">Steps</h2>
<div class="p">
<ol class="ol" id="validating-json-payloads-using-tsom-schema-validator__ol_t2v_wl2_bgc">
<li class="li">Instantiate the Schema ValidatorjavascriptCopyEdit<pre class="prettyprint language-plaintext"><code class="pre codeblock language-plaintext">var TsomSchemaValidator = new sn_tsom_core.TsomSchemaValidator();
</code></pre></li>
<li class="li">Run a Boolean Validation Check<pre class="prettyprint language-plaintext"><code class="pre codeblock language-plaintext">if (!TsomSchemaValidator.isValidJson(target_json)) {
gs.error('Invalid JSON: ' + JSON.stringify(target_json));
return;
}
</code></pre></li>
<li class="li">Run a Detailed Validation Check<pre class="prettyprint language-plaintext"><code class="pre codeblock language-plaintext">let result = TsomSchemaValidator.checkJsonValidation(target_json);
if (!result.valid) {
gs.error('Invalid JSON: ' + JSON.stringify(result, null, 2));
return;
}
</code></pre></li>
</ol>
</div>
</section>
<section class="section" id="validating-json-payloads-using-tsom-schema-validator__section_qzg_cm2_bgc"><h2 id="d3079e114" class="title sectiontitle">Example output</h2>
<div class="p">
<pre class="prettyprint language-plaintext"><code class="pre codeblock language-plaintext">Example Output
{
"schemaName": "devices",
"errors": [
{
"message": "Missing required property: model_name",
"params": { "key": "model_name" },
"code": 302,
"dataPath": "/devices/0/ports/0",
"schemaPath": "/properties/devices/items/properties/ports/items/required/4"
}
],
"valid": false
}
</code></pre>
</div>
</section>
</div>
<nav role="navigation"></nav><nav role="navigation" class="tasksNavigation"></nav><nav role="navigation" class="related-links"><div class="col-md-4"><dt>Related concepts</dt><dd><ul><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/concept/configuring-the-telco-generic-schema-etl.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/configuring-the-telco-generic-schema-etl.html" class="link" title="Leverage the prebuilt Telecom Discovery Builder framework ETL by duplicating it into your connector scope, assigning the appropriate data source, and deploying it as part of a new service graph connector.">Configuring the Telecom Discovery Builder framework ETL in a connector</a></li><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/concept/exploring-the-telco-generic-schema-etl-framework.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/exploring-the-telco-generic-schema-etl-framework.html" class="link" title="The Telecom Discovery Builder framework ETL (Extract, Transform, Load) is a reusable and schema-aligned component delivered with the Telecom Service Operations Management (TSOM) Core application. It provides a consistent and extensible method for ingesting telecom inventory data into the ServiceNow Configuration Management Database (CMDB) across multiple Service Graph Connectors (SGCs).">Telecom Discovery Builder framework</a></li></ul></dd></div></nav>
</article></main></body></article> | {
"attachments": {
"all_attachments": null,
"topic_attachments": []
},
"available_languages": [
"enus"
],
"breadcrumbs": [
{
"title": "Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html"
},
{
"title": "Using Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/using-tsom.html"
}
],
"breadcrumbs_html": "<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops\">Zurich Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html\">Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/using-tsom.html\">Using Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<span class=\"active\">Validating JSON payloads using TSOM Schema Validator</span>",
"bundle_id": "zurich-telecom-service-ops",
"bundle_key": 2733,
"bundle_landing_page": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html",
"bundle_subtitle": null,
"bundle_title": "Zurich Telecommunications Service Operations Management",
"canonical_link": null,
"dates": {
"Added on": "2025-08-02T00:48:08.794016Z",
"Created on": "2025-07-21T00:00:00Z",
"Initial upload": "2025-07-30T22:24:33.519043Z",
"Updated on": "2025-07-31T00:00:00Z"
},
"dislike_url": "https://servicenow-be-prod.servicenow.com/dislike/55686953",
"dislikes": 0,
"es_archived_content": false,
"is_in_fav": false,
"is_liked": null,
"is_watched": false,
"keywords": [
" zurich zurich"
],
"labels": [
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "zurich",
"navtitle": "Zurich",
"outputclasses": [],
"subjectHeadId": "versions",
"subjectheadNavtitle": "Versions",
"visibility": "show-facet"
},
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "tsom",
"navtitle": "Telecommunications Service Operations Management",
"outputclasses": [],
"subjectHeadId": "products",
"subjectheadNavtitle": "Products",
"visibility": "show-facet"
}
],
"labels_text": "Versions > Zurich; Products > CRM and Industry Products > Telecommunications Media and Technology Assurance > Telecommunications Service Operations Management",
"like_url": "https://servicenow-be-prod.servicenow.com/like/55686953",
"likes": 0,
"metadata": {
"AI Search": null,
"AI Search Assist": null,
"Application Insights": null,
"Capabilities": null,
"Code Signing": null,
"Contextual Search": null,
"DC.contributor": null,
"DC.coverage": null,
"DC.creator": "ServiceNow",
"DC.date.created": "2025-07-21T17:11:31+05:30",
"DC.date.modified": "2025-07-31",
"DC.format": "HTML5",
"DC.identifier": "validating-json-payloads-using-tsom-schema-validator",
"DC.language": null,
"DC.relation": "../../../product/tmt-telecom-service-operations-mgt/concept/using-tsom.html",
"DC.rights.owner": "(C) Copyright 2025",
"DC.subject": null,
"DC.type": "concept",
"Data Discovery": null,
"Data Policy": null,
"Data Privacy": null,
"Discovery": null,
"External Content for AI Search": null,
"Field Administration": null,
"Field Normalization": null,
"Key Management Framework": null,
"Localization Framework": null,
"Now Platform": null,
"PlatSec": null,
"Platform": null,
"Platform Administration": null,
"Platform Performance": null,
"Platform Privacy": null,
"Proactive Triggers": null,
"Process Optimization": null,
"RN doc editing record number": null,
"Search Administration": null,
"Secrets Management": null,
"ServiceNow AI Platform": null,
"State Model": null,
"Subscription Management": null,
"Task Communications Management": null,
"Timeline Visualizations": null,
"User Administration": null,
"User Experience Analytics": null,
"Zing": null,
"ai-now-assist": null,
"app-name": null,
"app_route": null,
"azureapimanagemen": null,
"change-completed": null,
"change-item": null,
"change-request-id": null,
"change-request-reference": null,
"com.glide.embedded_help.category": null,
"component": null,
"copyright": "(C) Copyright 2025",
"crossroads": null,
"data": null,
"description": "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.",
"dominant_bundle": null,
"erp-canvas-video": null,
"fsm-mobile": null,
"fsm-route": null,
"fsm-sched-opt": null,
"fsm-wrk-order": null,
"genai-round-7": null,
"generator": "DITA-OT",
"glossPartOfSpeech": null,
"glossStatus": null,
"guided setup": null,
"guided tours": null,
"keywords": null,
"min-toc": null,
"mini": null,
"mini-to truec": null,
"mini-toc": "yes",
"mini_toc": null,
"minitoc": null,
"modification": null,
"now-assist-app-gen-video": null,
"order": null,
"page-type": null,
"page-type ": null,
"prodname": null,
"product": null,
"product_name": null,
"release": null,
"resourceID": null,
"roles": null,
"route_page": null,
"route_params_listId": null,
"route_params_table": null,
"route_params_type": null,
"route_type": null,
"setconfigurationproperties": null,
"topic": null,
"translation-type": "source",
"version": null,
"workflow": "Customer and Industry",
"workplace-srvc-delvry-ditamap": null
},
"page_id": "product/tmt-telecom-service-operations-mgt/concept/validating-json-payloads-using-tsom-schema-validator.html",
"page_key": 55686953,
"preprocessed_PDF": "https://downloads.docs.servicenow.com/pdf/enus/servicenow-zurich-telecom-service-ops-enus.pdf",
"rating": null,
"read_time_data": {
"char_count": 2284,
"img_count": 0,
"read_time": 1,
"video_links": [
""
],
"word_count": 267
},
"related_links": [
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "Leverage the prebuilt Telecom Discovery Builder framework ETL by duplicating it into your connector scope, assigning the appropriate data source, and deploying it as part of a new service graph connector.",
"title": "Configuring the Telecom Discovery Builder framework ETL in a connector",
"topic": "/product/tmt-telecom-service-operations-mgt/concept/configuring-the-telco-generic-schema-etl.html",
"type": "concept",
"url": null
},
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "The Telecom Discovery Builder framework ETL (Extract, Transform, Load) is a reusable and schema-aligned component delivered with the Telecom Service Operations Management (TSOM) Core application. It provides a consistent and extensible method for ingesting telecom inventory data into the ServiceNow Configuration Management Database (CMDB) across multiple Service Graph Connectors (SGCs).",
"title": "Telecom Discovery Builder framework",
"topic": "/product/tmt-telecom-service-operations-mgt/concept/exploring-the-telco-generic-schema-etl-framework.html",
"type": "concept",
"url": null
}
],
"search_title": null,
"title": "Validating JSON payloads using TSOM Schema Validator",
"topic_cluster": {
"clustered_by": {
"enabled": true,
"primary_key": "versions",
"primary_sort": "top-down",
"type": "subjecthead"
},
"clustered_labels": [
"versions"
],
"clustered_topics": [],
"clustering_title": "Zurich"
},
"topic_html": "<article class=\"hascomments\" data-page=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/validating-json-payloads-using-tsom-schema-validator.html\" id=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/concept/validating-json-payloads-using-tsom-schema-validator.html\"><body id=\"validating-json-payloads-using-tsom-schema-validator\"><main role=\"main\"><article role=\"article\" class=\"dita\" id=\"validating-json-payloads-using-tsom-schema-validator\" aria-labelledby=\"title_validating-json-payloads-using-tsom-schema-validator\">\n <h1 class=\"title topictitle1\" id=\"title_validating-json-payloads-using-tsom-schema-validator\">Validating JSON payloads using TSOM Schema Validator</h1>\n \n \n <div class=\"body conbody\"><p class=\"shortdesc\">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.</p>\n <p class=\"p\">Use this validator to check whether your JSON payloads conform to the expected schema for telco objects like Devices, Logical Connections, and Topologies before creating import sets. This pre-validation step helps to prevent schema\n mismatch errors and improves debugging.</p>\n <section class=\"section\" id=\"validating-json-payloads-using-tsom-schema-validator__section_ukd_rk2_bgc\"><h2 id=\"d3079e45\" class=\"title sectiontitle\">Supported schema types</h2>\n \n <div class=\"p\">The validator supports multiple schema types for different telco data structures:<ul class=\"ul\" id=\"validating-json-payloads-using-tsom-schema-validator__ul_w31_nl2_bgc\">\n <li class=\"li\">Logical Composites - Representing groupings of components: Equipment, PDUs, Fan Shelves</li>\n <li class=\"li\">Devices - Equipment and their contained components</li>\n <li class=\"li\">Logical Connections - Connections between network interfaces</li>\n <li class=\"li\">Port Relations - Relationships between network interfaces: physical, logical, lags</li>\n <li class=\"li\">Logical Connection Relations - Relationships between logical connections</li>\n <li class=\"li\">Topologies - Network topology</li>\n </ul></div>\n </section>\n <section class=\"section\" id=\"validating-json-payloads-using-tsom-schema-validator__section_ud3_sl2_bgc\"><h2 id=\"d3079e75\" class=\"title sectiontitle\">Class structure</h2>\n \n <div class=\"p\">\n <pre class=\"prettyprint language-plaintext\"><code class=\"pre codeblock language-plaintext\">let TsomSchemaValidator = Class.create();\nTsomSchemaValidator.prototype = {\ninitialize: function() {\nthis.schemas = new TsomGenericSchema();\n},\nisValidJson: function(payload) {\n// Validation logic that determines if the JSON structure is valid\n// Returns boolean (true/false)\n},\ncheckJsonValidation: function(payload) {\n// Validation logic that determines if the JSON structure is valid\n// Returns a JSON object containing errors (if exist)\n},\ntype: 'TsomSchemaValidator'\n};</code></pre>\n </div>\n </section>\n <section class=\"section\" id=\"validating-json-payloads-using-tsom-schema-validator__section_pld_vl2_bgc\"><h2 id=\"d3079e87\" class=\"title sectiontitle\">Steps</h2>\n \n <div class=\"p\">\n <ol class=\"ol\" id=\"validating-json-payloads-using-tsom-schema-validator__ol_t2v_wl2_bgc\">\n <li class=\"li\">Instantiate the Schema ValidatorjavascriptCopyEdit<pre class=\"prettyprint language-plaintext\"><code class=\"pre codeblock language-plaintext\">var TsomSchemaValidator = new sn_tsom_core.TsomSchemaValidator();\n</code></pre></li>\n <li class=\"li\">Run a Boolean Validation Check<pre class=\"prettyprint language-plaintext\"><code class=\"pre codeblock language-plaintext\">if (!TsomSchemaValidator.isValidJson(target_json)) {\n gs.error('Invalid JSON: ' + JSON.stringify(target_json));\n return;\n}\n</code></pre></li>\n <li class=\"li\">Run a Detailed Validation Check<pre class=\"prettyprint language-plaintext\"><code class=\"pre codeblock language-plaintext\">let result = TsomSchemaValidator.checkJsonValidation(target_json);\nif (!result.valid) {\n gs.error('Invalid JSON: ' + JSON.stringify(result, null, 2));\n return;\n}\n</code></pre></li>\n </ol>\n </div>\n </section>\n <section class=\"section\" id=\"validating-json-payloads-using-tsom-schema-validator__section_qzg_cm2_bgc\"><h2 id=\"d3079e114\" class=\"title sectiontitle\">Example output</h2>\n \n <div class=\"p\">\n <pre class=\"prettyprint language-plaintext\"><code class=\"pre codeblock language-plaintext\">Example Output\n{\n "schemaName": "devices",\n "errors": [\n {\n "message": "Missing required property: model_name",\n "params": { "key": "model_name" },\n "code": 302,\n "dataPath": "/devices/0/ports/0",\n "schemaPath": "/properties/devices/items/properties/ports/items/required/4"\n }\n ],\n "valid": false\n}\n</code></pre>\n </div>\n </section>\n </div>\n <nav role=\"navigation\"></nav><nav role=\"navigation\" class=\"tasksNavigation\"></nav><nav role=\"navigation\" class=\"related-links\"><div class=\"col-md-4\"><dt>Related concepts</dt><dd><ul><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept/configuring-the-telco-generic-schema-etl.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/configuring-the-telco-generic-schema-etl.html\" class=\"link\" title=\"Leverage the prebuilt Telecom Discovery Builder framework ETL by duplicating it into your connector scope, assigning the appropriate data source, and deploying it as part of a new service graph connector.\">Configuring the Telecom Discovery Builder framework ETL in a connector</a></li><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept/exploring-the-telco-generic-schema-etl-framework.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/exploring-the-telco-generic-schema-etl-framework.html\" class=\"link\" title=\"The Telecom Discovery Builder framework ETL (Extract, Transform, Load) is a reusable and schema-aligned component delivered with the Telecom Service Operations Management (TSOM) Core application. It provides a consistent and extensible method for ingesting telecom inventory data into the ServiceNow Configuration Management Database (CMDB) across multiple Service Graph Connectors (SGCs).\">Telecom Discovery Builder framework</a></li></ul></dd></div></nav>\n</article></main></body></article>",
"topic_language": "enus",
"views": 0,
"your_rating": null
} | # 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.
Use this validator to check whether your JSON payloads conform to the expected schema for telco objects like Devices, Logical Connections, and Topologies before creating import sets. This pre-validation step helps to prevent schema
mismatch errors and improves debugging.
## Supported schema types
The validator supports multiple schema types for different telco data structures:
* Logical Composites - Representing groupings of components: Equipment, PDUs, Fan Shelves
* Devices - Equipment and their contained components
* Logical Connections - Connections between network interfaces
* Port Relations - Relationships between network interfaces: physical, logical, lags
* Logical Connection Relations - Relationships between logical connections
* Topologies - Network topology
## Class structure
```None
let TsomSchemaValidator = Class.create();
TsomSchemaValidator.prototype = {
initialize: function() {
this.schemas = new TsomGenericSchema();
},
isValidJson: function(payload) {
// Validation logic that determines if the JSON structure is valid
// Returns boolean (true/false)
},
checkJsonValidation: function(payload) {
// Validation logic that determines if the JSON structure is valid
// Returns a JSON object containing errors (if exist)
},
type: 'TsomSchemaValidator'
};
```
## Steps
1. Instantiate the Schema ValidatorjavascriptCopyEdit
```None
var TsomSchemaValidator = new sn_tsom_core.TsomSchemaValidator();
```
2. Run a Boolean Validation Check
```None
if (!TsomSchemaValidator.isValidJson(target_json)) {
gs.error('Invalid JSON: ' + JSON.stringify(target_json));
return;
}
```
3. Run a Detailed Validation Check
```None
let result = TsomSchemaValidator.checkJsonValidation(target_json);
if (!result.valid) {
gs.error('Invalid JSON: ' + JSON.stringify(result, null, 2));
return;
}
```
## Example output
```None
Example Output
{
"schemaName": "devices",
"errors": [
{
"message": "Missing required property: model_name",
"params": { "key": "model_name" },
"code": 302,
"dataPath": "/devices/0/ports/0",
"schemaPath": "/properties/devices/items/properties/ports/items/required/4"
}
],
"valid": false
}
```
| ---
title: Validating JSON payloads using TSOM Schema Validator
description: 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.
keywords: []
breadcrumbs:
- Telecommunications Service Operations Management
- Using Telecommunications Service Operations Management
---
# 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.
Use this validator to check whether your JSON payloads conform to the expected schema for telco objects like Devices, Logical Connections, and Topologies before creating import sets. This pre-validation step helps to prevent schema
mismatch errors and improves debugging.
## Supported schema types
The validator supports multiple schema types for different telco data structures:
* Logical Composites - Representing groupings of components: Equipment, PDUs, Fan Shelves
* Devices - Equipment and their contained components
* Logical Connections - Connections between network interfaces
* Port Relations - Relationships between network interfaces: physical, logical, lags
* Logical Connection Relations - Relationships between logical connections
* Topologies - Network topology
## Class structure
```None
let TsomSchemaValidator = Class.create();
TsomSchemaValidator.prototype = {
initialize: function() {
this.schemas = new TsomGenericSchema();
},
isValidJson: function(payload) {
// Validation logic that determines if the JSON structure is valid
// Returns boolean (true/false)
},
checkJsonValidation: function(payload) {
// Validation logic that determines if the JSON structure is valid
// Returns a JSON object containing errors (if exist)
},
type: 'TsomSchemaValidator'
};
```
## Steps
1. Instantiate the Schema ValidatorjavascriptCopyEdit
```None
var TsomSchemaValidator = new sn_tsom_core.TsomSchemaValidator();
```
2. Run a Boolean Validation Check
```None
if (!TsomSchemaValidator.isValidJson(target_json)) {
gs.error('Invalid JSON: ' + JSON.stringify(target_json));
return;
}
```
3. Run a Detailed Validation Check
```None
let result = TsomSchemaValidator.checkJsonValidation(target_json);
if (!result.valid) {
gs.error('Invalid JSON: ' + JSON.stringify(result, null, 2));
return;
}
```
## Example output
```None
Example Output
{
"schemaName": "devices",
"errors": [
{
"message": "Missing required property: model_name",
"params": { "key": "model_name" },
"code": 302,
"dataPath": "/devices/0/ports/0",
"schemaPath": "/properties/devices/items/properties/ports/items/required/4"
}
],
"valid": false
}
```
|
https://www.servicenow.com/docs/en-US/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/reference/components-installed-with-tsom.html | https://servicenow-be-prod.servicenow.com/api/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/reference/components-installed-with-tsom.html | 2025-08-02 | daily | 0.5 | 268.xml | en-US | zurich-telecom-service-ops | product/tmt-telecom-service-operations-mgt/reference/components-installed-with-tsom.html | zurich | Telecommunications Service Operations Management reference | Several types of components are installed with Telecommunications Service Operations Management applications and plugins. | [] | [
"Telecommunications Service Operations Management"
] | <article class="hascomments" data-page="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/reference/components-installed-with-tsom.html" id="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/reference/components-installed-with-tsom.html"><body id="components-installed-with-tsom"><main role="main"><article role="article" class="dita" id="components-installed-with-tsom" aria-labelledby="title_components-installed-with-tsom">
<h1 class="title topictitle1" id="title_components-installed-with-tsom"><span class="ph">Telecommunications Service Operations Management</span> reference</h1>
<div class="body refbody"><p class="shortdesc">Several types of components are installed with <span class="ph">Telecommunications Service Operations Management</span> applications and plugins.</p></div>
<nav role="navigation"><dt class="ullinks"></dt><dd class="ullinks"><ul class="ullinks"><li class="link ulchildlink"><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/reference/alarm-management-user-roles.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/reference/alarm-management-user-roles.html">System components installed with Telecommunications API notifications</a><p class="shortdesc">Administrators can assign user roles to grant access to the API notification database tables. The following standard roles for the Topic [sn_api_notif_mgmt_topic] and Topic Subscription [sn_api_notif_mgmt_subscription] tables are included in the <span class="ph">ServiceNow</span> system.</p></li><li class="link ulchildlink"><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/reference/properties-installed-with-nokia-altiplano.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/reference/properties-installed-with-nokia-altiplano.html">System components installed with Nokia Altiplano</a><p class="shortdesc">System properties control how the connector operates, including discovery options and performance settings.</p></li><li class="link ulchildlink"><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/concept/system-properties-affecting-telecom-discrepancy-identification-reconciliation.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/system-properties-affecting-telecom-discrepancy-identification-reconciliation.html">System components installed with Telecom Discrepancy Identification & Reconciliation</a><p class="shortdesc">The system properties are part of the TSOM Visibility plugin (sn_tsom_core) and control the Telecom Discrepancy Identification & Reconciliation log (TSOM CMDB Audit). The TSOM Visibility plugin serves as an enabler for the TSOM Visibility applications, containing logic that is shared across the Telecom Discovery and Telecom Discrepancy Identification & Reconciliation solution.</p></li></ul></dd></nav><nav role="navigation" class="tasksNavigation"></nav><nav role="navigation" class="related-links"></nav></article></main></body></article> | {
"attachments": {
"all_attachments": null,
"topic_attachments": []
},
"available_languages": [
"enus"
],
"breadcrumbs": [
{
"title": "Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html"
}
],
"breadcrumbs_html": "<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops\">Zurich Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html\">Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<span class=\"active\">Telecommunications Service Operations Management reference</span>",
"bundle_id": "zurich-telecom-service-ops",
"bundle_key": 2733,
"bundle_landing_page": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html",
"bundle_subtitle": null,
"bundle_title": "Zurich Telecommunications Service Operations Management",
"canonical_link": null,
"dates": {
"Added on": "2025-08-02T00:48:08.794016Z",
"Created on": "2025-06-24T00:00:00Z",
"Initial upload": "2025-07-30T22:24:33.519043Z",
"Updated on": "2025-07-31T00:00:00Z"
},
"dislike_url": "https://servicenow-be-prod.servicenow.com/dislike/55686955",
"dislikes": 0,
"es_archived_content": false,
"is_in_fav": false,
"is_liked": null,
"is_watched": false,
"keywords": [
" zurich zurich"
],
"labels": [
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "zurich",
"navtitle": "Zurich",
"outputclasses": [],
"subjectHeadId": "versions",
"subjectheadNavtitle": "Versions",
"visibility": "show-facet"
},
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "tsom",
"navtitle": "Telecommunications Service Operations Management",
"outputclasses": [],
"subjectHeadId": "products",
"subjectheadNavtitle": "Products",
"visibility": "show-facet"
}
],
"labels_text": "Versions > Zurich; Products > CRM and Industry Products > Telecommunications Media and Technology Assurance > Telecommunications Service Operations Management",
"like_url": "https://servicenow-be-prod.servicenow.com/like/55686955",
"likes": 0,
"metadata": {
"AI Search": null,
"AI Search Assist": null,
"Application Insights": null,
"Capabilities": null,
"Code Signing": null,
"Contextual Search": null,
"DC.contributor": null,
"DC.coverage": null,
"DC.creator": "ServiceNow",
"DC.date.created": "2025-06-24T12:48:24+05:30",
"DC.date.modified": "2025-07-31",
"DC.format": "HTML5",
"DC.identifier": "components-installed-with-tsom",
"DC.language": null,
"DC.relation": "../../../product/tmt-telecom-service-operations-mgt/reference/alarm-management-user-roles.html",
"DC.rights.owner": "(C) Copyright 2025",
"DC.subject": null,
"DC.type": "reference",
"Data Discovery": null,
"Data Policy": null,
"Data Privacy": null,
"Discovery": null,
"External Content for AI Search": null,
"Field Administration": null,
"Field Normalization": null,
"Key Management Framework": null,
"Localization Framework": null,
"Now Platform": null,
"PlatSec": null,
"Platform": null,
"Platform Administration": null,
"Platform Performance": null,
"Platform Privacy": null,
"Proactive Triggers": null,
"Process Optimization": null,
"RN doc editing record number": null,
"Search Administration": null,
"Secrets Management": null,
"ServiceNow AI Platform": null,
"State Model": null,
"Subscription Management": null,
"Task Communications Management": null,
"Timeline Visualizations": null,
"User Administration": null,
"User Experience Analytics": null,
"Zing": null,
"ai-now-assist": null,
"app-name": null,
"app_route": null,
"azureapimanagemen": null,
"change-completed": null,
"change-item": null,
"change-request-id": null,
"change-request-reference": null,
"com.glide.embedded_help.category": null,
"component": null,
"copyright": "(C) Copyright 2025",
"crossroads": null,
"data": null,
"description": "Several types of components are installed with Telecommunications Service Operations Management applications and plugins.",
"dominant_bundle": null,
"erp-canvas-video": null,
"fsm-mobile": null,
"fsm-route": null,
"fsm-sched-opt": null,
"fsm-wrk-order": null,
"genai-round-7": null,
"generator": "DITA-OT",
"glossPartOfSpeech": null,
"glossStatus": null,
"guided setup": null,
"guided tours": null,
"keywords": null,
"min-toc": null,
"mini": null,
"mini-to truec": null,
"mini-toc": null,
"mini_toc": null,
"minitoc": null,
"modification": null,
"now-assist-app-gen-video": null,
"order": null,
"page-type": null,
"page-type ": null,
"prodname": null,
"product": null,
"product_name": null,
"release": null,
"resourceID": null,
"roles": null,
"route_page": null,
"route_params_listId": null,
"route_params_table": null,
"route_params_type": null,
"route_type": null,
"setconfigurationproperties": null,
"topic": null,
"translation-type": "source",
"version": null,
"workflow": "Customer and Industry",
"workplace-srvc-delvry-ditamap": null
},
"page_id": "product/tmt-telecom-service-operations-mgt/reference/components-installed-with-tsom.html",
"page_key": 55686955,
"preprocessed_PDF": "https://downloads.docs.servicenow.com/pdf/enus/servicenow-zurich-telecom-service-ops-enus.pdf",
"rating": null,
"read_time_data": {
"char_count": 1084,
"img_count": 0,
"read_time": 1,
"video_links": [
""
],
"word_count": 134
},
"related_links": [],
"search_title": null,
"title": "Telecommunications Service Operations Management reference",
"topic_cluster": {
"clustered_by": {
"enabled": true,
"primary_key": "versions",
"primary_sort": "top-down",
"type": "subjecthead"
},
"clustered_labels": [
"versions"
],
"clustered_topics": [],
"clustering_title": "Zurich"
},
"topic_html": "<article class=\"hascomments\" data-page=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/reference/components-installed-with-tsom.html\" id=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/reference/components-installed-with-tsom.html\"><body id=\"components-installed-with-tsom\"><main role=\"main\"><article role=\"article\" class=\"dita\" id=\"components-installed-with-tsom\" aria-labelledby=\"title_components-installed-with-tsom\">\n <h1 class=\"title topictitle1\" id=\"title_components-installed-with-tsom\"><span class=\"ph\">Telecommunications Service Operations Management</span> reference</h1>\n \n \n <div class=\"body refbody\"><p class=\"shortdesc\">Several types of components are installed with <span class=\"ph\">Telecommunications Service Operations Management</span> applications and plugins.</p></div>\n<nav role=\"navigation\"><dt class=\"ullinks\"></dt><dd class=\"ullinks\"><ul class=\"ullinks\"><li class=\"link ulchildlink\"><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/reference/alarm-management-user-roles.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/reference/alarm-management-user-roles.html\">System components installed with Telecommunications API notifications</a><p class=\"shortdesc\">Administrators can assign user roles to grant access to the API notification database tables. The following standard roles for the Topic [sn_api_notif_mgmt_topic] and Topic Subscription [sn_api_notif_mgmt_subscription] tables are included in the <span class=\"ph\">ServiceNow</span> system.</p></li><li class=\"link ulchildlink\"><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/reference/properties-installed-with-nokia-altiplano.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/reference/properties-installed-with-nokia-altiplano.html\">System components installed with Nokia Altiplano</a><p class=\"shortdesc\">System properties control how the connector operates, including discovery options and performance settings.</p></li><li class=\"link ulchildlink\"><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept/system-properties-affecting-telecom-discrepancy-identification-reconciliation.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/system-properties-affecting-telecom-discrepancy-identification-reconciliation.html\">System components installed with Telecom Discrepancy Identification & Reconciliation</a><p class=\"shortdesc\">The system properties are part of the TSOM Visibility plugin (sn_tsom_core) and control the Telecom Discrepancy Identification & Reconciliation log (TSOM CMDB Audit). The TSOM Visibility plugin serves as an enabler for the TSOM Visibility applications, containing logic that is shared across the Telecom Discovery and Telecom Discrepancy Identification & Reconciliation solution.</p></li></ul></dd></nav><nav role=\"navigation\" class=\"tasksNavigation\"></nav><nav role=\"navigation\" class=\"related-links\"></nav></article></main></body></article>",
"topic_language": "enus",
"views": 0,
"your_rating": null
} | # Telecommunications Service Operations Management reference
Several types of components are installed with Telecommunications Service Operations Management applications and plugins.
| ---
title: Telecommunications Service Operations Management reference
description: Several types of components are installed with Telecommunications Service
Operations Management applications and plugins.
keywords: []
breadcrumbs:
- Telecommunications Service Operations Management
---
# Telecommunications Service Operations Management reference
Several types of components are installed with Telecommunications Service Operations Management applications and plugins.
|
https://www.servicenow.com/docs/en-US/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/reference/example-create-a-duplicate-of-telco-generic-etl-schema.html | https://servicenow-be-prod.servicenow.com/api/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/reference/example-create-a-duplicate-of-telco-generic-etl-schema.html | 2025-08-02 | daily | 0.5 | 268.xml | en-US | zurich-telecom-service-ops | product/tmt-telecom-service-operations-mgt/reference/example-create-a-duplicate-of-telco-generic-etl-schema.html | zurich | Example - Duplicate the Telco Generic ETL Schema | This example walks you through how to duplicate the Telco Generic Schema ETL to set up a customized Service Graph Connector (SGC) ETL for your telecom integration. Use this procedure when you want to create a baseline ETL in your | [] | [
"Telecommunications Service Operations Management",
"Configuring Telecommunications Service Operations Management",
"Set up Telecom Visibility",
"Configuring the Telecom Discovery Builder framework ETL in a connector",
"Duplicate the Telecom Discovery Builder framework ETL into a connector scope"
] | <article class="hascomments" data-page="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/reference/example-create-a-duplicate-of-telco-generic-etl-schema.html" id="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/reference/example-create-a-duplicate-of-telco-generic-etl-schema.html"><body id="example-create-a-duplicate-of-telco-generic-etl-schema"><main role="main"><article role="article" class="dita" id="example-create-a-duplicate-of-telco-generic-etl-schema" aria-labelledby="title_example-create-a-duplicate-of-telco-generic-etl-schema">
<h1 class="title topictitle1" id="title_example-create-a-duplicate-of-telco-generic-etl-schema">Example - Duplicate the Telco Generic ETL Schema</h1>
<div class="body refbody"><p class="shortdesc">This example walks you through how to duplicate the Telco Generic Schema ETL to set up a customized Service Graph Connector (SGC) ETL for your telecom integration. Use this procedure when you want to create a baseline ETL in
your connector’s application scope based on the standardized Telco Generic Schema, ensuring schema alignment, consistency, and faster deployment.</p>
<section class="section" id="example-create-a-duplicate-of-telco-generic-etl-schema__section_bxx_22z_dfc"><h2 id="d2972e42" class="title sectiontitle">Scenario</h2>
<p class="p">You are deploying a new Service Graph Connector and need to duplicate the Telco Generic Schema ETL into your connector’s application scope.</p>
<p class="p">Create a temporary data source, duplicate the ETL, and configure it to work with your connector’s device payloads.</p>
</section>
<section class="section" id="example-create-a-duplicate-of-telco-generic-etl-schema__section_hlz_h2z_dfc"><h2 id="d2972e54" class="title sectiontitle">Steps to duplicate the Telco Generic Schema ETL</h2>
<div class="p">
<ol class="ol" id="example-create-a-duplicate-of-telco-generic-etl-schema__ol_krf_h2z_dfc">
<li class="li">Switch to the connector’s application scope where you want to duplicate the ETL (e.g., Nokia NSP Connector).</li>
<li class="li">Create the data source: <ul class="ul" id="example-create-a-duplicate-of-telco-generic-etl-schema__ul_q1r_m2z_dfc">
<li class="li">Navigate to System Import Sets > Administration > Data Sources.</li>
<li class="li">Locate the Generic Schema Multi-Source Data Source provided by the TSOM Core application.</li>
<li class="li">Copy this data source into your connector’s application scope.</li>
<li class="li">Test the copied data source by running Test Load 20 Records to create a sample import set.</li>
</ul></li>
<li class="li">Open the Duplicate ETL Transform Map Dialog: In ETL Studio, select Duplicate ETL to start the duplication process.</li>
<li class="li">In the <span class="ph uicontrol">Duplicate from</span> list, choose Telco Generic Schema.</li>
<li class="li">Select <span class="ph uicontrol">Add new…</span> and enter a name for the duplicated ETL.</li>
<li class="li">Select importSet as the discovery source for your duplicated ETL.</li>
<li class="li">Enter a new name for the duplicated transform map.</li>
<li class="li">Specify the newly created temporary data source that you copied from the Generic Schema Multi Source.</li>
<li class="li">Optionally, enable <span class="ph uicontrol">Auto-pull a new import set</span> to automatically load new records after duplication.</li>
<li class="li">Click <span class="ph uicontrol">Create Duplicate</span> to complete the duplication.</li>
<li class="li">Update <span class="ph uicontrol">Basic Details</span>: <ul class="ul" id="example-create-a-duplicate-of-telco-generic-etl-schema__ul_sgb_dfz_dfc">
<li class="li">After duplication, open the newly created ETL.</li>
<li class="li">In step 1: specify <span class="ph uicontrol">Basic Details</span>, replace the temporary data source with your connector’s production data source.</li>
</ul></li>
<li class="li">Save the ETL Configuration: click <span class="ph uicontrol">Save</span> to finalize your changes.</li>
<li class="li">Run the <span class="ph uicontrol">Data Source</span>: From Import Schedules, run your connector’s data source to ingest real device data.</li>
</ol>
</div>
<p class="p">Result: The system creates a new ETL based on the Telco Generic Schema settings and processes the payloads from your specified connector data source. The imported data is transformed into Configuration Items (CIs) and inserted into
the ServiceNow CMDB with the expected relationships and structures.</p>
</section>
</div>
</article></main></body></article> | {
"attachments": {
"all_attachments": null,
"topic_attachments": []
},
"available_languages": [
"enus"
],
"breadcrumbs": [
{
"title": "Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html"
},
{
"title": "Configuring Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/configuring-tsom.html"
},
{
"title": "Set up Telecom Visibility",
"topic_id": "product/tmt-telecom-service-operations-mgt/task/configuring-tsom-visibility.html"
},
{
"title": "Configuring the Telecom Discovery Builder framework ETL in a connector",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/configuring-the-telco-generic-schema-etl.html"
},
{
"title": "Duplicate the Telecom Discovery Builder framework ETL into a connector scope",
"topic_id": "product/tmt-telecom-service-operations-mgt/task/duplicate-the-generic-etl-to-use-a-specific-connector.html"
}
],
"breadcrumbs_html": "<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops\">Zurich Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html\">Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/configuring-tsom.html\">Configuring Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/configuring-tsom-visibility.html\">Set up Telecom Visibility</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/configuring-the-telco-generic-schema-etl.html\">Configuring the Telecom Discovery Builder framework ETL in a connector</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/duplicate-the-generic-etl-to-use-a-specific-connector.html\">Duplicate the Telecom Discovery Builder framework ETL into a connector scope</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<span class=\"active\">Example - Duplicate the Telco Generic ETL Schema</span>",
"bundle_id": "zurich-telecom-service-ops",
"bundle_key": 2733,
"bundle_landing_page": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html",
"bundle_subtitle": null,
"bundle_title": "Zurich Telecommunications Service Operations Management",
"canonical_link": null,
"dates": {
"Added on": "2025-08-02T00:48:08.794016Z",
"Created on": "2025-04-29T00:00:00Z",
"Initial upload": "2025-07-30T22:24:33.519043Z",
"Updated on": "2025-07-31T00:00:00Z"
},
"dislike_url": "https://servicenow-be-prod.servicenow.com/dislike/55686956",
"dislikes": 0,
"es_archived_content": false,
"is_in_fav": false,
"is_liked": null,
"is_watched": false,
"keywords": [
" zurich zurich"
],
"labels": [
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "zurich",
"navtitle": "Zurich",
"outputclasses": [],
"subjectHeadId": "versions",
"subjectheadNavtitle": "Versions",
"visibility": "show-facet"
},
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "tsom",
"navtitle": "Telecommunications Service Operations Management",
"outputclasses": [],
"subjectHeadId": "products",
"subjectheadNavtitle": "Products",
"visibility": "show-facet"
}
],
"labels_text": "Versions > Zurich; Products > CRM and Industry Products > Telecommunications Media and Technology Assurance > Telecommunications Service Operations Management",
"like_url": "https://servicenow-be-prod.servicenow.com/like/55686956",
"likes": 0,
"metadata": {
"AI Search": null,
"AI Search Assist": null,
"Application Insights": null,
"Capabilities": null,
"Code Signing": null,
"Contextual Search": null,
"DC.contributor": null,
"DC.coverage": null,
"DC.creator": "ServiceNow",
"DC.date.created": "2025-04-29T18:16:04+05:30",
"DC.date.modified": "2025-07-31",
"DC.format": "HTML5",
"DC.identifier": "example-create-a-duplicate-of-telco-generic-etl-schema",
"DC.language": null,
"DC.relation": null,
"DC.rights.owner": "(C) Copyright 2025",
"DC.subject": null,
"DC.type": "reference",
"Data Discovery": null,
"Data Policy": null,
"Data Privacy": null,
"Discovery": null,
"External Content for AI Search": null,
"Field Administration": null,
"Field Normalization": null,
"Key Management Framework": null,
"Localization Framework": null,
"Now Platform": null,
"PlatSec": null,
"Platform": null,
"Platform Administration": null,
"Platform Performance": null,
"Platform Privacy": null,
"Proactive Triggers": null,
"Process Optimization": null,
"RN doc editing record number": null,
"Search Administration": null,
"Secrets Management": null,
"ServiceNow AI Platform": null,
"State Model": null,
"Subscription Management": null,
"Task Communications Management": null,
"Timeline Visualizations": null,
"User Administration": null,
"User Experience Analytics": null,
"Zing": null,
"ai-now-assist": null,
"app-name": null,
"app_route": null,
"azureapimanagemen": null,
"change-completed": null,
"change-item": null,
"change-request-id": null,
"change-request-reference": null,
"com.glide.embedded_help.category": null,
"component": null,
"copyright": "(C) Copyright 2025",
"crossroads": null,
"data": null,
"description": "This example walks you through how to duplicate the Telco Generic Schema ETL to set up a customized Service Graph Connector (SGC) ETL for your telecom integration. Use this procedure when you want to create a baseline ETL in your",
"dominant_bundle": null,
"erp-canvas-video": null,
"fsm-mobile": null,
"fsm-route": null,
"fsm-sched-opt": null,
"fsm-wrk-order": null,
"genai-round-7": null,
"generator": "DITA-OT",
"glossPartOfSpeech": null,
"glossStatus": null,
"guided setup": null,
"guided tours": null,
"keywords": null,
"min-toc": null,
"mini": null,
"mini-to truec": null,
"mini-toc": "yes",
"mini_toc": null,
"minitoc": null,
"modification": null,
"now-assist-app-gen-video": null,
"order": null,
"page-type": null,
"page-type ": null,
"prodname": null,
"product": null,
"product_name": null,
"release": null,
"resourceID": null,
"roles": null,
"route_page": null,
"route_params_listId": null,
"route_params_table": null,
"route_params_type": null,
"route_type": null,
"setconfigurationproperties": null,
"topic": null,
"translation-type": "source",
"version": null,
"workflow": "Customer and Industry",
"workplace-srvc-delvry-ditamap": null
},
"page_id": "product/tmt-telecom-service-operations-mgt/reference/example-create-a-duplicate-of-telco-generic-etl-schema.html",
"page_key": 55686956,
"preprocessed_PDF": "https://downloads.docs.servicenow.com/pdf/enus/servicenow-zurich-telecom-service-ops-enus.pdf",
"rating": null,
"read_time_data": {
"char_count": 2390,
"img_count": 0,
"read_time": 2,
"video_links": [
""
],
"word_count": 372
},
"related_links": [],
"search_title": null,
"title": "Example - Duplicate the Telco Generic ETL Schema",
"topic_cluster": {
"clustered_by": {
"enabled": true,
"primary_key": "versions",
"primary_sort": "top-down",
"type": "subjecthead"
},
"clustered_labels": [
"versions"
],
"clustered_topics": [],
"clustering_title": "Zurich"
},
"topic_html": "<article class=\"hascomments\" data-page=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/reference/example-create-a-duplicate-of-telco-generic-etl-schema.html\" id=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/reference/example-create-a-duplicate-of-telco-generic-etl-schema.html\"><body id=\"example-create-a-duplicate-of-telco-generic-etl-schema\"><main role=\"main\"><article role=\"article\" class=\"dita\" id=\"example-create-a-duplicate-of-telco-generic-etl-schema\" aria-labelledby=\"title_example-create-a-duplicate-of-telco-generic-etl-schema\">\n <h1 class=\"title topictitle1\" id=\"title_example-create-a-duplicate-of-telco-generic-etl-schema\">Example - Duplicate the Telco Generic ETL Schema</h1>\n \n \n <div class=\"body refbody\"><p class=\"shortdesc\">This example walks you through how to duplicate the Telco Generic Schema ETL to set up a customized Service Graph Connector (SGC) ETL for your telecom integration. Use this procedure when you want to create a baseline ETL in\n your connector’s application scope based on the standardized Telco Generic Schema, ensuring schema alignment, consistency, and faster deployment.</p>\n <section class=\"section\" id=\"example-create-a-duplicate-of-telco-generic-etl-schema__section_bxx_22z_dfc\"><h2 id=\"d2972e42\" class=\"title sectiontitle\">Scenario</h2>\n \n <p class=\"p\">You are deploying a new Service Graph Connector and need to duplicate the Telco Generic Schema ETL into your connector’s application scope.</p>\n <p class=\"p\">Create a temporary data source, duplicate the ETL, and configure it to work with your connector’s device payloads.</p>\n </section>\n <section class=\"section\" id=\"example-create-a-duplicate-of-telco-generic-etl-schema__section_hlz_h2z_dfc\"><h2 id=\"d2972e54\" class=\"title sectiontitle\">Steps to duplicate the Telco Generic Schema ETL</h2>\n \n <div class=\"p\">\n <ol class=\"ol\" id=\"example-create-a-duplicate-of-telco-generic-etl-schema__ol_krf_h2z_dfc\">\n <li class=\"li\">Switch to the connector’s application scope where you want to duplicate the ETL (e.g., Nokia NSP Connector).</li>\n <li class=\"li\">Create the data source: <ul class=\"ul\" id=\"example-create-a-duplicate-of-telco-generic-etl-schema__ul_q1r_m2z_dfc\">\n <li class=\"li\">Navigate to System Import Sets > Administration > Data Sources.</li>\n <li class=\"li\">Locate the Generic Schema Multi-Source Data Source provided by the TSOM Core application.</li>\n <li class=\"li\">Copy this data source into your connector’s application scope.</li>\n <li class=\"li\">Test the copied data source by running Test Load 20 Records to create a sample import set.</li>\n </ul></li>\n <li class=\"li\">Open the Duplicate ETL Transform Map Dialog: In ETL Studio, select Duplicate ETL to start the duplication process.</li>\n <li class=\"li\">In the <span class=\"ph uicontrol\">Duplicate from</span> list, choose Telco Generic Schema.</li>\n <li class=\"li\">Select <span class=\"ph uicontrol\">Add new…</span> and enter a name for the duplicated ETL.</li>\n <li class=\"li\">Select importSet as the discovery source for your duplicated ETL.</li>\n <li class=\"li\">Enter a new name for the duplicated transform map.</li>\n <li class=\"li\">Specify the newly created temporary data source that you copied from the Generic Schema Multi Source.</li>\n <li class=\"li\">Optionally, enable <span class=\"ph uicontrol\">Auto-pull a new import set</span> to automatically load new records after duplication.</li>\n <li class=\"li\">Click <span class=\"ph uicontrol\">Create Duplicate</span> to complete the duplication.</li>\n <li class=\"li\">Update <span class=\"ph uicontrol\">Basic Details</span>: <ul class=\"ul\" id=\"example-create-a-duplicate-of-telco-generic-etl-schema__ul_sgb_dfz_dfc\">\n <li class=\"li\">After duplication, open the newly created ETL.</li>\n <li class=\"li\">In step 1: specify <span class=\"ph uicontrol\">Basic Details</span>, replace the temporary data source with your connector’s production data source.</li>\n </ul></li>\n <li class=\"li\">Save the ETL Configuration: click <span class=\"ph uicontrol\">Save</span> to finalize your changes.</li>\n <li class=\"li\">Run the <span class=\"ph uicontrol\">Data Source</span>: From Import Schedules, run your connector’s data source to ingest real device data.</li>\n </ol>\n </div>\n <p class=\"p\">Result: The system creates a new ETL based on the Telco Generic Schema settings and processes the payloads from your specified connector data source. The imported data is transformed into Configuration Items (CIs) and inserted into\n the ServiceNow CMDB with the expected relationships and structures.</p>\n </section>\n </div>\n</article></main></body></article>",
"topic_language": "enus",
"views": 0,
"your_rating": null
} | # Example - Duplicate the Telco Generic ETL Schema
This example walks you through how to duplicate the Telco Generic Schema ETL to set up a customized Service Graph Connector (SGC) ETL for your telecom integration. Use this procedure when you want to create a baseline ETL in
your connector’s application scope based on the standardized Telco Generic Schema, ensuring schema alignment, consistency, and faster deployment.
## Scenario
You are deploying a new Service Graph Connector and need to duplicate the Telco Generic Schema ETL into your connector’s application scope.
Create a temporary data source, duplicate the ETL, and configure it to work with your connector’s device payloads.
## Steps to duplicate the Telco Generic Schema ETL
1. Switch to the connector’s application scope where you want to duplicate the ETL (e.g., Nokia NSP Connector).
2. Create the data source:
* Navigate to System Import Sets > Administration > Data Sources.
* Locate the Generic Schema Multi-Source Data Source provided by the TSOM Core application.
* Copy this data source into your connector’s application scope.
* Test the copied data source by running Test Load 20 Records to create a sample import set.
3. Open the Duplicate ETL Transform Map Dialog: In ETL Studio, select Duplicate ETL to start the duplication process.
4. In the Duplicate from list, choose Telco Generic Schema.
5. Select Add new… and enter a name for the duplicated ETL.
6. Select importSet as the discovery source for your duplicated ETL.
7. Enter a new name for the duplicated transform map.
8. Specify the newly created temporary data source that you copied from the Generic Schema Multi Source.
9. Optionally, enable Auto-pull a new import set to automatically load new records after duplication.
10. Click Create Duplicate to complete the duplication.
11. Update Basic Details:
* After duplication, open the newly created ETL.
* In step 1: specify Basic Details, replace the temporary data source with your connector’s production data source.
12. Save the ETL Configuration: click Save to finalize your changes.
13. Run the Data Source: From Import Schedules, run your connector’s data source to ingest real device data.
Result: The system creates a new ETL based on the Telco Generic Schema settings and processes the payloads from your specified connector data source. The imported data is transformed into Configuration Items (CIs) and inserted into
the ServiceNow CMDB with the expected relationships and structures.
| ---
title: Example - Duplicate the Telco Generic ETL Schema
description: This example walks you through how to duplicate the Telco Generic Schema
ETL to set up a customized Service Graph Connector (SGC) ETL for your telecom integration.
Use this procedure when you want to create a baseline ETL in your
keywords: []
breadcrumbs:
- Telecommunications Service Operations Management
- Configuring Telecommunications Service Operations Management
- Set up Telecom Visibility
- Configuring the Telecom Discovery Builder framework ETL in a connector
- Duplicate the Telecom Discovery Builder framework ETL into a connector scope
---
# Example - Duplicate the Telco Generic ETL Schema
This example walks you through how to duplicate the Telco Generic Schema ETL to set up a customized Service Graph Connector (SGC) ETL for your telecom integration. Use this procedure when you want to create a baseline ETL in
your connector’s application scope based on the standardized Telco Generic Schema, ensuring schema alignment, consistency, and faster deployment.
## Scenario
You are deploying a new Service Graph Connector and need to duplicate the Telco Generic Schema ETL into your connector’s application scope.
Create a temporary data source, duplicate the ETL, and configure it to work with your connector’s device payloads.
## Steps to duplicate the Telco Generic Schema ETL
1. Switch to the connector’s application scope where you want to duplicate the ETL (e.g., Nokia NSP Connector).
2. Create the data source:
* Navigate to System Import Sets > Administration > Data Sources.
* Locate the Generic Schema Multi-Source Data Source provided by the TSOM Core application.
* Copy this data source into your connector’s application scope.
* Test the copied data source by running Test Load 20 Records to create a sample import set.
3. Open the Duplicate ETL Transform Map Dialog: In ETL Studio, select Duplicate ETL to start the duplication process.
4. In the Duplicate from list, choose Telco Generic Schema.
5. Select Add new… and enter a name for the duplicated ETL.
6. Select importSet as the discovery source for your duplicated ETL.
7. Enter a new name for the duplicated transform map.
8. Specify the newly created temporary data source that you copied from the Generic Schema Multi Source.
9. Optionally, enable Auto-pull a new import set to automatically load new records after duplication.
10. Click Create Duplicate to complete the duplication.
11. Update Basic Details:
* After duplication, open the newly created ETL.
* In step 1: specify Basic Details, replace the temporary data source with your connector’s production data source.
12. Save the ETL Configuration: click Save to finalize your changes.
13. Run the Data Source: From Import Schedules, run your connector’s data source to ingest real device data.
Result: The system creates a new ETL based on the Telco Generic Schema settings and processes the payloads from your specified connector data source. The imported data is transformed into Configuration Items (CIs) and inserted into
the ServiceNow CMDB with the expected relationships and structures.
|
https://www.servicenow.com/docs/en-US/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/reference/properties-installed-with-nokia-altiplano.html | https://servicenow-be-prod.servicenow.com/api/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/reference/properties-installed-with-nokia-altiplano.html | 2025-08-02 | daily | 0.5 | 268.xml | en-US | zurich-telecom-service-ops | product/tmt-telecom-service-operations-mgt/reference/properties-installed-with-nokia-altiplano.html | zurich | System components installed with Nokia Altiplano | System properties control how the connector operates, including discovery options and performance settings. | [] | [
"Telecommunications Service Operations Management",
"Telecommunications Service Operations Management reference"
] | <article class="hascomments" data-page="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/reference/properties-installed-with-nokia-altiplano.html" id="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/reference/properties-installed-with-nokia-altiplano.html"><body id="properties-installed-with-nokia-altiplano"><main role="main"><article role="article" class="dita" id="properties-installed-with-nokia-altiplano" aria-labelledby="title_properties-installed-with-nokia-altiplano">
<h1 class="title topictitle1" id="title_properties-installed-with-nokia-altiplano">System components installed with Nokia Altiplano</h1>
<div class="body refbody"><p class="shortdesc">System properties control how the connector operates, including discovery options and performance settings.</p>
<div class="table-wrap"><table count-columns="2" class="table" id="properties-installed-with-nokia-altiplano__table_ghf_tcy_vfc"><caption><span class="table--title-label">Table 1. </span><span class="title">Properties installed with Nokia Altiplano</span></caption><colgroup><col/><col/></colgroup><thead class="thead">
<tr class="row">
<th class="entry" id="properties-installed-with-nokia-altiplano__table_ghf_tcy_vfc__entry__1">Property</th>
<th class="entry" id="properties-installed-with-nokia-altiplano__table_ghf_tcy_vfc__entry__2">Description</th>
</tr>
</thead><tbody class="tbody">
<tr class="row">
<td class="entry" headers="properties-installed-with-nokia-altiplano__table_ghf_tcy_vfc__entry__1"><span class="keyword parmname">sn_sgc_altiplano.enable_onu_discovery</span></td>
<td class="entry" headers="properties-installed-with-nokia-altiplano__table_ghf_tcy_vfc__entry__2">Enable or disable discovery of ONU devices and logical connections between OLT and ONU. <ul class="ul" id="properties-installed-with-nokia-altiplano__ul_lpn_4fc_wfc">
<li class="li">Default value: True</li>
<li class="li">Location: <span class="ph uicontrol">All</span>><span class="ph uicontrol">Service Graph Connectors</span>><span class="ph uicontrol">Nokia Altiplano</span>><span class="ph uicontrol">Properties</span> or <span class="ph uicontrol">System Properties</span> [sys_properties]
table filtering by the name ‘*altiplano’</li>
</ul></td>
</tr>
<tr class="row">
<td class="entry" headers="properties-installed-with-nokia-altiplano__table_ghf_tcy_vfc__entry__1"><span class="keyword parmname">sn_sgc_altiplano.devices_list_batch_size</span></td>
<td class="entry" headers="properties-installed-with-nokia-altiplano__table_ghf_tcy_vfc__entry__2">Controls the batch size for Altiplano REST API calls.<ul class="ul" id="properties-installed-with-nokia-altiplano__ul_yft_wfc_wfc">
<li class="li">Default value: 1000</li>
<li class="li">Location: <span class="ph uicontrol">All</span>><span class="ph uicontrol">Service Graph Connectors</span>><span class="ph uicontrol">Nokia Altiplano</span>><span class="ph uicontrol">Properties</span> or <span class="ph uicontrol">System Properties</span> [sys_properties]
table filtering by the name ‘*altiplano’</li>
</ul></td>
</tr>
<tr class="row">
<td class="entry" headers="properties-installed-with-nokia-altiplano__table_ghf_tcy_vfc__entry__1"><span class="keyword parmname">sn_sgc_altiplano.parallel_number_of_data_source_jobs</span></td>
<td class="entry" headers="properties-installed-with-nokia-altiplano__table_ghf_tcy_vfc__entry__2">Number of parallel jobs for collecting Altiplano data (requires "Enable parallel loading" setting).<ul class="ul" id="properties-installed-with-nokia-altiplano__ul_ont_xfc_wfc">
<li class="li">Default value: 2</li>
<li class="li">Location: <span class="ph uicontrol">All</span>><span class="ph uicontrol">Service Graph Connectors</span>><span class="ph uicontrol">Nokia Altiplano</span>><span class="ph uicontrol">Properties</span> or <span class="ph uicontrol">System Properties</span> [sys_properties]
table filtering by the name ‘*altiplano’</li>
</ul></td>
</tr>
<tr class="row">
<td class="entry" headers="properties-installed-with-nokia-altiplano__table_ghf_tcy_vfc__entry__1"><span class="keyword parmname">sn_sgc_altiplano.onu_ci_class</span></td>
<td class="entry" headers="properties-installed-with-nokia-altiplano__table_ghf_tcy_vfc__entry__2">Defines whether ONUs are stored as <code class="ph codeph">ONU</code> or <code class="ph codeph">ONT</code> CI class. <ul class="ul" id="properties-installed-with-nokia-altiplano__ul_fgp_yfc_wfc">
<li class="li">Default value: ONU</li>
<li class="li">Location: <span class="ph uicontrol">All</span>><span class="ph uicontrol">Service Graph Connectors</span>><span class="ph uicontrol">Nokia Altiplano</span>><span class="ph uicontrol">Properties</span> or <span class="ph uicontrol">System Properties</span> [sys_properties]
table filtering by the name ‘*altiplano’</li>
</ul></td>
</tr>
</tbody></table></div>
</div>
<nav role="navigation"></nav><nav role="navigation" class="tasksNavigation"></nav><nav role="navigation" class="related-links"><div class="col-md-4"><dt>Related concepts</dt><dd><ul><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/concept/service-graph-connector-for-nokia-altiplano.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/service-graph-connector-for-nokia-altiplano.html" class="link" title="The Service Graph Connector for Nokia Altiplano offers a telecom-aware integration that brings real-time network inventory from the Nokia Altiplano Access Network SDN Controller into your ServiceNow CMDB.">Telecom Discovery via Nokia Altiplano</a></li><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/concept/configuring-service-graph-connector-nokia-altiplano.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/configuring-service-graph-connector-nokia-altiplano.html" class="link" title="Configure the Nokia Altiplano service graph connector to import physical and logical inventory data from the Nokia Altiplano Access Network SDN Controller into your ServiceNow Configuration Management Database (CMDB).">Configuring Nokia Altiplano service graph connector</a></li></ul></dd></div></nav>
</article></main></body></article> | {
"attachments": {
"all_attachments": null,
"topic_attachments": []
},
"available_languages": [
"enus"
],
"breadcrumbs": [
{
"title": "Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html"
},
{
"title": "Telecommunications Service Operations Management reference",
"topic_id": "product/tmt-telecom-service-operations-mgt/reference/components-installed-with-tsom.html"
}
],
"breadcrumbs_html": "<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops\">Zurich Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html\">Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/reference/components-installed-with-tsom.html\">Telecommunications Service Operations Management reference</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<span class=\"active\">System components installed with Nokia Altiplano</span>",
"bundle_id": "zurich-telecom-service-ops",
"bundle_key": 2733,
"bundle_landing_page": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html",
"bundle_subtitle": null,
"bundle_title": "Zurich Telecommunications Service Operations Management",
"canonical_link": null,
"dates": {
"Added on": "2025-08-02T00:48:08.794016Z",
"Created on": "2025-07-03T00:00:00Z",
"Initial upload": "2025-07-30T22:24:33.519043Z",
"Updated on": "2025-07-31T00:00:00Z"
},
"dislike_url": "https://servicenow-be-prod.servicenow.com/dislike/55686957",
"dislikes": 0,
"es_archived_content": false,
"is_in_fav": false,
"is_liked": null,
"is_watched": false,
"keywords": [
" zurich zurich"
],
"labels": [
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "zurich",
"navtitle": "Zurich",
"outputclasses": [],
"subjectHeadId": "versions",
"subjectheadNavtitle": "Versions",
"visibility": "show-facet"
},
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "tsom",
"navtitle": "Telecommunications Service Operations Management",
"outputclasses": [],
"subjectHeadId": "products",
"subjectheadNavtitle": "Products",
"visibility": "show-facet"
}
],
"labels_text": "Versions > Zurich; Products > CRM and Industry Products > Telecommunications Media and Technology Assurance > Telecommunications Service Operations Management",
"like_url": "https://servicenow-be-prod.servicenow.com/like/55686957",
"likes": 0,
"metadata": {
"AI Search": null,
"AI Search Assist": null,
"Application Insights": null,
"Capabilities": null,
"Code Signing": null,
"Contextual Search": null,
"DC.contributor": null,
"DC.coverage": null,
"DC.creator": "ServiceNow",
"DC.date.created": "2025-07-03T12:55:31+05:30",
"DC.date.modified": "2025-07-31",
"DC.format": "HTML5",
"DC.identifier": "properties-installed-with-nokia-altiplano",
"DC.language": null,
"DC.relation": "../../../product/tmt-telecom-service-operations-mgt/reference/components-installed-with-tsom.html",
"DC.rights.owner": "(C) Copyright 2025",
"DC.subject": null,
"DC.type": "reference",
"Data Discovery": null,
"Data Policy": null,
"Data Privacy": null,
"Discovery": null,
"External Content for AI Search": null,
"Field Administration": null,
"Field Normalization": null,
"Key Management Framework": null,
"Localization Framework": null,
"Now Platform": null,
"PlatSec": null,
"Platform": null,
"Platform Administration": null,
"Platform Performance": null,
"Platform Privacy": null,
"Proactive Triggers": null,
"Process Optimization": null,
"RN doc editing record number": null,
"Search Administration": null,
"Secrets Management": null,
"ServiceNow AI Platform": null,
"State Model": null,
"Subscription Management": null,
"Task Communications Management": null,
"Timeline Visualizations": null,
"User Administration": null,
"User Experience Analytics": null,
"Zing": null,
"ai-now-assist": null,
"app-name": null,
"app_route": null,
"azureapimanagemen": null,
"change-completed": null,
"change-item": null,
"change-request-id": null,
"change-request-reference": null,
"com.glide.embedded_help.category": null,
"component": null,
"copyright": "(C) Copyright 2025",
"crossroads": null,
"data": null,
"description": "System properties control how the connector operates, including discovery options and performance settings.",
"dominant_bundle": null,
"erp-canvas-video": null,
"fsm-mobile": null,
"fsm-route": null,
"fsm-sched-opt": null,
"fsm-wrk-order": null,
"genai-round-7": null,
"generator": "DITA-OT",
"glossPartOfSpeech": null,
"glossStatus": null,
"guided setup": null,
"guided tours": null,
"keywords": null,
"min-toc": null,
"mini": null,
"mini-to truec": null,
"mini-toc": null,
"mini_toc": null,
"minitoc": null,
"modification": null,
"now-assist-app-gen-video": null,
"order": null,
"page-type": null,
"page-type ": null,
"prodname": null,
"product": null,
"product_name": null,
"release": null,
"resourceID": null,
"roles": null,
"route_page": null,
"route_params_listId": null,
"route_params_table": null,
"route_params_type": null,
"route_type": null,
"setconfigurationproperties": null,
"topic": null,
"translation-type": "source",
"version": null,
"workflow": "Customer and Industry",
"workplace-srvc-delvry-ditamap": null
},
"page_id": "product/tmt-telecom-service-operations-mgt/reference/properties-installed-with-nokia-altiplano.html",
"page_key": 55686957,
"preprocessed_PDF": "https://downloads.docs.servicenow.com/pdf/enus/servicenow-zurich-telecom-service-ops-enus.pdf",
"rating": null,
"read_time_data": {
"char_count": 1361,
"img_count": 0,
"read_time": 1,
"video_links": [
""
],
"word_count": 165
},
"related_links": [
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "The Service Graph Connector for Nokia Altiplano offers a telecom-aware integration that brings real-time network inventory from the Nokia Altiplano Access Network SDN Controller into your ServiceNow CMDB.",
"title": "Telecom Discovery via Nokia Altiplano",
"topic": "/product/tmt-telecom-service-operations-mgt/concept/service-graph-connector-for-nokia-altiplano.html",
"type": "concept",
"url": null
},
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "Configure the Nokia Altiplano service graph connector to import physical and logical inventory data from the Nokia Altiplano Access Network SDN Controller into your ServiceNow Configuration Management Database (CMDB).",
"title": "Configuring Nokia Altiplano service graph connector",
"topic": "/product/tmt-telecom-service-operations-mgt/concept/configuring-service-graph-connector-nokia-altiplano.html",
"type": "concept",
"url": null
}
],
"search_title": null,
"title": "System components installed with Nokia Altiplano",
"topic_cluster": {
"clustered_by": {
"enabled": true,
"primary_key": "versions",
"primary_sort": "top-down",
"type": "subjecthead"
},
"clustered_labels": [
"versions"
],
"clustered_topics": [],
"clustering_title": "Zurich"
},
"topic_html": "<article class=\"hascomments\" data-page=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/reference/properties-installed-with-nokia-altiplano.html\" id=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/reference/properties-installed-with-nokia-altiplano.html\"><body id=\"properties-installed-with-nokia-altiplano\"><main role=\"main\"><article role=\"article\" class=\"dita\" id=\"properties-installed-with-nokia-altiplano\" aria-labelledby=\"title_properties-installed-with-nokia-altiplano\">\n <h1 class=\"title topictitle1\" id=\"title_properties-installed-with-nokia-altiplano\">System components installed with Nokia Altiplano</h1>\n \n \n <div class=\"body refbody\"><p class=\"shortdesc\">System properties control how the connector operates, including discovery options and performance settings.</p>\n <div class=\"table-wrap\"><table count-columns=\"2\" class=\"table\" id=\"properties-installed-with-nokia-altiplano__table_ghf_tcy_vfc\"><caption><span class=\"table--title-label\">Table 1. </span><span class=\"title\">Properties installed with Nokia Altiplano</span></caption><colgroup><col/><col/></colgroup><thead class=\"thead\">\n <tr class=\"row\">\n <th class=\"entry\" id=\"properties-installed-with-nokia-altiplano__table_ghf_tcy_vfc__entry__1\">Property</th>\n <th class=\"entry\" id=\"properties-installed-with-nokia-altiplano__table_ghf_tcy_vfc__entry__2\">Description</th>\n </tr>\n </thead><tbody class=\"tbody\">\n <tr class=\"row\">\n <td class=\"entry\" headers=\"properties-installed-with-nokia-altiplano__table_ghf_tcy_vfc__entry__1\"><span class=\"keyword parmname\">sn_sgc_altiplano.enable_onu_discovery</span></td>\n <td class=\"entry\" headers=\"properties-installed-with-nokia-altiplano__table_ghf_tcy_vfc__entry__2\">Enable or disable discovery of ONU devices and logical connections between OLT and ONU. <ul class=\"ul\" id=\"properties-installed-with-nokia-altiplano__ul_lpn_4fc_wfc\">\n <li class=\"li\">Default value: True</li>\n <li class=\"li\">Location: <span class=\"ph uicontrol\">All</span>><span class=\"ph uicontrol\">Service Graph Connectors</span>><span class=\"ph uicontrol\">Nokia Altiplano</span>><span class=\"ph uicontrol\">Properties</span> or <span class=\"ph uicontrol\">System Properties</span> [sys_properties]\n table filtering by the name ‘*altiplano’</li>\n </ul></td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry\" headers=\"properties-installed-with-nokia-altiplano__table_ghf_tcy_vfc__entry__1\"><span class=\"keyword parmname\">sn_sgc_altiplano.devices_list_batch_size</span></td>\n <td class=\"entry\" headers=\"properties-installed-with-nokia-altiplano__table_ghf_tcy_vfc__entry__2\">Controls the batch size for Altiplano REST API calls.<ul class=\"ul\" id=\"properties-installed-with-nokia-altiplano__ul_yft_wfc_wfc\">\n <li class=\"li\">Default value: 1000</li>\n <li class=\"li\">Location: <span class=\"ph uicontrol\">All</span>><span class=\"ph uicontrol\">Service Graph Connectors</span>><span class=\"ph uicontrol\">Nokia Altiplano</span>><span class=\"ph uicontrol\">Properties</span> or <span class=\"ph uicontrol\">System Properties</span> [sys_properties]\n table filtering by the name ‘*altiplano’</li>\n </ul></td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry\" headers=\"properties-installed-with-nokia-altiplano__table_ghf_tcy_vfc__entry__1\"><span class=\"keyword parmname\">sn_sgc_altiplano.parallel_number_of_data_source_jobs</span></td>\n <td class=\"entry\" headers=\"properties-installed-with-nokia-altiplano__table_ghf_tcy_vfc__entry__2\">Number of parallel jobs for collecting Altiplano data (requires "Enable parallel loading" setting).<ul class=\"ul\" id=\"properties-installed-with-nokia-altiplano__ul_ont_xfc_wfc\">\n <li class=\"li\">Default value: 2</li>\n <li class=\"li\">Location: <span class=\"ph uicontrol\">All</span>><span class=\"ph uicontrol\">Service Graph Connectors</span>><span class=\"ph uicontrol\">Nokia Altiplano</span>><span class=\"ph uicontrol\">Properties</span> or <span class=\"ph uicontrol\">System Properties</span> [sys_properties]\n table filtering by the name ‘*altiplano’</li>\n </ul></td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry\" headers=\"properties-installed-with-nokia-altiplano__table_ghf_tcy_vfc__entry__1\"><span class=\"keyword parmname\">sn_sgc_altiplano.onu_ci_class</span></td>\n <td class=\"entry\" headers=\"properties-installed-with-nokia-altiplano__table_ghf_tcy_vfc__entry__2\">Defines whether ONUs are stored as <code class=\"ph codeph\">ONU</code> or <code class=\"ph codeph\">ONT</code> CI class. <ul class=\"ul\" id=\"properties-installed-with-nokia-altiplano__ul_fgp_yfc_wfc\">\n <li class=\"li\">Default value: ONU</li>\n <li class=\"li\">Location: <span class=\"ph uicontrol\">All</span>><span class=\"ph uicontrol\">Service Graph Connectors</span>><span class=\"ph uicontrol\">Nokia Altiplano</span>><span class=\"ph uicontrol\">Properties</span> or <span class=\"ph uicontrol\">System Properties</span> [sys_properties]\n table filtering by the name ‘*altiplano’</li>\n </ul></td>\n </tr>\n </tbody></table></div>\n </div>\n <nav role=\"navigation\"></nav><nav role=\"navigation\" class=\"tasksNavigation\"></nav><nav role=\"navigation\" class=\"related-links\"><div class=\"col-md-4\"><dt>Related concepts</dt><dd><ul><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept/service-graph-connector-for-nokia-altiplano.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/service-graph-connector-for-nokia-altiplano.html\" class=\"link\" title=\"The Service Graph Connector for Nokia Altiplano offers a telecom-aware integration that brings real-time network inventory from the Nokia Altiplano Access Network SDN Controller into your ServiceNow CMDB.\">Telecom Discovery via Nokia Altiplano</a></li><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept/configuring-service-graph-connector-nokia-altiplano.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/configuring-service-graph-connector-nokia-altiplano.html\" class=\"link\" title=\"Configure the Nokia Altiplano service graph connector to import physical and logical inventory data from the Nokia Altiplano Access Network SDN Controller into your ServiceNow Configuration Management Database (CMDB).\">Configuring Nokia Altiplano service graph connector</a></li></ul></dd></div></nav>\n</article></main></body></article>",
"topic_language": "enus",
"views": 0,
"your_rating": null
} | # System components installed with Nokia Altiplano
System properties control how the connector operates, including discovery options and performance settings.
Table 1. Properties installed with Nokia Altiplano
| Property | Description |
| --- | --- |
| sn\_sgc\_altiplano.enable\_onu\_discovery | Enable or disable discovery of ONU devices and logical connections between OLT and ONU. * Default value: True * Location: All>Service Graph Connectors>Nokia Altiplano>Properties or System Properties [sys\_properties] table filtering by the name ‘*altiplano’ |
| sn\_sgc\_altiplano.devices\_list\_batch\_size | Controls the batch size for Altiplano REST API calls. * Default value: 1000 * Location: All>Service Graph Connectors>Nokia Altiplano>Properties or System Properties [sys\_properties] table filtering by the name ‘*altiplano’ |
| sn\_sgc\_altiplano.parallel\_number\_of\_data\_source\_jobs | Number of parallel jobs for collecting Altiplano data (requires "Enable parallel loading" setting). * Default value: 2 * Location: All>Service Graph Connectors>Nokia Altiplano>Properties or System Properties [sys\_properties] table filtering by the name ‘*altiplano’ |
| sn\_sgc\_altiplano.onu\_ci\_class | Defines whether ONUs are stored as `ONU` or `ONT` CI class. * Default value: ONU * Location: All>Service Graph Connectors>Nokia Altiplano>Properties or System Properties [sys\_properties] table filtering by the name ‘*altiplano’ |
| ---
title: System components installed with Nokia Altiplano
description: System properties control how the connector operates, including discovery
options and performance settings.
keywords: []
breadcrumbs:
- Telecommunications Service Operations Management
- Telecommunications Service Operations Management reference
---
# System components installed with Nokia Altiplano
System properties control how the connector operates, including discovery options and performance settings.
Table 1. Properties installed with Nokia Altiplano
| Property | Description |
| --- | --- |
| sn\_sgc\_altiplano.enable\_onu\_discovery | Enable or disable discovery of ONU devices and logical connections between OLT and ONU. * Default value: True * Location: All>Service Graph Connectors>Nokia Altiplano>Properties or System Properties [sys\_properties] table filtering by the name ‘*altiplano’ |
| sn\_sgc\_altiplano.devices\_list\_batch\_size | Controls the batch size for Altiplano REST API calls. * Default value: 1000 * Location: All>Service Graph Connectors>Nokia Altiplano>Properties or System Properties [sys\_properties] table filtering by the name ‘*altiplano’ |
| sn\_sgc\_altiplano.parallel\_number\_of\_data\_source\_jobs | Number of parallel jobs for collecting Altiplano data (requires "Enable parallel loading" setting). * Default value: 2 * Location: All>Service Graph Connectors>Nokia Altiplano>Properties or System Properties [sys\_properties] table filtering by the name ‘*altiplano’ |
| sn\_sgc\_altiplano.onu\_ci\_class | Defines whether ONUs are stored as `ONU` or `ONT` CI class. * Default value: ONU * Location: All>Service Graph Connectors>Nokia Altiplano>Properties or System Properties [sys\_properties] table filtering by the name ‘*altiplano’ |
|
https://www.servicenow.com/docs/en-US/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/classifying-xnfs-cisco-switch-pattern.html | https://servicenow-be-prod.servicenow.com/api/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/classifying-xnfs-cisco-switch-pattern.html | 2025-08-02 | daily | 0.5 | 268.xml | en-US | zurich-telecom-service-ops | product/tmt-telecom-service-operations-mgt/task/classifying-xnfs-cisco-switch-pattern.html | zurich | Classifying xNFs for Telecom Cisco Switch Pattern | To access a full list of OIDs that will be classified. | [] | [
"Telecommunications Service Operations Management",
"Using Telecommunications Service Operations Management",
"Using Telecom Discovery patterns"
] | <article class="hascomments" data-page="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/classifying-xnfs-cisco-switch-pattern.html" id="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/classifying-xnfs-cisco-switch-pattern.html"><body id="classifying-xnfs-cisco-switch-pattern"><main role="main"><article role="article" class="dita" id="classifying-xnfs-cisco-switch-pattern" aria-labelledby="title_classifying-xnfs-cisco-switch-pattern">
<h1 class="title topictitle1" id="title_classifying-xnfs-cisco-switch-pattern">Classifying xNFs for Telecom Cisco Switch Pattern</h1>
<div class="body taskbody"><p class="shortdesc">To access a full list of OIDs that will be classified.</p>
<section class="section prereq" id="classifying-xnfs-cisco-switch-pattern__task-prereq"><div class="tasklabel"><p class="sectiontitle tasklabel">Before you begin</p></div>
<p class="p">Role required: admin</p>
<p class="p">Classifier name: <span class="ph uicontrol">Standard Network Switch</span>.</p>
</section>
<section><div class="tasklabel"><p class="sectiontitle tasklabel">Procedure</p></div><ol class="ol steps"><li class="li step stepexpand">
<span class="ph cmd">Navigate to <span class="ph menucascade"><span class="ph uicontrol">All</span><abbr> > </abbr><span class="ph uicontrol">Discovery Definition</span><abbr> > </abbr><span class="ph uicontrol">CI Classification</span><abbr> > </abbr><span class="ph uicontrol">SNMP</span></span>.</span>
</li><li class="li step stepexpand">
<span class="ph cmd">From the list, select <span class="ph uicontrol">Standard Network Switch</span>.</span>
</li><li class="li step stepexpand">
<span class="ph cmd">Open the tab <span class="ph uicontrol">SNMP OID Classifications</span> and see the list of OIDs.<img src="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/../images/telecom-cisco-switch-classification.png?_LANG=enus" class="image" id="classifying-xnfs-cisco-switch-pattern__image_ols_lt3_b2c" alt="snmp classification."/></span>
<div class="itemgroup info">
<div class="note note note_note"><span class="note__title">Note:</span>
<p class="p">For more information on how to add additional OIDs to the classifier, see <a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/concept/telecom-discovery-using-telecommunication-discovery-pattern.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/telecom-discovery-using-telecommunication-discovery-pattern.html" class="xref" title="The Telecommunications Discovery Patterns plugin (also known as TSOM Patterns) extends ServiceNow AI Platform Telecom Discovery to support direct discovery of standalone network elements—such as routers and switches—without relying on traditional network management systems. These patterns enable Communication Service Providers (CSPs) to identify and map multivendor xNFs using protocols like SNMP and CLI, with support for NETCONF.">Direct Discovery using Discovery Patterns</a>.</p>
</div>
<div class="p">The List of Specific OIDs to call this Pattern:<div class="table-wrap"><table count-columns="4" class="table frame-all" id="classifying-xnfs-cisco-switch-pattern__table_lfm_s4f_b2c"><caption></caption><colgroup><col style="width:66"/><col style="width:123"/><col style="width:189"/><col style="width:227"/></colgroup><tbody class="tbody">
<tr class="row">
<td class="entry colsep-1 rowsep-1"><strong class="ph b">Vendor</strong></td>
<td class="entry colsep-1 rowsep-1"><strong class="ph b">Model</strong></td>
<td class="entry colsep-1 rowsep-1"><strong class="ph b">OID</strong></td>
<td class="entry colsep-1 rowsep-1"><strong class="ph b">Pattern</strong></td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1">Cisco</td>
<td class="entry colsep-1 rowsep-1">Nexus 9000</td>
<td class="entry colsep-1 rowsep-1">1.3.6.1.4.1.9.12.3.1.3.1954</td>
<td class="entry colsep-1 rowsep-1">Telecom Cisco Switch</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1">Cisco</td>
<td class="entry colsep-1 rowsep-1">Nexus 3548</td>
<td class="entry colsep-1 rowsep-1">1.3.6.1.4.1.9.12.3.1.3.1666</td>
<td class="entry colsep-1 rowsep-1">Telecom Cisco Switch</td>
</tr>
</tbody></table></div></div>
<div class="p">MiB Tables Used on an xNF:<ul class="ul" id="classifying-xnfs-cisco-switch-pattern__ul_jzh_t4f_b2c">
<li class="li">SystemMIB</li>
<li class="li">EntityPhysicalMIB</li>
<li class="li">IfMIB</li>
<li class="li">IfXMIB</li>
<li class="li">IpMIB</li>
</ul></div>
</div>
</li></ol></section>
</div>
<nav role="navigation"></nav><nav role="navigation" class="tasksNavigation"></nav><nav role="navigation" class="related-links"></nav></article></main></body></article> | {
"attachments": {
"all_attachments": null,
"topic_attachments": []
},
"available_languages": [
"enus"
],
"breadcrumbs": [
{
"title": "Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html"
},
{
"title": "Using Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/using-tsom.html"
},
{
"title": "Using Telecom Discovery patterns",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/using-telecom-discovery-patterns.html"
}
],
"breadcrumbs_html": "<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops\">Zurich Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html\">Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/using-tsom.html\">Using Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/using-telecom-discovery-patterns.html\">Using Telecom Discovery patterns</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<span class=\"active\">Classifying xNFs for Telecom Cisco Switch Pattern</span>",
"bundle_id": "zurich-telecom-service-ops",
"bundle_key": 2733,
"bundle_landing_page": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html",
"bundle_subtitle": null,
"bundle_title": "Zurich Telecommunications Service Operations Management",
"canonical_link": null,
"dates": {
"Added on": "2025-08-02T00:48:08.794016Z",
"Created on": "2025-01-16T00:00:00Z",
"Initial upload": "2025-07-30T22:24:33.519043Z",
"Updated on": "2025-07-31T00:00:00Z"
},
"dislike_url": "https://servicenow-be-prod.servicenow.com/dislike/55686959",
"dislikes": 0,
"es_archived_content": false,
"is_in_fav": false,
"is_liked": null,
"is_watched": false,
"keywords": [
" zurich zurich"
],
"labels": [
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "zurich",
"navtitle": "Zurich",
"outputclasses": [],
"subjectHeadId": "versions",
"subjectheadNavtitle": "Versions",
"visibility": "show-facet"
},
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "tsom",
"navtitle": "Telecommunications Service Operations Management",
"outputclasses": [],
"subjectHeadId": "products",
"subjectheadNavtitle": "Products",
"visibility": "show-facet"
}
],
"labels_text": "Versions > Zurich; Products > CRM and Industry Products > Telecommunications Media and Technology Assurance > Telecommunications Service Operations Management",
"like_url": "https://servicenow-be-prod.servicenow.com/like/55686959",
"likes": 0,
"metadata": {
"AI Search": null,
"AI Search Assist": null,
"Application Insights": null,
"Capabilities": null,
"Code Signing": null,
"Contextual Search": null,
"DC.contributor": null,
"DC.coverage": null,
"DC.creator": "ServiceNow",
"DC.date.created": "2025-01-16T22:54:27+05:30",
"DC.date.modified": "2025-07-31",
"DC.format": "HTML5",
"DC.identifier": "classifying-xnfs-cisco-switch-pattern",
"DC.language": null,
"DC.relation": "../../../product/tmt-telecom-service-operations-mgt/concept/using-telecom-discovery-patterns.html",
"DC.rights.owner": "(C) Copyright 2025",
"DC.subject": null,
"DC.type": "task",
"Data Discovery": null,
"Data Policy": null,
"Data Privacy": null,
"Discovery": null,
"External Content for AI Search": null,
"Field Administration": null,
"Field Normalization": null,
"Key Management Framework": null,
"Localization Framework": null,
"Now Platform": null,
"PlatSec": null,
"Platform": null,
"Platform Administration": null,
"Platform Performance": null,
"Platform Privacy": null,
"Proactive Triggers": null,
"Process Optimization": null,
"RN doc editing record number": null,
"Search Administration": null,
"Secrets Management": null,
"ServiceNow AI Platform": null,
"State Model": null,
"Subscription Management": null,
"Task Communications Management": null,
"Timeline Visualizations": null,
"User Administration": null,
"User Experience Analytics": null,
"Zing": null,
"ai-now-assist": null,
"app-name": null,
"app_route": null,
"azureapimanagemen": null,
"change-completed": null,
"change-item": null,
"change-request-id": null,
"change-request-reference": null,
"com.glide.embedded_help.category": null,
"component": null,
"copyright": "(C) Copyright 2025",
"crossroads": null,
"data": null,
"description": "To access a full list of OIDs that will be classified.",
"dominant_bundle": null,
"erp-canvas-video": null,
"fsm-mobile": null,
"fsm-route": null,
"fsm-sched-opt": null,
"fsm-wrk-order": null,
"genai-round-7": null,
"generator": "DITA-OT",
"glossPartOfSpeech": null,
"glossStatus": null,
"guided setup": null,
"guided tours": null,
"keywords": null,
"min-toc": null,
"mini": null,
"mini-to truec": null,
"mini-toc": null,
"mini_toc": null,
"minitoc": null,
"modification": null,
"now-assist-app-gen-video": null,
"order": null,
"page-type": null,
"page-type ": null,
"prodname": null,
"product": null,
"product_name": null,
"release": null,
"resourceID": null,
"roles": null,
"route_page": null,
"route_params_listId": null,
"route_params_table": null,
"route_params_type": null,
"route_type": null,
"setconfigurationproperties": null,
"topic": null,
"translation-type": "source",
"version": null,
"workflow": "Customer and Industry",
"workplace-srvc-delvry-ditamap": null
},
"page_id": "product/tmt-telecom-service-operations-mgt/task/classifying-xnfs-cisco-switch-pattern.html",
"page_key": 55686959,
"preprocessed_PDF": "https://downloads.docs.servicenow.com/pdf/enus/servicenow-zurich-telecom-service-ops-enus.pdf",
"rating": null,
"read_time_data": {
"char_count": 728,
"img_count": 1,
"read_time": 1,
"video_links": [
""
],
"word_count": 114
},
"related_links": [],
"search_title": null,
"title": "Classifying xNFs for Telecom Cisco Switch Pattern",
"topic_cluster": {
"clustered_by": {
"enabled": true,
"primary_key": "versions",
"primary_sort": "top-down",
"type": "subjecthead"
},
"clustered_labels": [
"versions"
],
"clustered_topics": [],
"clustering_title": "Zurich"
},
"topic_html": "<article class=\"hascomments\" data-page=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/classifying-xnfs-cisco-switch-pattern.html\" id=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/classifying-xnfs-cisco-switch-pattern.html\"><body id=\"classifying-xnfs-cisco-switch-pattern\"><main role=\"main\"><article role=\"article\" class=\"dita\" id=\"classifying-xnfs-cisco-switch-pattern\" aria-labelledby=\"title_classifying-xnfs-cisco-switch-pattern\">\n <h1 class=\"title topictitle1\" id=\"title_classifying-xnfs-cisco-switch-pattern\">Classifying xNFs for Telecom Cisco Switch Pattern</h1>\n \n \n <div class=\"body taskbody\"><p class=\"shortdesc\">To access a full list of OIDs that will be classified.</p>\n <section class=\"section prereq\" id=\"classifying-xnfs-cisco-switch-pattern__task-prereq\"><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">Before you begin</p></div>\n <p class=\"p\">Role required: admin</p>\n <p class=\"p\">Classifier name: <span class=\"ph uicontrol\">Standard Network Switch</span>.</p>\n </section>\n <section><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">Procedure</p></div><ol class=\"ol steps\"><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">Navigate to <span class=\"ph menucascade\"><span class=\"ph uicontrol\">All</span><abbr> > </abbr><span class=\"ph uicontrol\">Discovery Definition</span><abbr> > </abbr><span class=\"ph uicontrol\">CI Classification</span><abbr> > </abbr><span class=\"ph uicontrol\">SNMP</span></span>.</span>\n </li><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">From the list, select <span class=\"ph uicontrol\">Standard Network Switch</span>.</span>\n </li><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">Open the tab <span class=\"ph uicontrol\">SNMP OID Classifications</span> and see the list of OIDs.<img src=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/../images/telecom-cisco-switch-classification.png?_LANG=enus\" class=\"image\" id=\"classifying-xnfs-cisco-switch-pattern__image_ols_lt3_b2c\" alt=\"snmp classification.\"/></span>\n <div class=\"itemgroup info\">\n <div class=\"note note note_note\"><span class=\"note__title\">Note:</span> \n <p class=\"p\">For more information on how to add additional OIDs to the classifier, see <a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept/telecom-discovery-using-telecommunication-discovery-pattern.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/telecom-discovery-using-telecommunication-discovery-pattern.html\" class=\"xref\" title=\"The Telecommunications Discovery Patterns plugin (also known as TSOM Patterns) extends ServiceNow AI Platform Telecom Discovery to support direct discovery of standalone network elements—such as routers and switches—without relying on traditional network management systems. These patterns enable Communication Service Providers (CSPs) to identify and map multivendor xNFs using protocols like SNMP and CLI, with support for NETCONF.\">Direct Discovery using Discovery Patterns</a>.</p>\n </div>\n <div class=\"p\">The List of Specific OIDs to call this Pattern:<div class=\"table-wrap\"><table count-columns=\"4\" class=\"table frame-all\" id=\"classifying-xnfs-cisco-switch-pattern__table_lfm_s4f_b2c\"><caption></caption><colgroup><col style=\"width:66\"/><col style=\"width:123\"/><col style=\"width:189\"/><col style=\"width:227\"/></colgroup><tbody class=\"tbody\">\n <tr class=\"row\">\n <td class=\"entry colsep-1 rowsep-1\"><strong class=\"ph b\">Vendor</strong></td>\n <td class=\"entry colsep-1 rowsep-1\"><strong class=\"ph b\">Model</strong></td>\n <td class=\"entry colsep-1 rowsep-1\"><strong class=\"ph b\">OID</strong></td>\n <td class=\"entry colsep-1 rowsep-1\"><strong class=\"ph b\">Pattern</strong></td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry colsep-1 rowsep-1\">Cisco</td>\n <td class=\"entry colsep-1 rowsep-1\">Nexus 9000</td>\n <td class=\"entry colsep-1 rowsep-1\">1.3.6.1.4.1.9.12.3.1.3.1954</td>\n <td class=\"entry colsep-1 rowsep-1\">Telecom Cisco Switch</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry colsep-1 rowsep-1\">Cisco</td>\n <td class=\"entry colsep-1 rowsep-1\">Nexus 3548</td>\n <td class=\"entry colsep-1 rowsep-1\">1.3.6.1.4.1.9.12.3.1.3.1666</td>\n <td class=\"entry colsep-1 rowsep-1\">Telecom Cisco Switch</td>\n </tr>\n </tbody></table></div></div>\n <div class=\"p\">MiB Tables Used on an xNF:<ul class=\"ul\" id=\"classifying-xnfs-cisco-switch-pattern__ul_jzh_t4f_b2c\">\n <li class=\"li\">SystemMIB</li>\n <li class=\"li\">EntityPhysicalMIB</li>\n <li class=\"li\">IfMIB</li>\n <li class=\"li\">IfXMIB</li>\n <li class=\"li\">IpMIB</li>\n </ul></div>\n </div>\n </li></ol></section>\n </div>\n<nav role=\"navigation\"></nav><nav role=\"navigation\" class=\"tasksNavigation\"></nav><nav role=\"navigation\" class=\"related-links\"></nav></article></main></body></article>",
"topic_language": "enus",
"views": 0,
"your_rating": null
} | # Classifying xNFs for Telecom Cisco Switch Pattern
To access a full list of OIDs that will be classified.
## Before you begin
Role required: admin
Classifier name: Standard Network Switch.
## Procedure
1. Navigate to All > Discovery Definition > CI Classification > SNMP.
2. From the list, select Standard Network Switch.
3. Open the tab SNMP OID Classifications and see the list of OIDs.
Note:
For more information on how to add additional OIDs to the classifier, see Direct Discovery using Discovery Patterns.
The List of Specific OIDs to call this Pattern:
| **Vendor** | **Model** | **OID** | **Pattern** |
| --- | --- | --- | --- |
| Cisco | Nexus 9000 | 1.3.6.1.4.1.9.12.3.1.3.1954 | Telecom Cisco Switch |
| Cisco | Nexus 3548 | 1.3.6.1.4.1.9.12.3.1.3.1666 | Telecom Cisco Switch |
MiB Tables Used on an xNF:
* SystemMIB
* EntityPhysicalMIB
* IfMIB
* IfXMIB
* IpMIB
| ---
title: Classifying xNFs for Telecom Cisco Switch Pattern
description: To access a full list of OIDs that will be classified.
keywords: []
breadcrumbs:
- Telecommunications Service Operations Management
- Using Telecommunications Service Operations Management
- Using Telecom Discovery patterns
---
# Classifying xNFs for Telecom Cisco Switch Pattern
To access a full list of OIDs that will be classified.
## Before you begin
Role required: admin
Classifier name: Standard Network Switch.
## Procedure
1. Navigate to All > Discovery Definition > CI Classification > SNMP.
2. From the list, select Standard Network Switch.
3. Open the tab SNMP OID Classifications and see the list of OIDs.
Note:
For more information on how to add additional OIDs to the classifier, see Direct Discovery using Discovery Patterns.
The List of Specific OIDs to call this Pattern:
| **Vendor** | **Model** | **OID** | **Pattern** |
| --- | --- | --- | --- |
| Cisco | Nexus 9000 | 1.3.6.1.4.1.9.12.3.1.3.1954 | Telecom Cisco Switch |
| Cisco | Nexus 3548 | 1.3.6.1.4.1.9.12.3.1.3.1666 | Telecom Cisco Switch |
MiB Tables Used on an xNF:
* SystemMIB
* EntityPhysicalMIB
* IfMIB
* IfXMIB
* IpMIB
|
https://www.servicenow.com/docs/en-US/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/classifying-xnfs-juniper-router-pattern.html | https://servicenow-be-prod.servicenow.com/api/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/classifying-xnfs-juniper-router-pattern.html | 2025-08-02 | daily | 0.5 | 268.xml | en-US | zurich-telecom-service-ops | product/tmt-telecom-service-operations-mgt/task/classifying-xnfs-juniper-router-pattern.html | zurich | Classifying xNFs for Telecom Juniper MX SSH Router Pattern | To access a full list of OIDs that will be classified. | [] | [
"Telecommunications Service Operations Management",
"Using Telecommunications Service Operations Management",
"Using Telecom Discovery patterns"
] | <article class="hascomments" data-page="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/classifying-xnfs-juniper-router-pattern.html" id="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/classifying-xnfs-juniper-router-pattern.html"><body id="classifying-xnfs-juniper-router-pattern"><main role="main"><article role="article" class="dita" id="classifying-xnfs-juniper-router-pattern" aria-labelledby="title_classifying-xnfs-juniper-router-pattern">
<h1 class="title topictitle1" id="title_classifying-xnfs-juniper-router-pattern">Classifying xNFs for Telecom Juniper MX SSH Router Pattern</h1>
<div class="body taskbody"><p class="shortdesc">To access a full list of OIDs that will be classified.</p>
<section class="section prereq" id="classifying-xnfs-juniper-router-pattern__task-prereq"><div class="tasklabel"><p class="sectiontitle tasklabel">Before you begin</p></div>
<p class="p">Role required: admin</p>
<p class="p">Classifier name: <span class="ph uicontrol">Standard Network Router</span>.</p>
</section>
<section><div class="tasklabel"><p class="sectiontitle tasklabel">Procedure</p></div><ol class="ol steps"><li class="li step stepexpand">
<span class="ph cmd">Navigate to <span class="ph menucascade"><span class="ph uicontrol">All</span><abbr> > </abbr><span class="ph uicontrol">Discovery Definition</span><abbr> > </abbr><span class="ph uicontrol">CI Classification</span><abbr> > </abbr><span class="ph uicontrol">SNMP</span></span>.</span>
</li><li class="li step stepexpand">
<span class="ph cmd">From the list, select <span class="ph uicontrol">Standard Network Router</span>.</span>
</li><li class="li step stepexpand">
<span class="ph cmd">Open the tab <span class="ph uicontrol">SNMP OID Classifications</span> and see the list of OIDs.<img src="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/../images/telecom-juniper-classification.png?_LANG=enus" class="image" id="classifying-xnfs-juniper-router-pattern__image_eyr_dr3_b2c" alt="snmp oid classifications."/></span>
<div class="itemgroup info">
<div class="note note note_note"><span class="note__title">Note:</span>
<p class="p">For more information on how to add additional OIDs to the classifier, see <a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/concept/telecom-discovery-using-telecommunication-discovery-pattern.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/telecom-discovery-using-telecommunication-discovery-pattern.html" class="xref" title="The Telecommunications Discovery Patterns plugin (also known as TSOM Patterns) extends ServiceNow AI Platform Telecom Discovery to support direct discovery of standalone network elements—such as routers and switches—without relying on traditional network management systems. These patterns enable Communication Service Providers (CSPs) to identify and map multivendor xNFs using protocols like SNMP and CLI, with support for NETCONF.">Direct Discovery using Discovery Patterns</a>.</p>
</div>
<div class="p">The List of Specific OIDs to call this Pattern:<div class="table-wrap"><table count-columns="4" class="table frame-all" id="classifying-xnfs-juniper-router-pattern__table_cfq_qmf_b2c"><caption></caption><colgroup><col style="width:107"/><col style="width:127"/><col style="width:218"/><col style="width:171"/></colgroup><tbody class="tbody">
<tr class="row">
<td class="entry colsep-1 rowsep-1"><strong class="ph b">Vendor</strong></td>
<td class="entry colsep-1 rowsep-1"><strong class="ph b">Model</strong></td>
<td class="entry colsep-1 rowsep-1"><strong class="ph b">OID</strong></td>
<td class="entry colsep-1 rowsep-1"><strong class="ph b">Pattern</strong></td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1">Juniper</td>
<td class="entry colsep-1 rowsep-1">MX80</td>
<td class="entry colsep-1 rowsep-1">1.3.6.1.4.1.2636.1.1.1.2.57</td>
<td class="entry colsep-1 rowsep-1">Telecom Juniper MX SSH Router</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1">Juniper</td>
<td class="entry colsep-1 rowsep-1">MX104</td>
<td class="entry colsep-1 rowsep-1">1.3.6.1.4.1.2636.1.1.1.2.97</td>
<td class="entry colsep-1 rowsep-1">Telecom Juniper MX SSH Router</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1">Juniper</td>
<td class="entry colsep-1 rowsep-1">MX240</td>
<td class="entry colsep-1 rowsep-1">1.3.6.1.4.1.2636.1.1.1.2.29</td>
<td class="entry colsep-1 rowsep-1">Telecom Juniper MX SSH Router</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1">Juniper</td>
<td class="entry colsep-1 rowsep-1">MX480</td>
<td class="entry colsep-1 rowsep-1">1.3.6.1.4.1.2636.1.1.1.2.25</td>
<td class="entry colsep-1 rowsep-1">Telecom Juniper MX SSH Router</td>
</tr>
</tbody></table></div></div>
<p class="p">MiB Tables Used on an xNF: SystemMIB.</p>
<div class="p">CLI Commands Used.<ul class="ul" id="classifying-xnfs-juniper-router-pattern__ul_wl3_5mf_b2c">
<li class="li">show chassis hardware | no-more | display xml</li>
<li class="li">show interface media | no-more | display xml</li>
</ul></div>
</div>
</li></ol></section>
</div>
<nav role="navigation"></nav><nav role="navigation" class="tasksNavigation"></nav><nav role="navigation" class="related-links"></nav></article></main></body></article> | {
"attachments": {
"all_attachments": null,
"topic_attachments": []
},
"available_languages": [
"enus"
],
"breadcrumbs": [
{
"title": "Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html"
},
{
"title": "Using Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/using-tsom.html"
},
{
"title": "Using Telecom Discovery patterns",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/using-telecom-discovery-patterns.html"
}
],
"breadcrumbs_html": "<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops\">Zurich Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html\">Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/using-tsom.html\">Using Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/using-telecom-discovery-patterns.html\">Using Telecom Discovery patterns</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<span class=\"active\">Classifying xNFs for Telecom Juniper MX SSH Router Pattern</span>",
"bundle_id": "zurich-telecom-service-ops",
"bundle_key": 2733,
"bundle_landing_page": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html",
"bundle_subtitle": null,
"bundle_title": "Zurich Telecommunications Service Operations Management",
"canonical_link": null,
"dates": {
"Added on": "2025-08-02T00:48:08.794016Z",
"Created on": "2025-01-16T00:00:00Z",
"Initial upload": "2025-07-30T22:24:33.519043Z",
"Updated on": "2025-07-31T00:00:00Z"
},
"dislike_url": "https://servicenow-be-prod.servicenow.com/dislike/55686960",
"dislikes": 0,
"es_archived_content": false,
"is_in_fav": false,
"is_liked": null,
"is_watched": false,
"keywords": [
" zurich zurich"
],
"labels": [
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "zurich",
"navtitle": "Zurich",
"outputclasses": [],
"subjectHeadId": "versions",
"subjectheadNavtitle": "Versions",
"visibility": "show-facet"
},
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "tsom",
"navtitle": "Telecommunications Service Operations Management",
"outputclasses": [],
"subjectHeadId": "products",
"subjectheadNavtitle": "Products",
"visibility": "show-facet"
}
],
"labels_text": "Versions > Zurich; Products > CRM and Industry Products > Telecommunications Media and Technology Assurance > Telecommunications Service Operations Management",
"like_url": "https://servicenow-be-prod.servicenow.com/like/55686960",
"likes": 0,
"metadata": {
"AI Search": null,
"AI Search Assist": null,
"Application Insights": null,
"Capabilities": null,
"Code Signing": null,
"Contextual Search": null,
"DC.contributor": null,
"DC.coverage": null,
"DC.creator": "ServiceNow",
"DC.date.created": "2025-01-16T22:37:24+05:30",
"DC.date.modified": "2025-07-31",
"DC.format": "HTML5",
"DC.identifier": "classifying-xnfs-juniper-router-pattern",
"DC.language": null,
"DC.relation": "../../../product/tmt-telecom-service-operations-mgt/concept/using-telecom-discovery-patterns.html",
"DC.rights.owner": "(C) Copyright 2025",
"DC.subject": null,
"DC.type": "task",
"Data Discovery": null,
"Data Policy": null,
"Data Privacy": null,
"Discovery": null,
"External Content for AI Search": null,
"Field Administration": null,
"Field Normalization": null,
"Key Management Framework": null,
"Localization Framework": null,
"Now Platform": null,
"PlatSec": null,
"Platform": null,
"Platform Administration": null,
"Platform Performance": null,
"Platform Privacy": null,
"Proactive Triggers": null,
"Process Optimization": null,
"RN doc editing record number": null,
"Search Administration": null,
"Secrets Management": null,
"ServiceNow AI Platform": null,
"State Model": null,
"Subscription Management": null,
"Task Communications Management": null,
"Timeline Visualizations": null,
"User Administration": null,
"User Experience Analytics": null,
"Zing": null,
"ai-now-assist": null,
"app-name": null,
"app_route": null,
"azureapimanagemen": null,
"change-completed": null,
"change-item": null,
"change-request-id": null,
"change-request-reference": null,
"com.glide.embedded_help.category": null,
"component": null,
"copyright": "(C) Copyright 2025",
"crossroads": null,
"data": null,
"description": "To access a full list of OIDs that will be classified.",
"dominant_bundle": null,
"erp-canvas-video": null,
"fsm-mobile": null,
"fsm-route": null,
"fsm-sched-opt": null,
"fsm-wrk-order": null,
"genai-round-7": null,
"generator": "DITA-OT",
"glossPartOfSpeech": null,
"glossStatus": null,
"guided setup": null,
"guided tours": null,
"keywords": null,
"min-toc": null,
"mini": null,
"mini-to truec": null,
"mini-toc": null,
"mini_toc": null,
"minitoc": null,
"modification": null,
"now-assist-app-gen-video": null,
"order": null,
"page-type": null,
"page-type ": null,
"prodname": null,
"product": null,
"product_name": null,
"release": null,
"resourceID": null,
"roles": null,
"route_page": null,
"route_params_listId": null,
"route_params_table": null,
"route_params_type": null,
"route_type": null,
"setconfigurationproperties": null,
"topic": null,
"translation-type": "source",
"version": null,
"workflow": "Customer and Industry",
"workplace-srvc-delvry-ditamap": null
},
"page_id": "product/tmt-telecom-service-operations-mgt/task/classifying-xnfs-juniper-router-pattern.html",
"page_key": 55686960,
"preprocessed_PDF": "https://downloads.docs.servicenow.com/pdf/enus/servicenow-zurich-telecom-service-ops-enus.pdf",
"rating": null,
"read_time_data": {
"char_count": 957,
"img_count": 1,
"read_time": 1,
"video_links": [
""
],
"word_count": 147
},
"related_links": [],
"search_title": null,
"title": "Classifying xNFs for Telecom Juniper MX SSH Router Pattern",
"topic_cluster": {
"clustered_by": {
"enabled": true,
"primary_key": "versions",
"primary_sort": "top-down",
"type": "subjecthead"
},
"clustered_labels": [
"versions"
],
"clustered_topics": [],
"clustering_title": "Zurich"
},
"topic_html": "<article class=\"hascomments\" data-page=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/classifying-xnfs-juniper-router-pattern.html\" id=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/classifying-xnfs-juniper-router-pattern.html\"><body id=\"classifying-xnfs-juniper-router-pattern\"><main role=\"main\"><article role=\"article\" class=\"dita\" id=\"classifying-xnfs-juniper-router-pattern\" aria-labelledby=\"title_classifying-xnfs-juniper-router-pattern\">\n <h1 class=\"title topictitle1\" id=\"title_classifying-xnfs-juniper-router-pattern\">Classifying xNFs for Telecom Juniper MX SSH Router Pattern</h1>\n \n \n <div class=\"body taskbody\"><p class=\"shortdesc\">To access a full list of OIDs that will be classified.</p>\n <section class=\"section prereq\" id=\"classifying-xnfs-juniper-router-pattern__task-prereq\"><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">Before you begin</p></div>\n <p class=\"p\">Role required: admin</p>\n <p class=\"p\">Classifier name: <span class=\"ph uicontrol\">Standard Network Router</span>.</p>\n </section>\n <section><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">Procedure</p></div><ol class=\"ol steps\"><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">Navigate to <span class=\"ph menucascade\"><span class=\"ph uicontrol\">All</span><abbr> > </abbr><span class=\"ph uicontrol\">Discovery Definition</span><abbr> > </abbr><span class=\"ph uicontrol\">CI Classification</span><abbr> > </abbr><span class=\"ph uicontrol\">SNMP</span></span>.</span>\n </li><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">From the list, select <span class=\"ph uicontrol\">Standard Network Router</span>.</span>\n </li><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">Open the tab <span class=\"ph uicontrol\">SNMP OID Classifications</span> and see the list of OIDs.<img src=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/../images/telecom-juniper-classification.png?_LANG=enus\" class=\"image\" id=\"classifying-xnfs-juniper-router-pattern__image_eyr_dr3_b2c\" alt=\"snmp oid classifications.\"/></span>\n <div class=\"itemgroup info\">\n <div class=\"note note note_note\"><span class=\"note__title\">Note:</span> \n <p class=\"p\">For more information on how to add additional OIDs to the classifier, see <a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept/telecom-discovery-using-telecommunication-discovery-pattern.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/telecom-discovery-using-telecommunication-discovery-pattern.html\" class=\"xref\" title=\"The Telecommunications Discovery Patterns plugin (also known as TSOM Patterns) extends ServiceNow AI Platform Telecom Discovery to support direct discovery of standalone network elements—such as routers and switches—without relying on traditional network management systems. These patterns enable Communication Service Providers (CSPs) to identify and map multivendor xNFs using protocols like SNMP and CLI, with support for NETCONF.\">Direct Discovery using Discovery Patterns</a>.</p>\n </div>\n <div class=\"p\">The List of Specific OIDs to call this Pattern:<div class=\"table-wrap\"><table count-columns=\"4\" class=\"table frame-all\" id=\"classifying-xnfs-juniper-router-pattern__table_cfq_qmf_b2c\"><caption></caption><colgroup><col style=\"width:107\"/><col style=\"width:127\"/><col style=\"width:218\"/><col style=\"width:171\"/></colgroup><tbody class=\"tbody\">\n <tr class=\"row\">\n <td class=\"entry colsep-1 rowsep-1\"><strong class=\"ph b\">Vendor</strong></td>\n <td class=\"entry colsep-1 rowsep-1\"><strong class=\"ph b\">Model</strong></td>\n <td class=\"entry colsep-1 rowsep-1\"><strong class=\"ph b\">OID</strong></td>\n <td class=\"entry colsep-1 rowsep-1\"><strong class=\"ph b\">Pattern</strong></td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry colsep-1 rowsep-1\">Juniper</td>\n <td class=\"entry colsep-1 rowsep-1\">MX80</td>\n <td class=\"entry colsep-1 rowsep-1\">1.3.6.1.4.1.2636.1.1.1.2.57</td>\n <td class=\"entry colsep-1 rowsep-1\">Telecom Juniper MX SSH Router</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry colsep-1 rowsep-1\">Juniper</td>\n <td class=\"entry colsep-1 rowsep-1\">MX104</td>\n <td class=\"entry colsep-1 rowsep-1\">1.3.6.1.4.1.2636.1.1.1.2.97</td>\n <td class=\"entry colsep-1 rowsep-1\">Telecom Juniper MX SSH Router</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry colsep-1 rowsep-1\">Juniper</td>\n <td class=\"entry colsep-1 rowsep-1\">MX240</td>\n <td class=\"entry colsep-1 rowsep-1\">1.3.6.1.4.1.2636.1.1.1.2.29</td>\n <td class=\"entry colsep-1 rowsep-1\">Telecom Juniper MX SSH Router</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry colsep-1 rowsep-1\">Juniper</td>\n <td class=\"entry colsep-1 rowsep-1\">MX480</td>\n <td class=\"entry colsep-1 rowsep-1\">1.3.6.1.4.1.2636.1.1.1.2.25</td>\n <td class=\"entry colsep-1 rowsep-1\">Telecom Juniper MX SSH Router</td>\n </tr>\n </tbody></table></div></div>\n <p class=\"p\">MiB Tables Used on an xNF: SystemMIB.</p>\n <div class=\"p\">CLI Commands Used.<ul class=\"ul\" id=\"classifying-xnfs-juniper-router-pattern__ul_wl3_5mf_b2c\">\n <li class=\"li\">show chassis hardware | no-more | display xml</li>\n <li class=\"li\">show interface media | no-more | display xml</li>\n </ul></div>\n </div>\n </li></ol></section>\n </div>\n<nav role=\"navigation\"></nav><nav role=\"navigation\" class=\"tasksNavigation\"></nav><nav role=\"navigation\" class=\"related-links\"></nav></article></main></body></article>",
"topic_language": "enus",
"views": 0,
"your_rating": null
} | # Classifying xNFs for Telecom Juniper MX SSH Router Pattern
To access a full list of OIDs that will be classified.
## Before you begin
Role required: admin
Classifier name: Standard Network Router.
## Procedure
1. Navigate to All > Discovery Definition > CI Classification > SNMP.
2. From the list, select Standard Network Router.
3. Open the tab SNMP OID Classifications and see the list of OIDs.
Note:
For more information on how to add additional OIDs to the classifier, see Direct Discovery using Discovery Patterns.
The List of Specific OIDs to call this Pattern:
| **Vendor** | **Model** | **OID** | **Pattern** |
| --- | --- | --- | --- |
| Juniper | MX80 | 1.3.6.1.4.1.2636.1.1.1.2.57 | Telecom Juniper MX SSH Router |
| Juniper | MX104 | 1.3.6.1.4.1.2636.1.1.1.2.97 | Telecom Juniper MX SSH Router |
| Juniper | MX240 | 1.3.6.1.4.1.2636.1.1.1.2.29 | Telecom Juniper MX SSH Router |
| Juniper | MX480 | 1.3.6.1.4.1.2636.1.1.1.2.25 | Telecom Juniper MX SSH Router |
MiB Tables Used on an xNF: SystemMIB.
CLI Commands Used.
* show chassis hardware | no-more | display xml
* show interface media | no-more | display xml
| ---
title: Classifying xNFs for Telecom Juniper MX SSH Router Pattern
description: To access a full list of OIDs that will be classified.
keywords: []
breadcrumbs:
- Telecommunications Service Operations Management
- Using Telecommunications Service Operations Management
- Using Telecom Discovery patterns
---
# Classifying xNFs for Telecom Juniper MX SSH Router Pattern
To access a full list of OIDs that will be classified.
## Before you begin
Role required: admin
Classifier name: Standard Network Router.
## Procedure
1. Navigate to All > Discovery Definition > CI Classification > SNMP.
2. From the list, select Standard Network Router.
3. Open the tab SNMP OID Classifications and see the list of OIDs.
Note:
For more information on how to add additional OIDs to the classifier, see Direct Discovery using Discovery Patterns.
The List of Specific OIDs to call this Pattern:
| **Vendor** | **Model** | **OID** | **Pattern** |
| --- | --- | --- | --- |
| Juniper | MX80 | 1.3.6.1.4.1.2636.1.1.1.2.57 | Telecom Juniper MX SSH Router |
| Juniper | MX104 | 1.3.6.1.4.1.2636.1.1.1.2.97 | Telecom Juniper MX SSH Router |
| Juniper | MX240 | 1.3.6.1.4.1.2636.1.1.1.2.29 | Telecom Juniper MX SSH Router |
| Juniper | MX480 | 1.3.6.1.4.1.2636.1.1.1.2.25 | Telecom Juniper MX SSH Router |
MiB Tables Used on an xNF: SystemMIB.
CLI Commands Used.
* show chassis hardware | no-more | display xml
* show interface media | no-more | display xml
|
https://www.servicenow.com/docs/en-US/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/classifying-xnfs-pattern-switch-pattern.html | https://servicenow-be-prod.servicenow.com/api/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/classifying-xnfs-pattern-switch-pattern.html | 2025-08-02 | daily | 0.5 | 268.xml | en-US | zurich-telecom-service-ops | product/tmt-telecom-service-operations-mgt/task/classifying-xnfs-pattern-switch-pattern.html | zurich | Classifying xNFs for Telecom Switch Pattern | To access a full list of OIDs that will be classified. | [] | [
"Telecommunications Service Operations Management",
"Using Telecommunications Service Operations Management",
"Using Telecom Discovery patterns"
] | <article class="hascomments" data-page="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/classifying-xnfs-pattern-switch-pattern.html" id="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/classifying-xnfs-pattern-switch-pattern.html"><body id="classifying-xnfs-pattern-switch-pattern"><main role="main"><article role="article" class="dita" id="classifying-xnfs-pattern-switch-pattern" aria-labelledby="title_classifying-xnfs-pattern-switch-pattern">
<h1 class="title topictitle1" id="title_classifying-xnfs-pattern-switch-pattern">Classifying xNFs for Telecom Switch Pattern</h1>
<div class="body taskbody"><p class="shortdesc">To access a full list of OIDs that will be classified.</p>
<section class="section prereq" id="classifying-xnfs-pattern-switch-pattern__task-prereq"><div class="tasklabel"><p class="sectiontitle tasklabel">Before you begin</p></div>
<p class="p">Role required: admin</p>
<p class="p">Classifier name: <span class="ph uicontrol">Standard Network Switch</span>.</p>
</section>
<section><div class="tasklabel"><p class="sectiontitle tasklabel">Procedure</p></div><ol class="ol steps"><li class="li step stepexpand">
<span class="ph cmd">Navigate to <span class="ph menucascade"><span class="ph uicontrol">All</span><abbr> > </abbr><span class="ph uicontrol">Discovery Definition</span><abbr> > </abbr><span class="ph uicontrol">CI Classification</span><abbr> > </abbr><span class="ph uicontrol">SNMP</span></span>.</span>
</li><li class="li step stepexpand">
<span class="ph cmd">From the list, select <span class="ph uicontrol">Standard Network Switch</span>.</span>
</li><li class="li step stepexpand">
<span class="ph cmd">Open the tab <span class="ph uicontrol">SNMP OID Classifications</span> and see the list of OIDs.<img src="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/../images/telecom-switch-pattern-classification.png?_LANG=enus" class="image" id="classifying-xnfs-pattern-switch-pattern__image_dbw_p53_b2c" alt="snmp oid classification."/></span>
<div class="itemgroup info">
<div class="note note note_note"><span class="note__title">Note:</span>
<p class="p">For more information on how to add additional OIDs to the classifier, see <a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/concept/telecom-discovery-using-telecommunication-discovery-pattern.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/telecom-discovery-using-telecommunication-discovery-pattern.html" class="xref" title="The Telecommunications Discovery Patterns plugin (also known as TSOM Patterns) extends ServiceNow AI Platform Telecom Discovery to support direct discovery of standalone network elements—such as routers and switches—without relying on traditional network management systems. These patterns enable Communication Service Providers (CSPs) to identify and map multivendor xNFs using protocols like SNMP and CLI, with support for NETCONF.">Direct Discovery using Discovery Patterns</a>.</p>
</div>
<div class="p">MiB Tables Used on an xNF:<ul class="ul" id="classifying-xnfs-pattern-switch-pattern__ul_ofr_d3n_zdc">
<li class="li">SystemMIB</li>
<li class="li">EntityPhysicalMIB</li>
<li class="li">IfMIB</li>
<li class="li">IfXMIB</li>
<li class="li">IpMIB</li>
</ul></div>
</div>
</li></ol></section>
</div>
<nav role="navigation"></nav><nav role="navigation" class="tasksNavigation"></nav><nav role="navigation" class="related-links"></nav></article></main></body></article> | {
"attachments": {
"all_attachments": null,
"topic_attachments": []
},
"available_languages": [
"enus"
],
"breadcrumbs": [
{
"title": "Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html"
},
{
"title": "Using Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/using-tsom.html"
},
{
"title": "Using Telecom Discovery patterns",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/using-telecom-discovery-patterns.html"
}
],
"breadcrumbs_html": "<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops\">Zurich Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html\">Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/using-tsom.html\">Using Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/using-telecom-discovery-patterns.html\">Using Telecom Discovery patterns</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<span class=\"active\">Classifying xNFs for Telecom Switch Pattern</span>",
"bundle_id": "zurich-telecom-service-ops",
"bundle_key": 2733,
"bundle_landing_page": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html",
"bundle_subtitle": null,
"bundle_title": "Zurich Telecommunications Service Operations Management",
"canonical_link": null,
"dates": {
"Added on": "2025-08-02T00:48:08.794016Z",
"Created on": "2025-01-16T00:00:00Z",
"Initial upload": "2025-07-30T22:24:33.519043Z",
"Updated on": "2025-07-31T00:00:00Z"
},
"dislike_url": "https://servicenow-be-prod.servicenow.com/dislike/55686961",
"dislikes": 0,
"es_archived_content": false,
"is_in_fav": false,
"is_liked": null,
"is_watched": false,
"keywords": [
" zurich zurich"
],
"labels": [
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "zurich",
"navtitle": "Zurich",
"outputclasses": [],
"subjectHeadId": "versions",
"subjectheadNavtitle": "Versions",
"visibility": "show-facet"
},
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "tsom",
"navtitle": "Telecommunications Service Operations Management",
"outputclasses": [],
"subjectHeadId": "products",
"subjectheadNavtitle": "Products",
"visibility": "show-facet"
}
],
"labels_text": "Versions > Zurich; Products > CRM and Industry Products > Telecommunications Media and Technology Assurance > Telecommunications Service Operations Management",
"like_url": "https://servicenow-be-prod.servicenow.com/like/55686961",
"likes": 0,
"metadata": {
"AI Search": null,
"AI Search Assist": null,
"Application Insights": null,
"Capabilities": null,
"Code Signing": null,
"Contextual Search": null,
"DC.contributor": null,
"DC.coverage": null,
"DC.creator": "ServiceNow",
"DC.date.created": "2025-01-16T22:45:13+05:30",
"DC.date.modified": "2025-07-31",
"DC.format": "HTML5",
"DC.identifier": "classifying-xnfs-pattern-switch-pattern",
"DC.language": null,
"DC.relation": "../../../product/tmt-telecom-service-operations-mgt/concept/using-telecom-discovery-patterns.html",
"DC.rights.owner": "(C) Copyright 2025",
"DC.subject": null,
"DC.type": "task",
"Data Discovery": null,
"Data Policy": null,
"Data Privacy": null,
"Discovery": null,
"External Content for AI Search": null,
"Field Administration": null,
"Field Normalization": null,
"Key Management Framework": null,
"Localization Framework": null,
"Now Platform": null,
"PlatSec": null,
"Platform": null,
"Platform Administration": null,
"Platform Performance": null,
"Platform Privacy": null,
"Proactive Triggers": null,
"Process Optimization": null,
"RN doc editing record number": null,
"Search Administration": null,
"Secrets Management": null,
"ServiceNow AI Platform": null,
"State Model": null,
"Subscription Management": null,
"Task Communications Management": null,
"Timeline Visualizations": null,
"User Administration": null,
"User Experience Analytics": null,
"Zing": null,
"ai-now-assist": null,
"app-name": null,
"app_route": null,
"azureapimanagemen": null,
"change-completed": null,
"change-item": null,
"change-request-id": null,
"change-request-reference": null,
"com.glide.embedded_help.category": null,
"component": null,
"copyright": "(C) Copyright 2025",
"crossroads": null,
"data": null,
"description": "To access a full list of OIDs that will be classified.",
"dominant_bundle": null,
"erp-canvas-video": null,
"fsm-mobile": null,
"fsm-route": null,
"fsm-sched-opt": null,
"fsm-wrk-order": null,
"genai-round-7": null,
"generator": "DITA-OT",
"glossPartOfSpeech": null,
"glossStatus": null,
"guided setup": null,
"guided tours": null,
"keywords": null,
"min-toc": null,
"mini": null,
"mini-to truec": null,
"mini-toc": null,
"mini_toc": null,
"minitoc": null,
"modification": null,
"now-assist-app-gen-video": null,
"order": null,
"page-type": null,
"page-type ": null,
"prodname": null,
"product": null,
"product_name": null,
"release": null,
"resourceID": null,
"roles": null,
"route_page": null,
"route_params_listId": null,
"route_params_table": null,
"route_params_type": null,
"route_type": null,
"setconfigurationproperties": null,
"topic": null,
"translation-type": "source",
"version": null,
"workflow": "Customer and Industry",
"workplace-srvc-delvry-ditamap": null
},
"page_id": "product/tmt-telecom-service-operations-mgt/task/classifying-xnfs-pattern-switch-pattern.html",
"page_key": 55686961,
"preprocessed_PDF": "https://downloads.docs.servicenow.com/pdf/enus/servicenow-zurich-telecom-service-ops-enus.pdf",
"rating": null,
"read_time_data": {
"char_count": 523,
"img_count": 1,
"read_time": 1,
"video_links": [
""
],
"word_count": 87
},
"related_links": [],
"search_title": null,
"title": "Classifying xNFs for Telecom Switch Pattern",
"topic_cluster": {
"clustered_by": {
"enabled": true,
"primary_key": "versions",
"primary_sort": "top-down",
"type": "subjecthead"
},
"clustered_labels": [
"versions"
],
"clustered_topics": [],
"clustering_title": "Zurich"
},
"topic_html": "<article class=\"hascomments\" data-page=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/classifying-xnfs-pattern-switch-pattern.html\" id=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/classifying-xnfs-pattern-switch-pattern.html\"><body id=\"classifying-xnfs-pattern-switch-pattern\"><main role=\"main\"><article role=\"article\" class=\"dita\" id=\"classifying-xnfs-pattern-switch-pattern\" aria-labelledby=\"title_classifying-xnfs-pattern-switch-pattern\">\n <h1 class=\"title topictitle1\" id=\"title_classifying-xnfs-pattern-switch-pattern\">Classifying xNFs for Telecom Switch Pattern</h1>\n \n \n <div class=\"body taskbody\"><p class=\"shortdesc\">To access a full list of OIDs that will be classified.</p>\n <section class=\"section prereq\" id=\"classifying-xnfs-pattern-switch-pattern__task-prereq\"><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">Before you begin</p></div>\n <p class=\"p\">Role required: admin</p>\n <p class=\"p\">Classifier name: <span class=\"ph uicontrol\">Standard Network Switch</span>.</p>\n </section>\n <section><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">Procedure</p></div><ol class=\"ol steps\"><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">Navigate to <span class=\"ph menucascade\"><span class=\"ph uicontrol\">All</span><abbr> > </abbr><span class=\"ph uicontrol\">Discovery Definition</span><abbr> > </abbr><span class=\"ph uicontrol\">CI Classification</span><abbr> > </abbr><span class=\"ph uicontrol\">SNMP</span></span>.</span>\n </li><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">From the list, select <span class=\"ph uicontrol\">Standard Network Switch</span>.</span>\n </li><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">Open the tab <span class=\"ph uicontrol\">SNMP OID Classifications</span> and see the list of OIDs.<img src=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/../images/telecom-switch-pattern-classification.png?_LANG=enus\" class=\"image\" id=\"classifying-xnfs-pattern-switch-pattern__image_dbw_p53_b2c\" alt=\"snmp oid classification.\"/></span>\n <div class=\"itemgroup info\">\n <div class=\"note note note_note\"><span class=\"note__title\">Note:</span> \n <p class=\"p\">For more information on how to add additional OIDs to the classifier, see <a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept/telecom-discovery-using-telecommunication-discovery-pattern.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/telecom-discovery-using-telecommunication-discovery-pattern.html\" class=\"xref\" title=\"The Telecommunications Discovery Patterns plugin (also known as TSOM Patterns) extends ServiceNow AI Platform Telecom Discovery to support direct discovery of standalone network elements—such as routers and switches—without relying on traditional network management systems. These patterns enable Communication Service Providers (CSPs) to identify and map multivendor xNFs using protocols like SNMP and CLI, with support for NETCONF.\">Direct Discovery using Discovery Patterns</a>.</p>\n </div>\n <div class=\"p\">MiB Tables Used on an xNF:<ul class=\"ul\" id=\"classifying-xnfs-pattern-switch-pattern__ul_ofr_d3n_zdc\">\n <li class=\"li\">SystemMIB</li>\n <li class=\"li\">EntityPhysicalMIB</li>\n <li class=\"li\">IfMIB</li>\n <li class=\"li\">IfXMIB</li>\n <li class=\"li\">IpMIB</li>\n </ul></div>\n </div>\n </li></ol></section>\n </div>\n<nav role=\"navigation\"></nav><nav role=\"navigation\" class=\"tasksNavigation\"></nav><nav role=\"navigation\" class=\"related-links\"></nav></article></main></body></article>",
"topic_language": "enus",
"views": 0,
"your_rating": null
} | # Classifying xNFs for Telecom Switch Pattern
To access a full list of OIDs that will be classified.
## Before you begin
Role required: admin
Classifier name: Standard Network Switch.
## Procedure
1. Navigate to All > Discovery Definition > CI Classification > SNMP.
2. From the list, select Standard Network Switch.
3. Open the tab SNMP OID Classifications and see the list of OIDs.
Note:
For more information on how to add additional OIDs to the classifier, see Direct Discovery using Discovery Patterns.
MiB Tables Used on an xNF:
* SystemMIB
* EntityPhysicalMIB
* IfMIB
* IfXMIB
* IpMIB
| ---
title: Classifying xNFs for Telecom Switch Pattern
description: To access a full list of OIDs that will be classified.
keywords: []
breadcrumbs:
- Telecommunications Service Operations Management
- Using Telecommunications Service Operations Management
- Using Telecom Discovery patterns
---
# Classifying xNFs for Telecom Switch Pattern
To access a full list of OIDs that will be classified.
## Before you begin
Role required: admin
Classifier name: Standard Network Switch.
## Procedure
1. Navigate to All > Discovery Definition > CI Classification > SNMP.
2. From the list, select Standard Network Switch.
3. Open the tab SNMP OID Classifications and see the list of OIDs.
Note:
For more information on how to add additional OIDs to the classifier, see Direct Discovery using Discovery Patterns.
MiB Tables Used on an xNF:
* SystemMIB
* EntityPhysicalMIB
* IfMIB
* IfXMIB
* IpMIB
|
https://www.servicenow.com/docs/en-US/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/classifying-xnfs-telecom-cisco.html | https://servicenow-be-prod.servicenow.com/api/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/classifying-xnfs-telecom-cisco.html | 2025-08-02 | daily | 0.5 | 268.xml | en-US | zurich-telecom-service-ops | product/tmt-telecom-service-operations-mgt/task/classifying-xnfs-telecom-cisco.html | zurich | Classifying xNFs for Telecom Cisco 7613 Router Pattern | To access a full list of OIDs that will be classified. | [] | [
"Telecommunications Service Operations Management",
"Using Telecommunications Service Operations Management",
"Using Telecom Discovery patterns"
] | <article class="hascomments" data-page="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/classifying-xnfs-telecom-cisco.html" id="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/classifying-xnfs-telecom-cisco.html"><body id="classifying-xnfs-telecom-cisco"><main role="main"><article role="article" class="dita" id="classifying-xnfs-telecom-cisco" aria-labelledby="title_classifying-xnfs-telecom-cisco">
<h1 class="title topictitle1" id="title_classifying-xnfs-telecom-cisco">Classifying xNFs for Telecom Cisco 7613 Router Pattern</h1>
<div class="body taskbody"><p class="shortdesc">To access a full list of OIDs that will be classified.</p>
<section class="section prereq" id="classifying-xnfs-telecom-cisco__task-prereq"><div class="tasklabel"><p class="sectiontitle tasklabel">Before you begin</p></div>
<p class="p">Role required: admin</p>
<p class="p">Classifier name: <span class="ph uicontrol">Standard Network Router</span>.</p>
</section>
<section><div class="tasklabel"><p class="sectiontitle tasklabel">Procedure</p></div><ol class="ol steps"><li class="li step stepexpand">
<span class="ph cmd">Navigate to <span class="ph menucascade"><span class="ph uicontrol">All</span><abbr> > </abbr><span class="ph uicontrol">Discovery Definition</span><abbr> > </abbr><span class="ph uicontrol">CI Classification</span><abbr> > </abbr><span class="ph uicontrol">SNMP</span></span>.</span>
</li><li class="li step stepexpand">
<span class="ph cmd">From the list, select <span class="ph uicontrol">Standard Network Router</span>.</span>
</li><li class="li step stepexpand">
<span class="ph cmd">Open the tab <span class="ph uicontrol">SNMP OID Classifications</span> and see the list of OIDs.<img src="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/../images/telecom-cisco-7613-classification.png?_LANG=enus" class="image" id="classifying-xnfs-telecom-cisco__image_gd3_hq3_b2c" alt="snmp oid classification."/></span>
<div class="itemgroup info">
<div class="note note note_note"><span class="note__title">Note:</span>
<p class="p">For more information on how to add additional OIDs to the classifier, see <a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/concept/telecom-discovery-using-telecommunication-discovery-pattern.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/telecom-discovery-using-telecommunication-discovery-pattern.html" class="xref" title="The Telecommunications Discovery Patterns plugin (also known as TSOM Patterns) extends ServiceNow AI Platform Telecom Discovery to support direct discovery of standalone network elements—such as routers and switches—without relying on traditional network management systems. These patterns enable Communication Service Providers (CSPs) to identify and map multivendor xNFs using protocols like SNMP and CLI, with support for NETCONF.">Direct Discovery using Discovery Patterns</a>.</p>
</div>
<div class="p">The List of Specific OIDs to call this Pattern:<div class="table-wrap"><table count-columns="4" class="table frame-all" id="classifying-xnfs-telecom-cisco__table_knh_dlf_b2c"><caption></caption><colgroup><col style="width:106"/><col style="width:127"/><col style="width:218"/><col style="width:172"/></colgroup><tbody class="tbody">
<tr class="row">
<td class="entry colsep-1 rowsep-1"><strong class="ph b">Vendor</strong></td>
<td class="entry colsep-1 rowsep-1"><strong class="ph b">Model</strong></td>
<td class="entry colsep-1 rowsep-1"><strong class="ph b">OID</strong></td>
<td class="entry colsep-1 rowsep-1"><strong class="ph b">Pattern</strong></td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1">Cisco</td>
<td class="entry colsep-1 rowsep-1">7613</td>
<td class="entry colsep-1 rowsep-1">1.3.6.1.4.1.9.1.528</td>
<td class="entry colsep-1 rowsep-1">Telecom Cisco 7613 Router</td>
</tr>
</tbody></table></div></div>
<div class="p">MiB Tables Used on an xNF:<ul class="ul" id="classifying-xnfs-telecom-cisco__ul_ofr_d3n_zdc">
<li class="li">SystemMIB</li>
<li class="li">EntityPhysicalMIB</li>
<li class="li">IfMIB</li>
<li class="li">IfXMIB</li>
<li class="li">IpMIB</li>
</ul></div>
</div>
</li></ol></section>
</div>
<nav role="navigation"></nav><nav role="navigation" class="tasksNavigation"></nav><nav role="navigation" class="related-links"></nav></article></main></body></article> | {
"attachments": {
"all_attachments": null,
"topic_attachments": []
},
"available_languages": [
"enus"
],
"breadcrumbs": [
{
"title": "Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html"
},
{
"title": "Using Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/using-tsom.html"
},
{
"title": "Using Telecom Discovery patterns",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/using-telecom-discovery-patterns.html"
}
],
"breadcrumbs_html": "<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops\">Zurich Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html\">Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/using-tsom.html\">Using Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/using-telecom-discovery-patterns.html\">Using Telecom Discovery patterns</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<span class=\"active\">Classifying xNFs for Telecom Cisco 7613 Router Pattern</span>",
"bundle_id": "zurich-telecom-service-ops",
"bundle_key": 2733,
"bundle_landing_page": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html",
"bundle_subtitle": null,
"bundle_title": "Zurich Telecommunications Service Operations Management",
"canonical_link": null,
"dates": {
"Added on": "2025-08-02T00:48:08.794016Z",
"Created on": "2025-01-16T00:00:00Z",
"Initial upload": "2025-07-30T22:24:33.519043Z",
"Updated on": "2025-07-31T00:00:00Z"
},
"dislike_url": "https://servicenow-be-prod.servicenow.com/dislike/55686963",
"dislikes": 0,
"es_archived_content": false,
"is_in_fav": false,
"is_liked": null,
"is_watched": false,
"keywords": [
" zurich zurich"
],
"labels": [
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "zurich",
"navtitle": "Zurich",
"outputclasses": [],
"subjectHeadId": "versions",
"subjectheadNavtitle": "Versions",
"visibility": "show-facet"
},
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "tsom",
"navtitle": "Telecommunications Service Operations Management",
"outputclasses": [],
"subjectHeadId": "products",
"subjectheadNavtitle": "Products",
"visibility": "show-facet"
}
],
"labels_text": "Versions > Zurich; Products > CRM and Industry Products > Telecommunications Media and Technology Assurance > Telecommunications Service Operations Management",
"like_url": "https://servicenow-be-prod.servicenow.com/like/55686963",
"likes": 0,
"metadata": {
"AI Search": null,
"AI Search Assist": null,
"Application Insights": null,
"Capabilities": null,
"Code Signing": null,
"Contextual Search": null,
"DC.contributor": null,
"DC.coverage": null,
"DC.creator": "ServiceNow",
"DC.date.created": "2025-01-16T22:19:03+05:30",
"DC.date.modified": "2025-07-31",
"DC.format": "HTML5",
"DC.identifier": "classifying-xnfs-telecom-cisco",
"DC.language": null,
"DC.relation": "../../../product/tmt-telecom-service-operations-mgt/concept/using-telecom-discovery-patterns.html",
"DC.rights.owner": "(C) Copyright 2025",
"DC.subject": null,
"DC.type": "task",
"Data Discovery": null,
"Data Policy": null,
"Data Privacy": null,
"Discovery": null,
"External Content for AI Search": null,
"Field Administration": null,
"Field Normalization": null,
"Key Management Framework": null,
"Localization Framework": null,
"Now Platform": null,
"PlatSec": null,
"Platform": null,
"Platform Administration": null,
"Platform Performance": null,
"Platform Privacy": null,
"Proactive Triggers": null,
"Process Optimization": null,
"RN doc editing record number": null,
"Search Administration": null,
"Secrets Management": null,
"ServiceNow AI Platform": null,
"State Model": null,
"Subscription Management": null,
"Task Communications Management": null,
"Timeline Visualizations": null,
"User Administration": null,
"User Experience Analytics": null,
"Zing": null,
"ai-now-assist": null,
"app-name": null,
"app_route": null,
"azureapimanagemen": null,
"change-completed": null,
"change-item": null,
"change-request-id": null,
"change-request-reference": null,
"com.glide.embedded_help.category": null,
"component": null,
"copyright": "(C) Copyright 2025",
"crossroads": null,
"data": null,
"description": "To access a full list of OIDs that will be classified.",
"dominant_bundle": null,
"erp-canvas-video": null,
"fsm-mobile": null,
"fsm-route": null,
"fsm-sched-opt": null,
"fsm-wrk-order": null,
"genai-round-7": null,
"generator": "DITA-OT",
"glossPartOfSpeech": null,
"glossStatus": null,
"guided setup": null,
"guided tours": null,
"keywords": null,
"min-toc": null,
"mini": null,
"mini-to truec": null,
"mini-toc": null,
"mini_toc": null,
"minitoc": null,
"modification": null,
"now-assist-app-gen-video": null,
"order": null,
"page-type": null,
"page-type ": null,
"prodname": null,
"product": null,
"product_name": null,
"release": null,
"resourceID": null,
"roles": null,
"route_page": null,
"route_params_listId": null,
"route_params_table": null,
"route_params_type": null,
"route_type": null,
"setconfigurationproperties": null,
"topic": null,
"translation-type": "source",
"version": null,
"workflow": "Customer and Industry",
"workplace-srvc-delvry-ditamap": null
},
"page_id": "product/tmt-telecom-service-operations-mgt/task/classifying-xnfs-telecom-cisco.html",
"page_key": 55686963,
"preprocessed_PDF": "https://downloads.docs.servicenow.com/pdf/enus/servicenow-zurich-telecom-service-ops-enus.pdf",
"rating": null,
"read_time_data": {
"char_count": 653,
"img_count": 1,
"read_time": 1,
"video_links": [
""
],
"word_count": 107
},
"related_links": [],
"search_title": null,
"title": "Classifying xNFs for Telecom Cisco 7613 Router Pattern",
"topic_cluster": {
"clustered_by": {
"enabled": true,
"primary_key": "versions",
"primary_sort": "top-down",
"type": "subjecthead"
},
"clustered_labels": [
"versions"
],
"clustered_topics": [],
"clustering_title": "Zurich"
},
"topic_html": "<article class=\"hascomments\" data-page=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/classifying-xnfs-telecom-cisco.html\" id=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/classifying-xnfs-telecom-cisco.html\"><body id=\"classifying-xnfs-telecom-cisco\"><main role=\"main\"><article role=\"article\" class=\"dita\" id=\"classifying-xnfs-telecom-cisco\" aria-labelledby=\"title_classifying-xnfs-telecom-cisco\">\n <h1 class=\"title topictitle1\" id=\"title_classifying-xnfs-telecom-cisco\">Classifying xNFs for Telecom Cisco 7613 Router Pattern</h1>\n \n \n <div class=\"body taskbody\"><p class=\"shortdesc\">To access a full list of OIDs that will be classified.</p>\n <section class=\"section prereq\" id=\"classifying-xnfs-telecom-cisco__task-prereq\"><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">Before you begin</p></div>\n <p class=\"p\">Role required: admin</p>\n <p class=\"p\">Classifier name: <span class=\"ph uicontrol\">Standard Network Router</span>.</p>\n </section>\n <section><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">Procedure</p></div><ol class=\"ol steps\"><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">Navigate to <span class=\"ph menucascade\"><span class=\"ph uicontrol\">All</span><abbr> > </abbr><span class=\"ph uicontrol\">Discovery Definition</span><abbr> > </abbr><span class=\"ph uicontrol\">CI Classification</span><abbr> > </abbr><span class=\"ph uicontrol\">SNMP</span></span>.</span>\n </li><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">From the list, select <span class=\"ph uicontrol\">Standard Network Router</span>.</span>\n </li><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">Open the tab <span class=\"ph uicontrol\">SNMP OID Classifications</span> and see the list of OIDs.<img src=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/../images/telecom-cisco-7613-classification.png?_LANG=enus\" class=\"image\" id=\"classifying-xnfs-telecom-cisco__image_gd3_hq3_b2c\" alt=\"snmp oid classification.\"/></span>\n <div class=\"itemgroup info\">\n <div class=\"note note note_note\"><span class=\"note__title\">Note:</span> \n <p class=\"p\">For more information on how to add additional OIDs to the classifier, see <a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept/telecom-discovery-using-telecommunication-discovery-pattern.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/telecom-discovery-using-telecommunication-discovery-pattern.html\" class=\"xref\" title=\"The Telecommunications Discovery Patterns plugin (also known as TSOM Patterns) extends ServiceNow AI Platform Telecom Discovery to support direct discovery of standalone network elements—such as routers and switches—without relying on traditional network management systems. These patterns enable Communication Service Providers (CSPs) to identify and map multivendor xNFs using protocols like SNMP and CLI, with support for NETCONF.\">Direct Discovery using Discovery Patterns</a>.</p>\n </div>\n <div class=\"p\">The List of Specific OIDs to call this Pattern:<div class=\"table-wrap\"><table count-columns=\"4\" class=\"table frame-all\" id=\"classifying-xnfs-telecom-cisco__table_knh_dlf_b2c\"><caption></caption><colgroup><col style=\"width:106\"/><col style=\"width:127\"/><col style=\"width:218\"/><col style=\"width:172\"/></colgroup><tbody class=\"tbody\">\n <tr class=\"row\">\n <td class=\"entry colsep-1 rowsep-1\"><strong class=\"ph b\">Vendor</strong></td>\n <td class=\"entry colsep-1 rowsep-1\"><strong class=\"ph b\">Model</strong></td>\n <td class=\"entry colsep-1 rowsep-1\"><strong class=\"ph b\">OID</strong></td>\n <td class=\"entry colsep-1 rowsep-1\"><strong class=\"ph b\">Pattern</strong></td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry colsep-1 rowsep-1\">Cisco</td>\n <td class=\"entry colsep-1 rowsep-1\">7613</td>\n <td class=\"entry colsep-1 rowsep-1\">1.3.6.1.4.1.9.1.528</td>\n <td class=\"entry colsep-1 rowsep-1\">Telecom Cisco 7613 Router</td>\n </tr>\n </tbody></table></div></div>\n <div class=\"p\">MiB Tables Used on an xNF:<ul class=\"ul\" id=\"classifying-xnfs-telecom-cisco__ul_ofr_d3n_zdc\">\n <li class=\"li\">SystemMIB</li>\n <li class=\"li\">EntityPhysicalMIB</li>\n <li class=\"li\">IfMIB</li>\n <li class=\"li\">IfXMIB</li>\n <li class=\"li\">IpMIB</li>\n </ul></div>\n </div>\n </li></ol></section>\n </div>\n<nav role=\"navigation\"></nav><nav role=\"navigation\" class=\"tasksNavigation\"></nav><nav role=\"navigation\" class=\"related-links\"></nav></article></main></body></article>",
"topic_language": "enus",
"views": 0,
"your_rating": null
} | # Classifying xNFs for Telecom Cisco 7613 Router Pattern
To access a full list of OIDs that will be classified.
## Before you begin
Role required: admin
Classifier name: Standard Network Router.
## Procedure
1. Navigate to All > Discovery Definition > CI Classification > SNMP.
2. From the list, select Standard Network Router.
3. Open the tab SNMP OID Classifications and see the list of OIDs.
Note:
For more information on how to add additional OIDs to the classifier, see Direct Discovery using Discovery Patterns.
The List of Specific OIDs to call this Pattern:
| **Vendor** | **Model** | **OID** | **Pattern** |
| --- | --- | --- | --- |
| Cisco | 7613 | 1.3.6.1.4.1.9.1.528 | Telecom Cisco 7613 Router |
MiB Tables Used on an xNF:
* SystemMIB
* EntityPhysicalMIB
* IfMIB
* IfXMIB
* IpMIB
| ---
title: Classifying xNFs for Telecom Cisco 7613 Router Pattern
description: To access a full list of OIDs that will be classified.
keywords: []
breadcrumbs:
- Telecommunications Service Operations Management
- Using Telecommunications Service Operations Management
- Using Telecom Discovery patterns
---
# Classifying xNFs for Telecom Cisco 7613 Router Pattern
To access a full list of OIDs that will be classified.
## Before you begin
Role required: admin
Classifier name: Standard Network Router.
## Procedure
1. Navigate to All > Discovery Definition > CI Classification > SNMP.
2. From the list, select Standard Network Router.
3. Open the tab SNMP OID Classifications and see the list of OIDs.
Note:
For more information on how to add additional OIDs to the classifier, see Direct Discovery using Discovery Patterns.
The List of Specific OIDs to call this Pattern:
| **Vendor** | **Model** | **OID** | **Pattern** |
| --- | --- | --- | --- |
| Cisco | 7613 | 1.3.6.1.4.1.9.1.528 | Telecom Cisco 7613 Router |
MiB Tables Used on an xNF:
* SystemMIB
* EntityPhysicalMIB
* IfMIB
* IfXMIB
* IpMIB
|
https://www.servicenow.com/docs/en-US/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/configure-attribute-value-discrepancy-in-cmdb-360.html | https://servicenow-be-prod.servicenow.com/api/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/configure-attribute-value-discrepancy-in-cmdb-360.html | 2025-08-02 | daily | 0.5 | 268.xml | en-US | zurich-telecom-service-ops | product/tmt-telecom-service-operations-mgt/task/configure-attribute-value-discrepancy-in-cmdb-360.html | zurich | Configure attribute value discrepancy in CMDB 360 | Configure attribute comparison settings in CMDB 360 to detect data inconsistencies across multiple discovery sources. | [] | [
"Telecommunications Service Operations Management",
"Configuring Telecommunications Service Operations Management",
"Set up Telecom Visibility",
"Activate Telecom Discrepancy Identification and Reconciliation"
] | <article class="hascomments" data-page="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/configure-attribute-value-discrepancy-in-cmdb-360.html" id="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/configure-attribute-value-discrepancy-in-cmdb-360.html"><body id="configure-attribute-value-discrepancy-in-cmdb-360"><main role="main"><article role="article" class="dita" id="configure-attribute-value-discrepancy-in-cmdb-360" aria-labelledby="title_configure-attribute-value-discrepancy-in-cmdb-360">
<h1 class="title topictitle1" id="title_configure-attribute-value-discrepancy-in-cmdb-360">Configure attribute value discrepancy in CMDB 360</h1>
<div class="body taskbody"><p class="shortdesc">Configure attribute comparison settings in CMDB 360 to detect data inconsistencies across multiple discovery sources.</p>
<section class="section prereq" id="configure-attribute-value-discrepancy-in-cmdb-360__task-prereq"><div class="tasklabel"><p class="sectiontitle tasklabel">Before you begin</p></div>
<p class="p">Role required: admin</p>
<p class="p">Confirm that CMDB 360 is enabled and configured in your instance.</p>
</section>
<section class="section context" id="configure-attribute-value-discrepancy-in-cmdb-360__context_xf2_lxz_zfc"><div class="tasklabel"><p class="sectiontitle tasklabel">About this task</p></div>
<p class="p">The following screenshot can help you to set up the fields to identify the discrepancy.<img src="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/../images/set-attribute-discrepancy-value.png?_LANG=enus" class="image" id="configure-attribute-value-discrepancy-in-cmdb-360__image_p12_4xz_zfc" alt="CMDB MultiSource Column Metadata user interface with the fields configured for discrepancy."/></p>
</section>
<section><div class="tasklabel"><p class="sectiontitle tasklabel">Procedure</p></div><ol class="ol steps"><li class="li step stepexpand">
<span class="ph cmd">Navigate to the table <span class="ph menucascade"><span class="ph uicontrol">All</span><abbr> > </abbr><span class="ph uicontrol">cmdb_multisource_column_metadata.list</span></span>.</span>
</li><li class="li step stepexpand">
<span class="ph cmd">Select <span class="ph uicontrol">New</span> to create a new record.</span>
</li><li class="li step stepexpand">
<span class="ph cmd">In the <span class="ph uicontrol">MultiSource Column</span> field, select the attribute to compare.</span>
</li><li class="li step stepexpand">
<span class="ph cmd">Select the table to compare the attributes to the fields.</span>
<div class="itemgroup info">
<div class="note note note_note"><span class="note__title">Note:</span> If the table you need isn’t listed, select and hold (or right-click) on the Table label and select <span class="ph uicontrol">Configure Dictionary</span>.</div>
</div>
</li><li class="li step stepexpand">(Optional)
<span class="ph cmd">To configure a dictionary entry, do the following.</span>
<ol type="a" class="ol substeps" id="configure-attribute-value-discrepancy-in-cmdb-360__substeps_l1p_31t_zfc">
<li class="li substep">
<span class="ph cmd">In the dictionary entry, select <span class="ph uicontrol">View</span> and then select <span class="ph uicontrol">Advanced</span>.</span>
</li>
<li class="li substep">
<span class="ph cmd">In the <span class="ph uicontrol">Attributes</span> field, set the attributes as <code class="ph codeph">base_start=true</code> and <code class="ph codeph">allow_public=true</code>.</span>
</li>
</ol>
</li></ol></section>
<section class="section result" id="configure-attribute-value-discrepancy-in-cmdb-360__result_k2l_51t_zfc"><div class="tasklabel"><p class="sectiontitle tasklabel">Result</p></div>
<p class="p">You can use the configured attributes in the CMDB 360 query.</p>
</section>
</div>
<nav role="navigation"></nav><nav role="navigation" class="tasksNavigation"></nav><nav role="navigation" class="related-links"><div class="col-md-4"><dt>Related tasks</dt><dd><ul><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/task/control-ci-attribute-updates-using-reconciliation-rules.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/control-ci-attribute-updates-using-reconciliation-rules.html" class="link" title="To prevent specific attributes of a Configuration Item (CI) from being overwritten by Discovery or other data sources, use Reconciliation Rules. These rules define which data source is trusted to update a particular attribute when multiple sources provide values.">Control CI attribute updates using Reconciliation rules</a></li><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/task/use-attribute-value-discrepancy-in-cmdb-360.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/use-attribute-value-discrepancy-in-cmdb-360.html" class="link" title="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.">Generate reports for attribute value discrepancies</a></li></ul></dd></div></nav>
</article></main></body></article> | {
"attachments": {
"all_attachments": null,
"topic_attachments": []
},
"available_languages": [
"enus"
],
"breadcrumbs": [
{
"title": "Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html"
},
{
"title": "Configuring Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/configuring-tsom.html"
},
{
"title": "Set up Telecom Visibility",
"topic_id": "product/tmt-telecom-service-operations-mgt/task/configuring-tsom-visibility.html"
},
{
"title": "Activate Telecom Discrepancy Identification and Reconciliation",
"topic_id": "product/tmt-telecom-service-operations-mgt/task/configure-telecom-reconciliation.html"
}
],
"breadcrumbs_html": "<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops\">Zurich Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html\">Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/configuring-tsom.html\">Configuring Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/configuring-tsom-visibility.html\">Set up Telecom Visibility</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/configure-telecom-reconciliation.html\">Activate Telecom Discrepancy Identification and Reconciliation</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<span class=\"active\">Configure attribute value discrepancy in CMDB 360</span>",
"bundle_id": "zurich-telecom-service-ops",
"bundle_key": 2733,
"bundle_landing_page": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html",
"bundle_subtitle": null,
"bundle_title": "Zurich Telecommunications Service Operations Management",
"canonical_link": null,
"dates": {
"Added on": "2025-08-02T00:48:08.794016Z",
"Created on": "2025-07-15T00:00:00Z",
"Initial upload": "2025-07-30T22:24:33.519043Z",
"Updated on": "2025-07-31T00:00:00Z"
},
"dislike_url": "https://servicenow-be-prod.servicenow.com/dislike/55686964",
"dislikes": 0,
"es_archived_content": false,
"is_in_fav": false,
"is_liked": null,
"is_watched": false,
"keywords": [
" zurich zurich"
],
"labels": [
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "zurich",
"navtitle": "Zurich",
"outputclasses": [],
"subjectHeadId": "versions",
"subjectheadNavtitle": "Versions",
"visibility": "show-facet"
},
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "tsom",
"navtitle": "Telecommunications Service Operations Management",
"outputclasses": [],
"subjectHeadId": "products",
"subjectheadNavtitle": "Products",
"visibility": "show-facet"
}
],
"labels_text": "Versions > Zurich; Products > CRM and Industry Products > Telecommunications Media and Technology Assurance > Telecommunications Service Operations Management",
"like_url": "https://servicenow-be-prod.servicenow.com/like/55686964",
"likes": 0,
"metadata": {
"AI Search": null,
"AI Search Assist": null,
"Application Insights": null,
"Capabilities": null,
"Code Signing": null,
"Contextual Search": null,
"DC.contributor": null,
"DC.coverage": null,
"DC.creator": "ServiceNow",
"DC.date.created": "2025-07-15T18:53:52+05:30",
"DC.date.modified": "2025-07-31",
"DC.format": "HTML5",
"DC.identifier": "configure-attribute-value-discrepancy-in-cmdb-360",
"DC.language": null,
"DC.relation": "control-ci-attribute-updates-using-reconciliation-rules.html",
"DC.rights.owner": "(C) Copyright 2025",
"DC.subject": null,
"DC.type": "task",
"Data Discovery": null,
"Data Policy": null,
"Data Privacy": null,
"Discovery": null,
"External Content for AI Search": null,
"Field Administration": null,
"Field Normalization": null,
"Key Management Framework": null,
"Localization Framework": null,
"Now Platform": null,
"PlatSec": null,
"Platform": null,
"Platform Administration": null,
"Platform Performance": null,
"Platform Privacy": null,
"Proactive Triggers": null,
"Process Optimization": null,
"RN doc editing record number": null,
"Search Administration": null,
"Secrets Management": null,
"ServiceNow AI Platform": null,
"State Model": null,
"Subscription Management": null,
"Task Communications Management": null,
"Timeline Visualizations": null,
"User Administration": null,
"User Experience Analytics": null,
"Zing": null,
"ai-now-assist": null,
"app-name": null,
"app_route": null,
"azureapimanagemen": null,
"change-completed": null,
"change-item": null,
"change-request-id": null,
"change-request-reference": null,
"com.glide.embedded_help.category": null,
"component": null,
"copyright": "(C) Copyright 2025",
"crossroads": null,
"data": null,
"description": "Configure attribute comparison settings in CMDB 360 to detect data inconsistencies across multiple discovery sources.",
"dominant_bundle": null,
"erp-canvas-video": null,
"fsm-mobile": null,
"fsm-route": null,
"fsm-sched-opt": null,
"fsm-wrk-order": null,
"genai-round-7": null,
"generator": "DITA-OT",
"glossPartOfSpeech": null,
"glossStatus": null,
"guided setup": null,
"guided tours": null,
"keywords": null,
"min-toc": null,
"mini": null,
"mini-to truec": null,
"mini-toc": null,
"mini_toc": null,
"minitoc": null,
"modification": null,
"now-assist-app-gen-video": null,
"order": null,
"page-type": null,
"page-type ": null,
"prodname": null,
"product": null,
"product_name": null,
"release": null,
"resourceID": null,
"roles": null,
"route_page": null,
"route_params_listId": null,
"route_params_table": null,
"route_params_type": null,
"route_type": null,
"setconfigurationproperties": null,
"topic": null,
"translation-type": "source",
"version": null,
"workflow": "Customer and Industry",
"workplace-srvc-delvry-ditamap": null
},
"page_id": "product/tmt-telecom-service-operations-mgt/task/configure-attribute-value-discrepancy-in-cmdb-360.html",
"page_key": 55686964,
"preprocessed_PDF": "https://downloads.docs.servicenow.com/pdf/enus/servicenow-zurich-telecom-service-ops-enus.pdf",
"rating": null,
"read_time_data": {
"char_count": 971,
"img_count": 1,
"read_time": 1,
"video_links": [
""
],
"word_count": 152
},
"related_links": [
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "To prevent specific attributes of a Configuration Item (CI) from being overwritten by Discovery or other data sources, use Reconciliation Rules. These rules define which data source is trusted to update a particular attribute when multiple sources provide values.",
"title": "Control CI attribute updates using Reconciliation rules",
"topic": "/product/tmt-telecom-service-operations-mgt/task/control-ci-attribute-updates-using-reconciliation-rules.html",
"type": "task",
"url": null
},
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "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.",
"title": "Generate reports for attribute value discrepancies",
"topic": "/product/tmt-telecom-service-operations-mgt/task/use-attribute-value-discrepancy-in-cmdb-360.html",
"type": "task",
"url": null
}
],
"search_title": null,
"title": "Configure attribute value discrepancy in CMDB 360",
"topic_cluster": {
"clustered_by": {
"enabled": true,
"primary_key": "versions",
"primary_sort": "top-down",
"type": "subjecthead"
},
"clustered_labels": [
"versions"
],
"clustered_topics": [],
"clustering_title": "Zurich"
},
"topic_html": "<article class=\"hascomments\" data-page=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/configure-attribute-value-discrepancy-in-cmdb-360.html\" id=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/configure-attribute-value-discrepancy-in-cmdb-360.html\"><body id=\"configure-attribute-value-discrepancy-in-cmdb-360\"><main role=\"main\"><article role=\"article\" class=\"dita\" id=\"configure-attribute-value-discrepancy-in-cmdb-360\" aria-labelledby=\"title_configure-attribute-value-discrepancy-in-cmdb-360\">\n <h1 class=\"title topictitle1\" id=\"title_configure-attribute-value-discrepancy-in-cmdb-360\">Configure attribute value discrepancy in CMDB 360</h1>\n \n \n <div class=\"body taskbody\"><p class=\"shortdesc\">Configure attribute comparison settings in CMDB 360 to detect data inconsistencies across multiple discovery sources.</p>\n <section class=\"section prereq\" id=\"configure-attribute-value-discrepancy-in-cmdb-360__task-prereq\"><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">Before you begin</p></div>\n <p class=\"p\">Role required: admin</p>\n <p class=\"p\">Confirm that CMDB 360 is enabled and configured in your instance.</p>\n </section>\n <section class=\"section context\" id=\"configure-attribute-value-discrepancy-in-cmdb-360__context_xf2_lxz_zfc\"><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">About this task</p></div>\n <p class=\"p\">The following screenshot can help you to set up the fields to identify the discrepancy.<img src=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/../images/set-attribute-discrepancy-value.png?_LANG=enus\" class=\"image\" id=\"configure-attribute-value-discrepancy-in-cmdb-360__image_p12_4xz_zfc\" alt=\"CMDB MultiSource Column Metadata user interface with the fields configured for discrepancy.\"/></p>\n </section>\n <section><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">Procedure</p></div><ol class=\"ol steps\"><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">Navigate to the table <span class=\"ph menucascade\"><span class=\"ph uicontrol\">All</span><abbr> > </abbr><span class=\"ph uicontrol\">cmdb_multisource_column_metadata.list</span></span>.</span>\n </li><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">Select <span class=\"ph uicontrol\">New</span> to create a new record.</span>\n </li><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">In the <span class=\"ph uicontrol\">MultiSource Column</span> field, select the attribute to compare.</span>\n </li><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">Select the table to compare the attributes to the fields.</span>\n <div class=\"itemgroup info\">\n <div class=\"note note note_note\"><span class=\"note__title\">Note:</span> If the table you need isn’t listed, select and hold (or right-click) on the Table label and select <span class=\"ph uicontrol\">Configure Dictionary</span>.</div>\n </div>\n </li><li class=\"li step stepexpand\">(Optional) \n <span class=\"ph cmd\">To configure a dictionary entry, do the following.</span>\n <ol type=\"a\" class=\"ol substeps\" id=\"configure-attribute-value-discrepancy-in-cmdb-360__substeps_l1p_31t_zfc\">\n <li class=\"li substep\">\n <span class=\"ph cmd\">In the dictionary entry, select <span class=\"ph uicontrol\">View</span> and then select <span class=\"ph uicontrol\">Advanced</span>.</span>\n </li>\n <li class=\"li substep\">\n <span class=\"ph cmd\">In the <span class=\"ph uicontrol\">Attributes</span> field, set the attributes as <code class=\"ph codeph\">base_start=true</code> and <code class=\"ph codeph\">allow_public=true</code>.</span>\n </li>\n </ol>\n </li></ol></section>\n <section class=\"section result\" id=\"configure-attribute-value-discrepancy-in-cmdb-360__result_k2l_51t_zfc\"><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">Result</p></div>\n <p class=\"p\">You can use the configured attributes in the CMDB 360 query.</p>\n </section>\n </div>\n <nav role=\"navigation\"></nav><nav role=\"navigation\" class=\"tasksNavigation\"></nav><nav role=\"navigation\" class=\"related-links\"><div class=\"col-md-4\"><dt>Related tasks</dt><dd><ul><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/task/control-ci-attribute-updates-using-reconciliation-rules.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/control-ci-attribute-updates-using-reconciliation-rules.html\" class=\"link\" title=\"To prevent specific attributes of a Configuration Item (CI) from being overwritten by Discovery or other data sources, use Reconciliation Rules. These rules define which data source is trusted to update a particular attribute when multiple sources provide values.\">Control CI attribute updates using Reconciliation rules</a></li><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/task/use-attribute-value-discrepancy-in-cmdb-360.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/use-attribute-value-discrepancy-in-cmdb-360.html\" class=\"link\" title=\"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.\">Generate reports for attribute value discrepancies</a></li></ul></dd></div></nav>\n</article></main></body></article>",
"topic_language": "enus",
"views": 0,
"your_rating": null
} | # Configure attribute value discrepancy in CMDB 360
Configure attribute comparison settings in CMDB 360 to detect data inconsistencies across multiple discovery sources.
## Before you begin
Role required: admin
Confirm that CMDB 360 is enabled and configured in your instance.
## About this task
The following screenshot can help you to set up the fields to identify the discrepancy.
## Procedure
1. Navigate to the table All > cmdb\_multisource\_column\_metadata.list.
2. Select New to create a new record.
3. In the MultiSource Column field, select the attribute to compare.
4. Select the table to compare the attributes to the fields.
Note: If the table you need isn’t listed, select and hold (or right-click) on the Table label and select Configure Dictionary.
5. (Optional)
To configure a dictionary entry, do the following.
1. In the dictionary entry, select View and then select Advanced.
2. In the Attributes field, set the attributes as `base_start=true` and `allow_public=true`.
### Result
You can use the configured attributes in the CMDB 360 query.
| ---
title: Configure attribute value discrepancy in CMDB 360
description: Configure attribute comparison settings in CMDB 360 to detect data inconsistencies
across multiple discovery sources.
keywords: []
breadcrumbs:
- Telecommunications Service Operations Management
- Configuring Telecommunications Service Operations Management
- Set up Telecom Visibility
- Activate Telecom Discrepancy Identification and Reconciliation
---
# Configure attribute value discrepancy in CMDB 360
Configure attribute comparison settings in CMDB 360 to detect data inconsistencies across multiple discovery sources.
## Before you begin
Role required: admin
Confirm that CMDB 360 is enabled and configured in your instance.
## About this task
The following screenshot can help you to set up the fields to identify the discrepancy.
## Procedure
1. Navigate to the table All > cmdb\_multisource\_column\_metadata.list.
2. Select New to create a new record.
3. In the MultiSource Column field, select the attribute to compare.
4. Select the table to compare the attributes to the fields.
Note: If the table you need isn’t listed, select and hold (or right-click) on the Table label and select Configure Dictionary.
5. (Optional)
To configure a dictionary entry, do the following.
1. In the dictionary entry, select View and then select Advanced.
2. In the Attributes field, set the attributes as `base_start=true` and `allow_public=true`.
### Result
You can use the configured attributes in the CMDB 360 query.
|
https://www.servicenow.com/docs/en-US/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/configure-certification-filter-for-audit.html | https://servicenow-be-prod.servicenow.com/api/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/configure-certification-filter-for-audit.html | 2025-08-02 | daily | 0.5 | 268.xml | en-US | zurich-telecom-service-ops | product/tmt-telecom-service-operations-mgt/task/configure-certification-filter-for-audit.html | zurich | Configure filter for audit | Define filtering conditions to control the scope of Telecom Discrepancy audits. These filters ensure that audits run only on the desired set of CIs, improving performance and targeting accuracy. | [] | [
"Telecommunications Service Operations Management",
"Configuring Telecommunications Service Operations Management",
"Set up Telecom Visibility",
"Activate Telecom Discrepancy Identification and Reconciliation"
] | <article class="hascomments" data-page="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/configure-certification-filter-for-audit.html" id="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/configure-certification-filter-for-audit.html"><body id="configure-certification-filter-for-audit"><main role="main"><article role="article" class="dita" id="configure-certification-filter-for-audit" aria-labelledby="title_configure-certification-filter-for-audit">
<h1 class="title topictitle1" id="title_configure-certification-filter-for-audit">Configure filter for audit</h1>
<div class="body taskbody"><p class="shortdesc">Define filtering conditions to control the scope of Telecom Discrepancy audits. These filters ensure that audits run only on the desired set of CIs, improving performance and targeting accuracy.</p>
<section class="section prereq" id="configure-certification-filter-for-audit__task-prereq"><div class="tasklabel"><p class="sectiontitle tasklabel">Before you begin</p></div>
<p class="p">Role required: admin</p>
</section>
<section class="section context"><div class="tasklabel"><p class="sectiontitle tasklabel">About this task</p></div>
<div class="p">Understanding Filtering Conditions in Telecom Discrepancy Audits<ul class="ul" id="configure-certification-filter-for-audit__ul_sz3_z3d_zfc">
<li class="li">Audits use filtering conditions to narrow the scope of CIs being evaluated.</li>
<li class="li">Filtering conditions are essential for narrowing down audit targets.</li>
<li class="li">You can define and modify conditions per audit instance to meet specific audit requirements.</li>
<li class="li">Filtering by <code class="ph codeph">discovery_source</code> is a common condition to filter records associated with particular integration sources (e.g., TSOM and Altiplano). Additionally, you can customize the filter according
to the audit requirements.</li>
<li class="li">Each version of the audit can have a different filtering condition.</li>
</ul></div>
<div class="p">The following are the audit filters:<ol class="ol" id="configure-certification-filter-for-audit__ol_bvh_kjd_zfc">
<li class="li">Telecom Logical Connections Discrepancy Audit: This audit runs at the logical connection table. The default filter condition is defined as <code class="ph codeph">discovery_source</code> like TSOM. This condition is applied on
each CI in the logical connection table.</li>
<li class="li">Telecom Network Topology Discrepancy Audit: This audit runs at the network topology table. The default filter condition is defined as <code class="ph codeph">discovery_source</code> like TSOM. This condition is applied on each CI
in the network topology table.</li>
<li class="li">Telecom Discrepancy Audit: This audit runs at the relationships table. The default filter condition is defined as <code class="ph codeph">discovery_source</code> like TSOM. This condition is applied on each CI at the equipment
level.</li>
</ol></div>
<p class="p">The following screenshot helps to understand the user interface of the certification filter <img src="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/../images/certification-filter.png?_LANG=enus" class="image" id="configure-certification-filter-for-audit__image_cgq_qqd_zfc" alt="The user interface of TSOM certification and logical connection discrepancy audit filter."/>.</p>
</section>
<section><div class="tasklabel"><p class="sectiontitle tasklabel">Procedure</p></div><ol class="ol steps"><li class="li step stepexpand">
<span class="ph cmd">Navigate to <span class="ph menucascade"><span class="ph uicontrol">All</span><abbr> > </abbr><span class="ph uicontrol">Certification</span><abbr> > </abbr><span class="ph uicontrol">Filters</span></span>.</span>
</li><li class="li step stepexpand">
<span class="ph cmd">Select <span class="ph uicontrol">New</span>.</span>
<div class="itemgroup stepresult">The certification filter interface appears.</div>
</li><li class="li step stepexpand">
<span class="ph cmd">Fill in the fields.</span>
<div class="itemgroup info">For more guidance, see <a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/task//csh" href="https://servicenow-be-prod.servicenow.com/csh?topicname=t_CreatingCertificationFilters&version=zurich&pubname=zurich-servicenow-platform" class="xref">Create a certification filter</a>.</div>
</li><li class="li step stepexpand">
<span class="ph cmd">Add the filter conditions.</span>
<div class="itemgroup info">For example, Discovery source contains TSOM.</div>
</li><li class="li step stepexpand">
<span class="ph cmd">Select <span class="ph uicontrol">Submit</span>.</span>
<div class="itemgroup stepresult">The filter is created.</div>
</li></ol></section>
<section class="section result" id="configure-certification-filter-for-audit__result_qfv_sqd_zfc"><div class="tasklabel"><p class="sectiontitle tasklabel">Result</p></div>
<p class="p">You can use the filter in the logical connection audit.</p>
</section>
</div>
<nav role="navigation"></nav><nav role="navigation" class="tasksNavigation"></nav><nav role="navigation" class="related-links"><div class="col-md-4"><dt>Related tasks</dt><dd><ul><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/task/run-audits.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/run-audits.html" class="link" title="The Telecom Discrepancy Audit validates the integrity of configuration items (CIs) and relationships across your telecom inventory using the CMDB Compliance framework.">Run Telecom Discrepancy audit</a></li><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/task/run-audits.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/run-audits.html#example-for-telecom-discrepancy-and-reconciliation" class="link" title="The following example illustrates how the audit works in a scenario.">Example for Telecom Discrepancy Audit and Remediation</a></li><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/task/configure-attribute-value-discrepancy-in-cmdb-360.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/configure-attribute-value-discrepancy-in-cmdb-360.html" class="link" title="Configure attribute comparison settings in CMDB 360 to detect data inconsistencies across multiple discovery sources.">Configure attribute value discrepancy in CMDB 360</a></li><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/task/control-ci-attribute-updates-using-reconciliation-rules.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/control-ci-attribute-updates-using-reconciliation-rules.html" class="link" title="To prevent specific attributes of a Configuration Item (CI) from being overwritten by Discovery or other data sources, use Reconciliation Rules. These rules define which data source is trusted to update a particular attribute when multiple sources provide values.">Control CI attribute updates using Reconciliation rules</a></li></ul></dd></div><div class="col-md-4"><dt>Related concepts</dt><dd><ul><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/concept/system-properties-affecting-telecom-discrepancy-identification-reconciliation.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/system-properties-affecting-telecom-discrepancy-identification-reconciliation.html" class="link" title="The system properties are part of the TSOM Visibility plugin (sn_tsom_core) and control the Telecom Discrepancy Identification & Reconciliation log (TSOM CMDB Audit). The TSOM Visibility plugin serves as an enabler for the TSOM Visibility applications, containing logic that is shared across the Telecom Discovery and Telecom Discrepancy Identification & Reconciliation solution.">System components installed with Telecom Discrepancy Identification & Reconciliation</a></li></ul></dd></div></nav>
</article></main></body></article> | {
"attachments": {
"all_attachments": null,
"topic_attachments": []
},
"available_languages": [
"enus"
],
"breadcrumbs": [
{
"title": "Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html"
},
{
"title": "Configuring Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/configuring-tsom.html"
},
{
"title": "Set up Telecom Visibility",
"topic_id": "product/tmt-telecom-service-operations-mgt/task/configuring-tsom-visibility.html"
},
{
"title": "Activate Telecom Discrepancy Identification and Reconciliation",
"topic_id": "product/tmt-telecom-service-operations-mgt/task/configure-telecom-reconciliation.html"
}
],
"breadcrumbs_html": "<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops\">Zurich Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html\">Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/configuring-tsom.html\">Configuring Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/configuring-tsom-visibility.html\">Set up Telecom Visibility</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/configure-telecom-reconciliation.html\">Activate Telecom Discrepancy Identification and Reconciliation</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<span class=\"active\">Configure filter for audit</span>",
"bundle_id": "zurich-telecom-service-ops",
"bundle_key": 2733,
"bundle_landing_page": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html",
"bundle_subtitle": null,
"bundle_title": "Zurich Telecommunications Service Operations Management",
"canonical_link": null,
"dates": {
"Added on": "2025-08-02T00:48:08.794016Z",
"Created on": "2025-07-12T00:00:00Z",
"Initial upload": "2025-07-30T22:24:33.519043Z",
"Updated on": "2025-07-31T00:00:00Z"
},
"dislike_url": "https://servicenow-be-prod.servicenow.com/dislike/55686965",
"dislikes": 0,
"es_archived_content": false,
"is_in_fav": false,
"is_liked": null,
"is_watched": false,
"keywords": [
" zurich zurich"
],
"labels": [
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "zurich",
"navtitle": "Zurich",
"outputclasses": [],
"subjectHeadId": "versions",
"subjectheadNavtitle": "Versions",
"visibility": "show-facet"
},
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "tsom",
"navtitle": "Telecommunications Service Operations Management",
"outputclasses": [],
"subjectHeadId": "products",
"subjectheadNavtitle": "Products",
"visibility": "show-facet"
}
],
"labels_text": "Versions > Zurich; Products > CRM and Industry Products > Telecommunications Media and Technology Assurance > Telecommunications Service Operations Management",
"like_url": "https://servicenow-be-prod.servicenow.com/like/55686965",
"likes": 0,
"metadata": {
"AI Search": null,
"AI Search Assist": null,
"Application Insights": null,
"Capabilities": null,
"Code Signing": null,
"Contextual Search": null,
"DC.contributor": null,
"DC.coverage": null,
"DC.creator": "ServiceNow",
"DC.date.created": "2025-07-12T18:23:09+05:30",
"DC.date.modified": "2025-07-31",
"DC.format": "HTML5",
"DC.identifier": "configure-certification-filter-for-audit",
"DC.language": null,
"DC.relation": "run-audits.html",
"DC.rights.owner": "(C) Copyright 2025",
"DC.subject": null,
"DC.type": "task",
"Data Discovery": null,
"Data Policy": null,
"Data Privacy": null,
"Discovery": null,
"External Content for AI Search": null,
"Field Administration": null,
"Field Normalization": null,
"Key Management Framework": null,
"Localization Framework": null,
"Now Platform": null,
"PlatSec": null,
"Platform": null,
"Platform Administration": null,
"Platform Performance": null,
"Platform Privacy": null,
"Proactive Triggers": null,
"Process Optimization": null,
"RN doc editing record number": null,
"Search Administration": null,
"Secrets Management": null,
"ServiceNow AI Platform": null,
"State Model": null,
"Subscription Management": null,
"Task Communications Management": null,
"Timeline Visualizations": null,
"User Administration": null,
"User Experience Analytics": null,
"Zing": null,
"ai-now-assist": null,
"app-name": null,
"app_route": null,
"azureapimanagemen": null,
"change-completed": null,
"change-item": null,
"change-request-id": null,
"change-request-reference": null,
"com.glide.embedded_help.category": null,
"component": null,
"copyright": "(C) Copyright 2025",
"crossroads": null,
"data": null,
"description": "Define filtering conditions to control the scope of Telecom Discrepancy audits. These filters ensure that audits run only on the desired set of CIs, improving performance and targeting accuracy.",
"dominant_bundle": null,
"erp-canvas-video": null,
"fsm-mobile": null,
"fsm-route": null,
"fsm-sched-opt": null,
"fsm-wrk-order": null,
"genai-round-7": null,
"generator": "DITA-OT",
"glossPartOfSpeech": null,
"glossStatus": null,
"guided setup": null,
"guided tours": null,
"keywords": null,
"min-toc": null,
"mini": null,
"mini-to truec": null,
"mini-toc": null,
"mini_toc": null,
"minitoc": null,
"modification": null,
"now-assist-app-gen-video": null,
"order": null,
"page-type": null,
"page-type ": null,
"prodname": null,
"product": null,
"product_name": null,
"release": null,
"resourceID": null,
"roles": null,
"route_page": null,
"route_params_listId": null,
"route_params_table": null,
"route_params_type": null,
"route_type": null,
"setconfigurationproperties": null,
"topic": null,
"translation-type": "source",
"version": null,
"workflow": "Customer and Industry",
"workplace-srvc-delvry-ditamap": null
},
"page_id": "product/tmt-telecom-service-operations-mgt/task/configure-certification-filter-for-audit.html",
"page_key": 55686965,
"preprocessed_PDF": "https://downloads.docs.servicenow.com/pdf/enus/servicenow-zurich-telecom-service-ops-enus.pdf",
"rating": null,
"read_time_data": {
"char_count": 2101,
"img_count": 1,
"read_time": 2,
"video_links": [
""
],
"word_count": 300
},
"related_links": [
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "The Telecom Discrepancy Audit validates the integrity of configuration items (CIs) and relationships across your telecom inventory using the CMDB Compliance framework.",
"title": "Run Telecom Discrepancy audit",
"topic": "/product/tmt-telecom-service-operations-mgt/task/run-audits.html",
"type": "task",
"url": null
},
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "The following example illustrates how the audit works in a scenario.",
"title": "Example for Telecom Discrepancy Audit and Remediation",
"topic": "/product/tmt-telecom-service-operations-mgt/task/run-audits.html",
"type": "task",
"url": null
},
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "The system properties are part of the TSOM Visibility plugin (sn_tsom_core) and control the Telecom Discrepancy Identification & Reconciliation log (TSOM CMDB Audit). The TSOM Visibility plugin serves as an enabler for the TSOM Visibility applications, containing logic that is shared across the Telecom Discovery and Telecom Discrepancy Identification & Reconciliation solution.",
"title": "System components installed with Telecom Discrepancy Identification & Reconciliation",
"topic": "/product/tmt-telecom-service-operations-mgt/concept/system-properties-affecting-telecom-discrepancy-identification-reconciliation.html",
"type": "concept",
"url": null
},
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "Configure attribute comparison settings in CMDB 360 to detect data inconsistencies across multiple discovery sources.",
"title": "Configure attribute value discrepancy in CMDB 360",
"topic": "/product/tmt-telecom-service-operations-mgt/task/configure-attribute-value-discrepancy-in-cmdb-360.html",
"type": "task",
"url": null
},
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "To prevent specific attributes of a Configuration Item (CI) from being overwritten by Discovery or other data sources, use Reconciliation Rules. These rules define which data source is trusted to update a particular attribute when multiple sources provide values.",
"title": "Control CI attribute updates using Reconciliation rules",
"topic": "/product/tmt-telecom-service-operations-mgt/task/control-ci-attribute-updates-using-reconciliation-rules.html",
"type": "task",
"url": null
}
],
"search_title": null,
"title": "Configure filter for audit",
"topic_cluster": {
"clustered_by": {
"enabled": true,
"primary_key": "versions",
"primary_sort": "top-down",
"type": "subjecthead"
},
"clustered_labels": [
"versions"
],
"clustered_topics": [],
"clustering_title": "Zurich"
},
"topic_html": "<article class=\"hascomments\" data-page=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/configure-certification-filter-for-audit.html\" id=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/configure-certification-filter-for-audit.html\"><body id=\"configure-certification-filter-for-audit\"><main role=\"main\"><article role=\"article\" class=\"dita\" id=\"configure-certification-filter-for-audit\" aria-labelledby=\"title_configure-certification-filter-for-audit\">\n <h1 class=\"title topictitle1\" id=\"title_configure-certification-filter-for-audit\">Configure filter for audit</h1>\n \n \n <div class=\"body taskbody\"><p class=\"shortdesc\">Define filtering conditions to control the scope of Telecom Discrepancy audits. These filters ensure that audits run only on the desired set of CIs, improving performance and targeting accuracy.</p>\n <section class=\"section prereq\" id=\"configure-certification-filter-for-audit__task-prereq\"><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">Before you begin</p></div>\n <p class=\"p\">Role required: admin</p>\n </section>\n <section class=\"section context\"><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">About this task</p></div>\n <div class=\"p\">Understanding Filtering Conditions in Telecom Discrepancy Audits<ul class=\"ul\" id=\"configure-certification-filter-for-audit__ul_sz3_z3d_zfc\">\n <li class=\"li\">Audits use filtering conditions to narrow the scope of CIs being evaluated.</li>\n <li class=\"li\">Filtering conditions are essential for narrowing down audit targets.</li>\n <li class=\"li\">You can define and modify conditions per audit instance to meet specific audit requirements.</li>\n <li class=\"li\">Filtering by <code class=\"ph codeph\">discovery_source</code> is a common condition to filter records associated with particular integration sources (e.g., TSOM and Altiplano). Additionally, you can customize the filter according\n to the audit requirements.</li>\n <li class=\"li\">Each version of the audit can have a different filtering condition.</li>\n </ul></div>\n <div class=\"p\">The following are the audit filters:<ol class=\"ol\" id=\"configure-certification-filter-for-audit__ol_bvh_kjd_zfc\">\n <li class=\"li\">Telecom Logical Connections Discrepancy Audit: This audit runs at the logical connection table. The default filter condition is defined as <code class=\"ph codeph\">discovery_source</code> like TSOM. This condition is applied on\n each CI in the logical connection table.</li>\n <li class=\"li\">Telecom Network Topology Discrepancy Audit: This audit runs at the network topology table. The default filter condition is defined as <code class=\"ph codeph\">discovery_source</code> like TSOM. This condition is applied on each CI\n in the network topology table.</li>\n <li class=\"li\">Telecom Discrepancy Audit: This audit runs at the relationships table. The default filter condition is defined as <code class=\"ph codeph\">discovery_source</code> like TSOM. This condition is applied on each CI at the equipment\n level.</li>\n </ol></div>\n <p class=\"p\">The following screenshot helps to understand the user interface of the certification filter <img src=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/../images/certification-filter.png?_LANG=enus\" class=\"image\" id=\"configure-certification-filter-for-audit__image_cgq_qqd_zfc\" alt=\"The user interface of TSOM certification and logical connection discrepancy audit filter.\"/>.</p>\n </section>\n <section><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">Procedure</p></div><ol class=\"ol steps\"><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">Navigate to <span class=\"ph menucascade\"><span class=\"ph uicontrol\">All</span><abbr> > </abbr><span class=\"ph uicontrol\">Certification</span><abbr> > </abbr><span class=\"ph uicontrol\">Filters</span></span>.</span>\n </li><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">Select <span class=\"ph uicontrol\">New</span>.</span>\n <div class=\"itemgroup stepresult\">The certification filter interface appears.</div>\n </li><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">Fill in the fields.</span>\n <div class=\"itemgroup info\">For more guidance, see <a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/task//csh\" href=\"https://servicenow-be-prod.servicenow.com/csh?topicname=t_CreatingCertificationFilters&version=zurich&pubname=zurich-servicenow-platform\" class=\"xref\">Create a certification filter</a>.</div>\n </li><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">Add the filter conditions.</span>\n <div class=\"itemgroup info\">For example, Discovery source contains TSOM.</div>\n </li><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">Select <span class=\"ph uicontrol\">Submit</span>.</span>\n <div class=\"itemgroup stepresult\">The filter is created.</div>\n </li></ol></section>\n <section class=\"section result\" id=\"configure-certification-filter-for-audit__result_qfv_sqd_zfc\"><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">Result</p></div>\n <p class=\"p\">You can use the filter in the logical connection audit.</p>\n </section>\n </div>\n <nav role=\"navigation\"></nav><nav role=\"navigation\" class=\"tasksNavigation\"></nav><nav role=\"navigation\" class=\"related-links\"><div class=\"col-md-4\"><dt>Related tasks</dt><dd><ul><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/task/run-audits.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/run-audits.html\" class=\"link\" title=\"The Telecom Discrepancy Audit validates the integrity of configuration items (CIs) and relationships across your telecom inventory using the CMDB Compliance framework.\">Run Telecom Discrepancy audit</a></li><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/task/run-audits.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/run-audits.html#example-for-telecom-discrepancy-and-reconciliation\" class=\"link\" title=\"The following example illustrates how the audit works in a scenario.\">Example for Telecom Discrepancy Audit and Remediation</a></li><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/task/configure-attribute-value-discrepancy-in-cmdb-360.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/configure-attribute-value-discrepancy-in-cmdb-360.html\" class=\"link\" title=\"Configure attribute comparison settings in CMDB 360 to detect data inconsistencies across multiple discovery sources.\">Configure attribute value discrepancy in CMDB 360</a></li><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/task/control-ci-attribute-updates-using-reconciliation-rules.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/control-ci-attribute-updates-using-reconciliation-rules.html\" class=\"link\" title=\"To prevent specific attributes of a Configuration Item (CI) from being overwritten by Discovery or other data sources, use Reconciliation Rules. These rules define which data source is trusted to update a particular attribute when multiple sources provide values.\">Control CI attribute updates using Reconciliation rules</a></li></ul></dd></div><div class=\"col-md-4\"><dt>Related concepts</dt><dd><ul><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept/system-properties-affecting-telecom-discrepancy-identification-reconciliation.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/system-properties-affecting-telecom-discrepancy-identification-reconciliation.html\" class=\"link\" title=\"The system properties are part of the TSOM Visibility plugin (sn_tsom_core) and control the Telecom Discrepancy Identification & Reconciliation log (TSOM CMDB Audit). The TSOM Visibility plugin serves as an enabler for the TSOM Visibility applications, containing logic that is shared across the Telecom Discovery and Telecom Discrepancy Identification & Reconciliation solution.\">System components installed with Telecom Discrepancy Identification & Reconciliation</a></li></ul></dd></div></nav>\n</article></main></body></article>",
"topic_language": "enus",
"views": 0,
"your_rating": null
} | # Configure filter for audit
Define filtering conditions to control the scope of Telecom Discrepancy audits. These filters ensure that audits run only on the desired set of CIs, improving performance and targeting accuracy.
## Before you begin
Role required: admin
## About this task
Understanding Filtering Conditions in Telecom Discrepancy Audits
* Audits use filtering conditions to narrow the scope of CIs being evaluated.
* Filtering conditions are essential for narrowing down audit targets.
* You can define and modify conditions per audit instance to meet specific audit requirements.
* Filtering by `discovery_source` is a common condition to filter records associated with particular integration sources (e.g., TSOM and Altiplano). Additionally, you can customize the filter according
to the audit requirements.
* Each version of the audit can have a different filtering condition.
The following are the audit filters:
1. Telecom Logical Connections Discrepancy Audit: This audit runs at the logical connection table. The default filter condition is defined as `discovery_source` like TSOM. This condition is applied on
each CI in the logical connection table.
2. Telecom Network Topology Discrepancy Audit: This audit runs at the network topology table. The default filter condition is defined as `discovery_source` like TSOM. This condition is applied on each CI
in the network topology table.
3. Telecom Discrepancy Audit: This audit runs at the relationships table. The default filter condition is defined as `discovery_source` like TSOM. This condition is applied on each CI at the equipment
level.
The following screenshot helps to understand the user interface of the certification filter .
## Procedure
1. Navigate to All > Certification > Filters.
2. Select New.
The certification filter interface appears.
3. Fill in the fields.
For more guidance, see Create a certification filter.
4. Add the filter conditions.
For example, Discovery source contains TSOM.
5. Select Submit.
The filter is created.
### Result
You can use the filter in the logical connection audit.
| ---
title: Configure filter for audit
description: Define filtering conditions to control the scope of Telecom Discrepancy
audits. These filters ensure that audits run only on the desired set of CIs, improving
performance and targeting accuracy.
keywords: []
breadcrumbs:
- Telecommunications Service Operations Management
- Configuring Telecommunications Service Operations Management
- Set up Telecom Visibility
- Activate Telecom Discrepancy Identification and Reconciliation
---
# Configure filter for audit
Define filtering conditions to control the scope of Telecom Discrepancy audits. These filters ensure that audits run only on the desired set of CIs, improving performance and targeting accuracy.
## Before you begin
Role required: admin
## About this task
Understanding Filtering Conditions in Telecom Discrepancy Audits
* Audits use filtering conditions to narrow the scope of CIs being evaluated.
* Filtering conditions are essential for narrowing down audit targets.
* You can define and modify conditions per audit instance to meet specific audit requirements.
* Filtering by `discovery_source` is a common condition to filter records associated with particular integration sources (e.g., TSOM and Altiplano). Additionally, you can customize the filter according
to the audit requirements.
* Each version of the audit can have a different filtering condition.
The following are the audit filters:
1. Telecom Logical Connections Discrepancy Audit: This audit runs at the logical connection table. The default filter condition is defined as `discovery_source` like TSOM. This condition is applied on
each CI in the logical connection table.
2. Telecom Network Topology Discrepancy Audit: This audit runs at the network topology table. The default filter condition is defined as `discovery_source` like TSOM. This condition is applied on each CI
in the network topology table.
3. Telecom Discrepancy Audit: This audit runs at the relationships table. The default filter condition is defined as `discovery_source` like TSOM. This condition is applied on each CI at the equipment
level.
The following screenshot helps to understand the user interface of the certification filter .
## Procedure
1. Navigate to All > Certification > Filters.
2. Select New.
The certification filter interface appears.
3. Fill in the fields.
For more guidance, see Create a certification filter.
4. Add the filter conditions.
For example, Discovery source contains TSOM.
5. Select Submit.
The filter is created.
### Result
You can use the filter in the logical connection audit.
|
https://www.servicenow.com/docs/en-US/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/configure-concurrent-import-and-parallel-loading.html | https://servicenow-be-prod.servicenow.com/api/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/configure-concurrent-import-and-parallel-loading.html | 2025-08-02 | daily | 0.5 | 268.xml | en-US | zurich-telecom-service-ops | product/tmt-telecom-service-operations-mgt/task/configure-concurrent-import-and-parallel-loading.html | zurich | Configure concurrent import and parallel loading for Nokia Altiplano | Improve the efficiency of large data imports from Nokia Altiplano by configuring concurrent imports and enabling parallel loading. This configuration allows the platform to run multiple data import and transformation jobs simultaneously. | [] | [
"Telecommunications Service Operations Management",
"Configuring Telecommunications Service Operations Management",
"Set up Telecom Visibility",
"Configuring Nokia Altiplano service graph connector"
] | <article class="hascomments" data-page="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/configure-concurrent-import-and-parallel-loading.html" id="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/configure-concurrent-import-and-parallel-loading.html"><body id="configure-concurrent-import-and-parallel-loading"><main role="main"><article role="article" class="dita" id="configure-concurrent-import-and-parallel-loading" aria-labelledby="title_configure-concurrent-import-and-parallel-loading">
<h1 class="title topictitle1" id="title_configure-concurrent-import-and-parallel-loading">Configure concurrent import and parallel loading for Nokia Altiplano</h1>
<div class="body taskbody"><p class="shortdesc">Improve the efficiency of large data imports from Nokia Altiplano by configuring concurrent imports and enabling parallel loading. This configuration allows the platform to run multiple data import and transformation jobs
simultaneously.</p>
<section class="section prereq" id="configure-concurrent-import-and-parallel-loading__task-prereq"><div class="tasklabel"><p class="sectiontitle tasklabel">Before you begin</p></div>
<p class="p">Role required: admin</p>
</section>
<section class="section context" id="configure-concurrent-import-and-parallel-loading__context_adx_r5z_yfc"><div class="tasklabel"><p class="sectiontitle tasklabel">About this task</p></div>
<p class="p">Concurrent import and parallel loading improve performance by dividing large datasets into smaller partitions, allowing multiple transformation and collection jobs to run in parallel. This setup is useful when importing large
volumes of equipment, logical connections, and network topology data during bulk or filtered discoveries.</p>
<div class="p">Use the following guidance to optimize performance:<ul class="ul" id="configure-concurrent-import-and-parallel-loading__ul_yzx_2wz_yfc">
<li class="li">If transformation is slow: Enable Concurrent import in the import schedule.</li>
<li class="li">If data collection is slow: In addition to enabling concurrent import, configure Parallel loading in the data source and update the system property.</li>
</ul><div class="note note note_note"><span class="note__title">Note:</span> Parallel loading works in addition to concurrent import. It does not replace it.</div></div>
</section>
<section><div class="tasklabel"><p class="sectiontitle tasklabel">Procedure</p></div><ol class="ol steps"><li class="li step">
<span class="ph cmd">Navigate to <span class="ph menucascade"><span class="ph uicontrol">All</span><abbr> > </abbr><span class="ph uicontrol">Service Graph Connectors</span><abbr> > </abbr><span class="ph uicontrol">Nokia Altiplano</span><abbr> > </abbr><span class="ph uicontrol">Import Schedule</span></span>.</span>
</li><li class="li step">
<span class="ph cmd">Configure concurrent import or concurrent import</span>
<div class="table-wrap"><table count-columns="2" border="1" frame="hsides" rules="rows" cellpadding="4" cellspacing="0" summary="" class="simpletable choicetable choicetableborder" id="configure-concurrent-import-and-parallel-loading__choicetable_mpn_2vz_yfc"><colgroup><col style="width:50%"/><col style="width:50%"/></colgroup><thead class="thead"><tr class="sthead chhead"><th scope="col" class="stentry choptionhd" style="vertical-align:bottom;text-align:left;">To</th><th scope="col" class="stentry chdeschd" style="vertical-align:bottom;text-align:left;">Do the following</th></tr></thead><tbody><tr class="strow chrow">
<td style="vertical-align:top;" headers="d7430e93-option" id="d7430e106" class="stentry choption">To enable concurrent import</td>
<td style="vertical-align:top;" class="stentry chdesc">
<ol class="ol" type="a" id="configure-concurrent-import-and-parallel-loading__ol_xxs_lvz_yfc">
<li class="li">Navigate to the <span class="ph uicontrol">Import Schedule</span> for the discovery job.</li>
<li class="li">Select the <span class="ph uicontrol">Concurrent import</span> checkbox.</li>
<li class="li">Set the <span class="ph uicontrol">Partition method</span> to <span class="ph uicontrol">Custom size</span>.</li>
<li class="li">In the <span class="ph uicontrol">Partition size</span>e field, enter the number of records per partition (for example, 1000).</li>
</ol>
<div class="note note note_note"><span class="note__title">Note:</span> The system splits the dataset into import sets based on the partition size. Each import set is processed in parallel, improving the speed of data transformation.</div>
</td>
</tr><tr class="strow chrow">
<td style="vertical-align:top;" headers="d7430e93-option" id="d7430e148" class="stentry choption">Configure parallel loading in the data source </td>
<td style="vertical-align:top;" class="stentry chdesc">
<ol class="ol" type="a" id="configure-concurrent-import-and-parallel-loading__ol_x5d_tvz_yfc">
<li class="li">Navigate to the corresponding Data Source record.</li>
<li class="li">Select the <span class="ph uicontrol">Parallel loading</span> checkbox.</li>
<li class="li">Navigate to Nokia Altiplano > Properties.</li>
<li class="li">Open the system property <span class="keyword parmname">sn_sgc_altiplano.parallel_number_of_data_source_jobs</span></li>
<li class="li">Set the value to the desired number of parallel jobs (for example, <code class="ph codeph">3</code>).<div class="note note note_note"><span class="note__title">Note:</span> By default, the number of data source jobs is set to <code class="ph codeph">1</code>. Increasing this value allows the
platform to execute multiple data collection jobs concurrently.</div></li>
</ol>
</td>
</tr></tbody></table></div>
</li></ol></section>
</div>
<nav role="navigation"></nav><nav role="navigation" class="tasksNavigation"></nav><nav role="navigation" class="related-links"><div class="col-md-4"><dt>Related tasks</dt><dd><ul><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/task/initial-setup-procedure.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/initial-setup-procedure.html" class="link" title="Learn how to install and configure the Service Graph Connector for Nokia Altiplano, including optional demo data, connectivity setup, and data collection schedules.">Install and configure the Nokia Altiplano</a></li></ul></dd></div><div class="col-md-4"><dt>Related concepts</dt><dd><ul><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/concept/data-mapping.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/data-mapping.html" class="link" title="Use the Service Graph Connector for Nokia Altiplano to map discovered physical and logical network resources to telecom-aligned Configuration Item (CI) classes in the CMDB. The connector supports consistent service modeling, visibility into chassis-level components, and automation of logical and physical relationships.">Mapping Nokia Altiplano CIs and Relationships in CMDB</a></li></ul></dd></div><div class="col-md-4"><dt>Related reference</dt><dd><ul><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/reference/properties-installed-with-nokia-altiplano.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/reference/properties-installed-with-nokia-altiplano.html" class="link" title="System properties control how the connector operates, including discovery options and performance settings.">System components installed with Nokia Altiplano</a></li></ul></dd></div></nav>
</article></main></body></article> | {
"attachments": {
"all_attachments": null,
"topic_attachments": []
},
"available_languages": [
"enus"
],
"breadcrumbs": [
{
"title": "Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html"
},
{
"title": "Configuring Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/configuring-tsom.html"
},
{
"title": "Set up Telecom Visibility",
"topic_id": "product/tmt-telecom-service-operations-mgt/task/configuring-tsom-visibility.html"
},
{
"title": "Configuring Nokia Altiplano service graph connector",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/configuring-service-graph-connector-nokia-altiplano.html"
}
],
"breadcrumbs_html": "<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops\">Zurich Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html\">Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/configuring-tsom.html\">Configuring Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/configuring-tsom-visibility.html\">Set up Telecom Visibility</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/configuring-service-graph-connector-nokia-altiplano.html\">Configuring Nokia Altiplano service graph connector</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<span class=\"active\">Configure concurrent import and parallel loading for Nokia Altiplano</span>",
"bundle_id": "zurich-telecom-service-ops",
"bundle_key": 2733,
"bundle_landing_page": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html",
"bundle_subtitle": null,
"bundle_title": "Zurich Telecommunications Service Operations Management",
"canonical_link": null,
"dates": {
"Added on": "2025-08-02T00:48:08.794016Z",
"Created on": "2025-07-13T00:00:00Z",
"Initial upload": "2025-07-30T22:24:33.519043Z",
"Updated on": "2025-07-31T00:00:00Z"
},
"dislike_url": "https://servicenow-be-prod.servicenow.com/dislike/55686966",
"dislikes": 0,
"es_archived_content": false,
"is_in_fav": false,
"is_liked": null,
"is_watched": false,
"keywords": [
" zurich zurich"
],
"labels": [
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "zurich",
"navtitle": "Zurich",
"outputclasses": [],
"subjectHeadId": "versions",
"subjectheadNavtitle": "Versions",
"visibility": "show-facet"
},
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "tsom",
"navtitle": "Telecommunications Service Operations Management",
"outputclasses": [],
"subjectHeadId": "products",
"subjectheadNavtitle": "Products",
"visibility": "show-facet"
}
],
"labels_text": "Versions > Zurich; Products > CRM and Industry Products > Telecommunications Media and Technology Assurance > Telecommunications Service Operations Management",
"like_url": "https://servicenow-be-prod.servicenow.com/like/55686966",
"likes": 0,
"metadata": {
"AI Search": null,
"AI Search Assist": null,
"Application Insights": null,
"Capabilities": null,
"Code Signing": null,
"Contextual Search": null,
"DC.contributor": null,
"DC.coverage": null,
"DC.creator": "ServiceNow",
"DC.date.created": "2025-07-13T22:23:44+05:30",
"DC.date.modified": "2025-07-31",
"DC.format": "HTML5",
"DC.identifier": "configure-concurrent-import-and-parallel-loading",
"DC.language": null,
"DC.relation": "initial-setup-procedure.html",
"DC.rights.owner": "(C) Copyright 2025",
"DC.subject": null,
"DC.type": "task",
"Data Discovery": null,
"Data Policy": null,
"Data Privacy": null,
"Discovery": null,
"External Content for AI Search": null,
"Field Administration": null,
"Field Normalization": null,
"Key Management Framework": null,
"Localization Framework": null,
"Now Platform": null,
"PlatSec": null,
"Platform": null,
"Platform Administration": null,
"Platform Performance": null,
"Platform Privacy": null,
"Proactive Triggers": null,
"Process Optimization": null,
"RN doc editing record number": null,
"Search Administration": null,
"Secrets Management": null,
"ServiceNow AI Platform": null,
"State Model": null,
"Subscription Management": null,
"Task Communications Management": null,
"Timeline Visualizations": null,
"User Administration": null,
"User Experience Analytics": null,
"Zing": null,
"ai-now-assist": null,
"app-name": null,
"app_route": null,
"azureapimanagemen": null,
"change-completed": null,
"change-item": null,
"change-request-id": null,
"change-request-reference": null,
"com.glide.embedded_help.category": null,
"component": null,
"copyright": "(C) Copyright 2025",
"crossroads": null,
"data": null,
"description": "Improve the efficiency of large data imports from Nokia Altiplano by configuring concurrent imports and enabling parallel loading. This configuration allows the platform to run multiple data import and transformation jobs simultaneously.",
"dominant_bundle": null,
"erp-canvas-video": null,
"fsm-mobile": null,
"fsm-route": null,
"fsm-sched-opt": null,
"fsm-wrk-order": null,
"genai-round-7": null,
"generator": "DITA-OT",
"glossPartOfSpeech": null,
"glossStatus": null,
"guided setup": null,
"guided tours": null,
"keywords": null,
"min-toc": null,
"mini": null,
"mini-to truec": null,
"mini-toc": null,
"mini_toc": null,
"minitoc": null,
"modification": null,
"now-assist-app-gen-video": null,
"order": null,
"page-type": null,
"page-type ": null,
"prodname": null,
"product": null,
"product_name": null,
"release": null,
"resourceID": null,
"roles": null,
"route_page": null,
"route_params_listId": null,
"route_params_table": null,
"route_params_type": null,
"route_type": null,
"setconfigurationproperties": null,
"topic": null,
"translation-type": "source",
"version": null,
"workflow": "Customer and Industry",
"workplace-srvc-delvry-ditamap": null
},
"page_id": "product/tmt-telecom-service-operations-mgt/task/configure-concurrent-import-and-parallel-loading.html",
"page_key": 55686966,
"preprocessed_PDF": "https://downloads.docs.servicenow.com/pdf/enus/servicenow-zurich-telecom-service-ops-enus.pdf",
"rating": null,
"read_time_data": {
"char_count": 2103,
"img_count": 0,
"read_time": 2,
"video_links": [
""
],
"word_count": 302
},
"related_links": [
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "Learn how to install and configure the Service Graph Connector for Nokia Altiplano, including optional demo data, connectivity setup, and data collection schedules.",
"title": "Install and configure the Nokia Altiplano",
"topic": "/product/tmt-telecom-service-operations-mgt/task/initial-setup-procedure.html",
"type": "task",
"url": null
},
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "Use the Service Graph Connector for Nokia Altiplano to map discovered physical and logical network resources to telecom-aligned Configuration Item (CI) classes in the CMDB. The connector supports consistent service modeling, visibility into chassis-level components, and automation of logical and physical relationships.",
"title": "Mapping Nokia Altiplano CIs and Relationships in CMDB",
"topic": "/product/tmt-telecom-service-operations-mgt/concept/data-mapping.html",
"type": "concept",
"url": null
},
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "System properties control how the connector operates, including discovery options and performance settings.",
"title": "System components installed with Nokia Altiplano",
"topic": "/product/tmt-telecom-service-operations-mgt/reference/properties-installed-with-nokia-altiplano.html",
"type": "reference",
"url": null
}
],
"search_title": null,
"title": "Configure concurrent import and parallel loading for Nokia Altiplano",
"topic_cluster": {
"clustered_by": {
"enabled": true,
"primary_key": "versions",
"primary_sort": "top-down",
"type": "subjecthead"
},
"clustered_labels": [
"versions"
],
"clustered_topics": [],
"clustering_title": "Zurich"
},
"topic_html": "<article class=\"hascomments\" data-page=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/configure-concurrent-import-and-parallel-loading.html\" id=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/configure-concurrent-import-and-parallel-loading.html\"><body id=\"configure-concurrent-import-and-parallel-loading\"><main role=\"main\"><article role=\"article\" class=\"dita\" id=\"configure-concurrent-import-and-parallel-loading\" aria-labelledby=\"title_configure-concurrent-import-and-parallel-loading\">\n <h1 class=\"title topictitle1\" id=\"title_configure-concurrent-import-and-parallel-loading\">Configure concurrent import and parallel loading for Nokia Altiplano</h1>\n \n \n <div class=\"body taskbody\"><p class=\"shortdesc\">Improve the efficiency of large data imports from Nokia Altiplano by configuring concurrent imports and enabling parallel loading. This configuration allows the platform to run multiple data import and transformation jobs\n simultaneously.</p>\n <section class=\"section prereq\" id=\"configure-concurrent-import-and-parallel-loading__task-prereq\"><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">Before you begin</p></div>\n <p class=\"p\">Role required: admin</p>\n </section>\n <section class=\"section context\" id=\"configure-concurrent-import-and-parallel-loading__context_adx_r5z_yfc\"><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">About this task</p></div>\n <p class=\"p\">Concurrent import and parallel loading improve performance by dividing large datasets into smaller partitions, allowing multiple transformation and collection jobs to run in parallel. This setup is useful when importing large\n volumes of equipment, logical connections, and network topology data during bulk or filtered discoveries.</p>\n <div class=\"p\">Use the following guidance to optimize performance:<ul class=\"ul\" id=\"configure-concurrent-import-and-parallel-loading__ul_yzx_2wz_yfc\">\n <li class=\"li\">If transformation is slow: Enable Concurrent import in the import schedule.</li>\n <li class=\"li\">If data collection is slow: In addition to enabling concurrent import, configure Parallel loading in the data source and update the system property.</li>\n </ul><div class=\"note note note_note\"><span class=\"note__title\">Note:</span> Parallel loading works in addition to concurrent import. It does not replace it.</div></div>\n </section>\n <section><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">Procedure</p></div><ol class=\"ol steps\"><li class=\"li step\">\n <span class=\"ph cmd\">Navigate to <span class=\"ph menucascade\"><span class=\"ph uicontrol\">All</span><abbr> > </abbr><span class=\"ph uicontrol\">Service Graph Connectors</span><abbr> > </abbr><span class=\"ph uicontrol\">Nokia Altiplano</span><abbr> > </abbr><span class=\"ph uicontrol\">Import Schedule</span></span>.</span>\n </li><li class=\"li step\">\n <span class=\"ph cmd\">Configure concurrent import or concurrent import</span>\n <div class=\"table-wrap\"><table count-columns=\"2\" border=\"1\" frame=\"hsides\" rules=\"rows\" cellpadding=\"4\" cellspacing=\"0\" summary=\"\" class=\"simpletable choicetable choicetableborder\" id=\"configure-concurrent-import-and-parallel-loading__choicetable_mpn_2vz_yfc\"><colgroup><col style=\"width:50%\"/><col style=\"width:50%\"/></colgroup><thead class=\"thead\"><tr class=\"sthead chhead\"><th scope=\"col\" class=\"stentry choptionhd\" style=\"vertical-align:bottom;text-align:left;\">To</th><th scope=\"col\" class=\"stentry chdeschd\" style=\"vertical-align:bottom;text-align:left;\">Do the following</th></tr></thead><tbody><tr class=\"strow chrow\">\n <td style=\"vertical-align:top;\" headers=\"d7430e93-option\" id=\"d7430e106\" class=\"stentry choption\">To enable concurrent import</td>\n <td style=\"vertical-align:top;\" class=\"stentry chdesc\">\n <ol class=\"ol\" type=\"a\" id=\"configure-concurrent-import-and-parallel-loading__ol_xxs_lvz_yfc\">\n <li class=\"li\">Navigate to the <span class=\"ph uicontrol\">Import Schedule</span> for the discovery job.</li>\n <li class=\"li\">Select the <span class=\"ph uicontrol\">Concurrent import</span> checkbox.</li>\n <li class=\"li\">Set the <span class=\"ph uicontrol\">Partition method</span> to <span class=\"ph uicontrol\">Custom size</span>.</li>\n <li class=\"li\">In the <span class=\"ph uicontrol\">Partition size</span>e field, enter the number of records per partition (for example, 1000).</li>\n </ol>\n <div class=\"note note note_note\"><span class=\"note__title\">Note:</span> The system splits the dataset into import sets based on the partition size. Each import set is processed in parallel, improving the speed of data transformation.</div>\n </td>\n </tr><tr class=\"strow chrow\">\n <td style=\"vertical-align:top;\" headers=\"d7430e93-option\" id=\"d7430e148\" class=\"stentry choption\">Configure parallel loading in the data source </td>\n <td style=\"vertical-align:top;\" class=\"stentry chdesc\">\n <ol class=\"ol\" type=\"a\" id=\"configure-concurrent-import-and-parallel-loading__ol_x5d_tvz_yfc\">\n <li class=\"li\">Navigate to the corresponding Data Source record.</li>\n <li class=\"li\">Select the <span class=\"ph uicontrol\">Parallel loading</span> checkbox.</li>\n <li class=\"li\">Navigate to Nokia Altiplano > Properties.</li>\n <li class=\"li\">Open the system property <span class=\"keyword parmname\">sn_sgc_altiplano.parallel_number_of_data_source_jobs</span></li>\n <li class=\"li\">Set the value to the desired number of parallel jobs (for example, <code class=\"ph codeph\">3</code>).<div class=\"note note note_note\"><span class=\"note__title\">Note:</span> By default, the number of data source jobs is set to <code class=\"ph codeph\">1</code>. Increasing this value allows the\n platform to execute multiple data collection jobs concurrently.</div></li>\n </ol>\n </td>\n </tr></tbody></table></div>\n </li></ol></section>\n </div>\n <nav role=\"navigation\"></nav><nav role=\"navigation\" class=\"tasksNavigation\"></nav><nav role=\"navigation\" class=\"related-links\"><div class=\"col-md-4\"><dt>Related tasks</dt><dd><ul><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/task/initial-setup-procedure.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/initial-setup-procedure.html\" class=\"link\" title=\"Learn how to install and configure the Service Graph Connector for Nokia Altiplano, including optional demo data, connectivity setup, and data collection schedules.\">Install and configure the Nokia Altiplano</a></li></ul></dd></div><div class=\"col-md-4\"><dt>Related concepts</dt><dd><ul><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept/data-mapping.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/data-mapping.html\" class=\"link\" title=\"Use the Service Graph Connector for Nokia Altiplano to map discovered physical and logical network resources to telecom-aligned Configuration Item (CI) classes in the CMDB. The connector supports consistent service modeling, visibility into chassis-level components, and automation of logical and physical relationships.\">Mapping Nokia Altiplano CIs and Relationships in CMDB</a></li></ul></dd></div><div class=\"col-md-4\"><dt>Related reference</dt><dd><ul><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/reference/properties-installed-with-nokia-altiplano.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/reference/properties-installed-with-nokia-altiplano.html\" class=\"link\" title=\"System properties control how the connector operates, including discovery options and performance settings.\">System components installed with Nokia Altiplano</a></li></ul></dd></div></nav>\n</article></main></body></article>",
"topic_language": "enus",
"views": 0,
"your_rating": null
} | # Configure concurrent import and parallel loading for Nokia Altiplano
Improve the efficiency of large data imports from Nokia Altiplano by configuring concurrent imports and enabling parallel loading. This configuration allows the platform to run multiple data import and transformation jobs
simultaneously.
## Before you begin
Role required: admin
## About this task
Concurrent import and parallel loading improve performance by dividing large datasets into smaller partitions, allowing multiple transformation and collection jobs to run in parallel. This setup is useful when importing large
volumes of equipment, logical connections, and network topology data during bulk or filtered discoveries.
Use the following guidance to optimize performance:
* If transformation is slow: Enable Concurrent import in the import schedule.
* If data collection is slow: In addition to enabling concurrent import, configure Parallel loading in the data source and update the system property.
Note: Parallel loading works in addition to concurrent import. It does not replace it.
## Procedure
1. Navigate to All > Service Graph Connectors > Nokia Altiplano > Import Schedule.
2. Configure concurrent import or concurrent import
| To | Do the following |
| --- | --- |
| To enable concurrent import | 1. Navigate to the Import Schedule for the discovery job. 2. Select the Concurrent import checkbox. 3. Set the Partition method to Custom size. 4. In the Partition sizee field, enter the number of records per partition (for example, 1000).Note: The system splits the dataset into import sets based on the partition size. Each import set is processed in parallel, improving the speed of data transformation. |
| Configure parallel loading in the data source | 1. Navigate to the corresponding Data Source record. 2. Select the Parallel loading checkbox. 3. Navigate to Nokia Altiplano > Properties. 4. Open the system property sn\_sgc\_altiplano.parallel\_number\_of\_data\_source\_jobs 5. Set the value to the desired number of parallel jobs (for example, `3`).Note: By default, the number of data source jobs is set to `1`. Increasing this value allows the platform to execute multiple data collection jobs concurrently. |
| ---
title: Configure concurrent import and parallel loading for Nokia Altiplano
description: Improve the efficiency of large data imports from Nokia Altiplano by
configuring concurrent imports and enabling parallel loading. This configuration
allows the platform to run multiple data import and transformation jobs simultaneously.
keywords: []
breadcrumbs:
- Telecommunications Service Operations Management
- Configuring Telecommunications Service Operations Management
- Set up Telecom Visibility
- Configuring Nokia Altiplano service graph connector
---
# Configure concurrent import and parallel loading for Nokia Altiplano
Improve the efficiency of large data imports from Nokia Altiplano by configuring concurrent imports and enabling parallel loading. This configuration allows the platform to run multiple data import and transformation jobs
simultaneously.
## Before you begin
Role required: admin
## About this task
Concurrent import and parallel loading improve performance by dividing large datasets into smaller partitions, allowing multiple transformation and collection jobs to run in parallel. This setup is useful when importing large
volumes of equipment, logical connections, and network topology data during bulk or filtered discoveries.
Use the following guidance to optimize performance:
* If transformation is slow: Enable Concurrent import in the import schedule.
* If data collection is slow: In addition to enabling concurrent import, configure Parallel loading in the data source and update the system property.
Note: Parallel loading works in addition to concurrent import. It does not replace it.
## Procedure
1. Navigate to All > Service Graph Connectors > Nokia Altiplano > Import Schedule.
2. Configure concurrent import or concurrent import
| To | Do the following |
| --- | --- |
| To enable concurrent import | 1. Navigate to the Import Schedule for the discovery job. 2. Select the Concurrent import checkbox. 3. Set the Partition method to Custom size. 4. In the Partition sizee field, enter the number of records per partition (for example, 1000).Note: The system splits the dataset into import sets based on the partition size. Each import set is processed in parallel, improving the speed of data transformation. |
| Configure parallel loading in the data source | 1. Navigate to the corresponding Data Source record. 2. Select the Parallel loading checkbox. 3. Navigate to Nokia Altiplano > Properties. 4. Open the system property sn\_sgc\_altiplano.parallel\_number\_of\_data\_source\_jobs 5. Set the value to the desired number of parallel jobs (for example, `3`).Note: By default, the number of data source jobs is set to `1`. Increasing this value allows the platform to execute multiple data collection jobs concurrently. |
|
https://www.servicenow.com/docs/en-US/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/configure-telecom-reconciliation.html | https://servicenow-be-prod.servicenow.com/api/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/configure-telecom-reconciliation.html | 2025-08-02 | daily | 0.5 | 268.xml | en-US | zurich-telecom-service-ops | product/tmt-telecom-service-operations-mgt/task/configure-telecom-reconciliation.html | zurich | Activate Telecom Discrepancy Identification and Reconciliation | Activate the Telecom Discrepancy Identification and Reconciliation feature (part of the Telecom Visibility plugin) to ensure consistency between telecom network resources discovered in the live network and the data represented in the CMDB or Telecom Network Inventory (TNI). This feature | [] | [
"Telecommunications Service Operations Management",
"Configuring Telecommunications Service Operations Management",
"Set up Telecom Visibility"
] | <article class="hascomments" data-page="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/configure-telecom-reconciliation.html" id="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/configure-telecom-reconciliation.html"><body id="configure-telecom-reconciliation"><main role="main"><article role="article" class="dita" id="configure-telecom-reconciliation" aria-labelledby="title_configure-telecom-reconciliation">
<h1 class="title topictitle1" id="title_configure-telecom-reconciliation">Activate Telecom Discrepancy Identification and Reconciliation</h1>
<div class="body taskbody"><p class="shortdesc">Activate the Telecom Discrepancy Identification and Reconciliation feature (part of the Telecom Visibility plugin) to ensure consistency between telecom network resources discovered in the live network and the data
represented in the CMDB or Telecom Network Inventory (TNI). This feature helps detect and remediate mismatches automatically, supporting service accuracy and data integrity across your telecom environment.</p>
<section class="section prereq" id="configure-telecom-reconciliation__task-prereq"><div class="tasklabel"><p class="sectiontitle tasklabel">Before you begin</p></div>
<p class="p">Role required: admin</p>
<p class="p">To use this feature, your organization must have an active subscription to TSOM. Telecom Discovery, Telecom Visibility, and this feature are licensed together.</p>
</section>
<section class="section context" id="configure-telecom-reconciliation__context_act_dxn_xfc"><div class="tasklabel"><p class="sectiontitle tasklabel">About this task</p></div>
<div class="p">Plugin dependencies - Ensure the following plugins are installed and activated:<div class="table-wrap"><table count-columns="3" class="table" id="configure-telecom-reconciliation__table_yk1_fxn_xfc"><caption></caption><colgroup><col/><col/><col/></colgroup><thead class="thead">
<tr class="row">
<th class="entry" id="configure-telecom-reconciliation__table_yk1_fxn_xfc__entry__1">Plugin</th>
<th class="entry" id="configure-telecom-reconciliation__table_yk1_fxn_xfc__entry__2">ID / App ID</th>
<th class="entry" id="configure-telecom-reconciliation__table_yk1_fxn_xfc__entry__3">Type</th>
</tr>
</thead><tbody class="tbody">
<tr class="row">
<td class="entry" headers="configure-telecom-reconciliation__table_yk1_fxn_xfc__entry__1">Telecom Service Operation Core</td>
<td class="entry" headers="configure-telecom-reconciliation__table_yk1_fxn_xfc__entry__2"><code class="ph codeph">sn_tsom_core</code></td>
<td class="entry" headers="configure-telecom-reconciliation__table_yk1_fxn_xfc__entry__3">Store</td>
</tr>
<tr class="row">
<td class="entry" headers="configure-telecom-reconciliation__table_yk1_fxn_xfc__entry__1">CMDB CI Class Models</td>
<td class="entry" headers="configure-telecom-reconciliation__table_yk1_fxn_xfc__entry__2"><code class="ph codeph">sn_cmdb_ci_class</code></td>
<td class="entry" headers="configure-telecom-reconciliation__table_yk1_fxn_xfc__entry__3">Store</td>
</tr>
<tr class="row">
<td class="entry" headers="configure-telecom-reconciliation__table_yk1_fxn_xfc__entry__1">Expanded Model and Asset Classes</td>
<td class="entry" headers="configure-telecom-reconciliation__table_yk1_fxn_xfc__entry__2"><code class="ph codeph">sn_ent</code></td>
<td class="entry" headers="configure-telecom-reconciliation__table_yk1_fxn_xfc__entry__3">Store</td>
</tr>
<tr class="row">
<td class="entry" headers="configure-telecom-reconciliation__table_yk1_fxn_xfc__entry__1">Visibility Content</td>
<td class="entry" headers="configure-telecom-reconciliation__table_yk1_fxn_xfc__entry__2"><code class="ph codeph">sn_pattern_design</code></td>
<td class="entry" headers="configure-telecom-reconciliation__table_yk1_fxn_xfc__entry__3">Store</td>
</tr>
<tr class="row">
<td class="entry" headers="configure-telecom-reconciliation__table_yk1_fxn_xfc__entry__1">Integration Commons for CMDB</td>
<td class="entry" headers="configure-telecom-reconciliation__table_yk1_fxn_xfc__entry__2"><code class="ph codeph">sn_cmdb_int_util</code></td>
<td class="entry" headers="configure-telecom-reconciliation__table_yk1_fxn_xfc__entry__3">Store</td>
</tr>
<tr class="row">
<td class="entry" headers="configure-telecom-reconciliation__table_yk1_fxn_xfc__entry__1">Discovery Core</td>
<td class="entry" headers="configure-telecom-reconciliation__table_yk1_fxn_xfc__entry__2"><code class="ph codeph">com.snc.discovery.core</code></td>
<td class="entry" headers="configure-telecom-reconciliation__table_yk1_fxn_xfc__entry__3">Family</td>
</tr>
<tr class="row">
<td class="entry" headers="configure-telecom-reconciliation__table_yk1_fxn_xfc__entry__1">ITOM Discovery License</td>
<td class="entry" headers="configure-telecom-reconciliation__table_yk1_fxn_xfc__entry__2"><code class="ph codeph">com.snc.itom.discovery.license</code></td>
<td class="entry" headers="configure-telecom-reconciliation__table_yk1_fxn_xfc__entry__3">Family</td>
</tr>
<tr class="row">
<td class="entry" headers="configure-telecom-reconciliation__table_yk1_fxn_xfc__entry__1">ITOM Licensing</td>
<td class="entry" headers="configure-telecom-reconciliation__table_yk1_fxn_xfc__entry__2"><code class="ph codeph">com.snc.itom.license</code></td>
<td class="entry" headers="configure-telecom-reconciliation__table_yk1_fxn_xfc__entry__3">Family</td>
</tr>
</tbody></table></div></div>
</section>
<section id="configure-telecom-reconciliation__steps_c2l_hyg_yfc"><div class="tasklabel"><p class="sectiontitle tasklabel">Procedure</p></div><ol class="ol steps" id="configure-telecom-reconciliation__steps_c2l_hyg_yfc"><li class="li step">
<span class="ph cmd">Ensure the sn_tsom_core plugin is automatically installed when you install Telecommunications Discovery Patterns or the Nokia Altiplano Service Graph Connector.</span>
</li><li class="li step">
<span class="ph cmd">Ensure the mentioned dependent plugins are activated.</span>
</li></ol></section>
</div>
<nav role="navigation"></nav><nav role="navigation" class="tasksNavigation"></nav><nav role="navigation" class="related-links"><div class="col-md-4"><dt>Related tasks</dt><dd><ul><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/task/run-audits.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/run-audits.html" class="link" title="The Telecom Discrepancy Audit validates the integrity of configuration items (CIs) and relationships across your telecom inventory using the CMDB Compliance framework.">Run Telecom Discrepancy audit</a></li><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/task/control-ci-attribute-updates-using-reconciliation-rules.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/control-ci-attribute-updates-using-reconciliation-rules.html" class="link" title="To prevent specific attributes of a Configuration Item (CI) from being overwritten by Discovery or other data sources, use Reconciliation Rules. These rules define which data source is trusted to update a particular attribute when multiple sources provide values.">Control CI attribute updates using Reconciliation rules</a></li></ul></dd></div><div class="col-md-4"><dt>Related concepts</dt><dd><ul><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/concept/discrepancy-identification-types-of-discrepancies.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/discrepancy-identification-types-of-discrepancies.html" class="link" title="The Telecom Discrepancy Identification and Reconciliation capability identifies and classifies mismatches between the network state (as discovered through TSOM Discovery or Service Graph Connectors) and the inventory data stored in the CMDB or TNI.">Discrepancy identification – types of discrepancies</a></li><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/concept/system-properties-affecting-telecom-discrepancy-identification-reconciliation.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/system-properties-affecting-telecom-discrepancy-identification-reconciliation.html" class="link" title="The system properties are part of the TSOM Visibility plugin (sn_tsom_core) and control the Telecom Discrepancy Identification & Reconciliation log (TSOM CMDB Audit). The TSOM Visibility plugin serves as an enabler for the TSOM Visibility applications, containing logic that is shared across the Telecom Discovery and Telecom Discrepancy Identification & Reconciliation solution.">System components installed with Telecom Discrepancy Identification & Reconciliation</a></li><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/concept/exploring-telecom-reconciliation.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/exploring-telecom-reconciliation.html" class="link" title="Use the Telecom Discrepancy Identification and Reconciliation capability to keep your CMDB or Telecommunications Network Inventory (TNI) in sync with your live telecom network. By continuously auditing and comparing discovered data with inventory records, this solution helps you detect, classify, and automatically remediate inconsistencies before they impact service quality, assurance, or fulfillment processes.">Telecom Discrepancy Identification and Reconciliation</a></li></ul></dd></div></nav>
</article></main></body></article> | {
"attachments": {
"all_attachments": null,
"topic_attachments": []
},
"available_languages": [
"enus"
],
"breadcrumbs": [
{
"title": "Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html"
},
{
"title": "Configuring Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/configuring-tsom.html"
},
{
"title": "Set up Telecom Visibility",
"topic_id": "product/tmt-telecom-service-operations-mgt/task/configuring-tsom-visibility.html"
}
],
"breadcrumbs_html": "<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops\">Zurich Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html\">Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/configuring-tsom.html\">Configuring Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/configuring-tsom-visibility.html\">Set up Telecom Visibility</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<span class=\"active\">Activate Telecom Discrepancy Identification and Reconciliation</span>",
"bundle_id": "zurich-telecom-service-ops",
"bundle_key": 2733,
"bundle_landing_page": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html",
"bundle_subtitle": null,
"bundle_title": "Zurich Telecommunications Service Operations Management",
"canonical_link": null,
"dates": {
"Added on": "2025-08-02T00:48:08.794016Z",
"Created on": "2024-12-06T00:00:00Z",
"Initial upload": "2025-07-30T22:24:33.519043Z",
"Updated on": "2025-07-31T00:00:00Z"
},
"dislike_url": "https://servicenow-be-prod.servicenow.com/dislike/55686967",
"dislikes": 0,
"es_archived_content": false,
"is_in_fav": false,
"is_liked": null,
"is_watched": false,
"keywords": [
" zurich zurich"
],
"labels": [
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "zurich",
"navtitle": "Zurich",
"outputclasses": [],
"subjectHeadId": "versions",
"subjectheadNavtitle": "Versions",
"visibility": "show-facet"
},
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "tsom",
"navtitle": "Telecommunications Service Operations Management",
"outputclasses": [],
"subjectHeadId": "products",
"subjectheadNavtitle": "Products",
"visibility": "show-facet"
}
],
"labels_text": "Versions > Zurich; Products > CRM and Industry Products > Telecommunications Media and Technology Assurance > Telecommunications Service Operations Management",
"like_url": "https://servicenow-be-prod.servicenow.com/like/55686967",
"likes": 0,
"metadata": {
"AI Search": null,
"AI Search Assist": null,
"Application Insights": null,
"Capabilities": null,
"Code Signing": null,
"Contextual Search": null,
"DC.contributor": null,
"DC.coverage": null,
"DC.creator": "ServiceNow",
"DC.date.created": "2024-12-06T11:58:49+05:30",
"DC.date.modified": "2025-07-31",
"DC.format": "HTML5",
"DC.identifier": "configure-telecom-reconciliation",
"DC.language": null,
"DC.relation": "../concept/discrepancy-identification-types-of-discrepancies.html",
"DC.rights.owner": "(C) Copyright 2025",
"DC.subject": null,
"DC.type": "task",
"Data Discovery": null,
"Data Policy": null,
"Data Privacy": null,
"Discovery": null,
"External Content for AI Search": null,
"Field Administration": null,
"Field Normalization": null,
"Key Management Framework": null,
"Localization Framework": null,
"Now Platform": null,
"PlatSec": null,
"Platform": null,
"Platform Administration": null,
"Platform Performance": null,
"Platform Privacy": null,
"Proactive Triggers": null,
"Process Optimization": null,
"RN doc editing record number": null,
"Search Administration": null,
"Secrets Management": null,
"ServiceNow AI Platform": null,
"State Model": null,
"Subscription Management": null,
"Task Communications Management": null,
"Timeline Visualizations": null,
"User Administration": null,
"User Experience Analytics": null,
"Zing": null,
"ai-now-assist": null,
"app-name": null,
"app_route": null,
"azureapimanagemen": null,
"change-completed": null,
"change-item": null,
"change-request-id": null,
"change-request-reference": null,
"com.glide.embedded_help.category": null,
"component": null,
"copyright": "(C) Copyright 2025",
"crossroads": null,
"data": null,
"description": "Activate the Telecom Discrepancy Identification and Reconciliation feature (part of the Telecom Visibility plugin) to ensure consistency between telecom network resources discovered in the live network and the data represented in the CMDB or Telecom Network Inventory (TNI). This feature",
"dominant_bundle": null,
"erp-canvas-video": null,
"fsm-mobile": null,
"fsm-route": null,
"fsm-sched-opt": null,
"fsm-wrk-order": null,
"genai-round-7": null,
"generator": "DITA-OT",
"glossPartOfSpeech": null,
"glossStatus": null,
"guided setup": null,
"guided tours": null,
"keywords": null,
"min-toc": null,
"mini": null,
"mini-to truec": null,
"mini-toc": null,
"mini_toc": null,
"minitoc": null,
"modification": null,
"now-assist-app-gen-video": null,
"order": null,
"page-type": null,
"page-type ": null,
"prodname": null,
"product": null,
"product_name": null,
"release": null,
"resourceID": null,
"roles": null,
"route_page": null,
"route_params_listId": null,
"route_params_table": null,
"route_params_type": null,
"route_type": null,
"setconfigurationproperties": null,
"topic": null,
"translation-type": "source",
"version": null,
"workflow": "Customer and Industry",
"workplace-srvc-delvry-ditamap": null
},
"page_id": "product/tmt-telecom-service-operations-mgt/task/configure-telecom-reconciliation.html",
"page_key": 55686967,
"preprocessed_PDF": "https://downloads.docs.servicenow.com/pdf/enus/servicenow-zurich-telecom-service-ops-enus.pdf",
"rating": null,
"read_time_data": {
"char_count": 1331,
"img_count": 0,
"read_time": 1,
"video_links": [
""
],
"word_count": 169
},
"related_links": [
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "The Telecom Discrepancy Identification and Reconciliation capability identifies and classifies mismatches between the network state (as discovered through TSOM Discovery or Service Graph Connectors) and the inventory data stored in the CMDB or TNI.",
"title": "Discrepancy identification – types of discrepancies",
"topic": "/product/tmt-telecom-service-operations-mgt/concept/discrepancy-identification-types-of-discrepancies.html",
"type": "concept",
"url": null
},
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "The system properties are part of the TSOM Visibility plugin (sn_tsom_core) and control the Telecom Discrepancy Identification & Reconciliation log (TSOM CMDB Audit). The TSOM Visibility plugin serves as an enabler for the TSOM Visibility applications, containing logic that is shared across the Telecom Discovery and Telecom Discrepancy Identification & Reconciliation solution.",
"title": "System components installed with Telecom Discrepancy Identification & Reconciliation",
"topic": "/product/tmt-telecom-service-operations-mgt/concept/system-properties-affecting-telecom-discrepancy-identification-reconciliation.html",
"type": "concept",
"url": null
},
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "Use the Telecom Discrepancy Identification and Reconciliation capability to keep your CMDB or Telecommunications Network Inventory (TNI) in sync with your live telecom network. By continuously auditing and comparing discovered data with inventory records, this solution helps you detect, classify, and automatically remediate inconsistencies before they impact service quality, assurance, or fulfillment processes.",
"title": "Telecom Discrepancy Identification and Reconciliation",
"topic": "/product/tmt-telecom-service-operations-mgt/concept/exploring-telecom-reconciliation.html",
"type": "concept",
"url": null
},
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "The Telecom Discrepancy Audit validates the integrity of configuration items (CIs) and relationships across your telecom inventory using the CMDB Compliance framework.",
"title": "Run Telecom Discrepancy audit",
"topic": "/product/tmt-telecom-service-operations-mgt/task/run-audits.html",
"type": "task",
"url": null
},
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "To prevent specific attributes of a Configuration Item (CI) from being overwritten by Discovery or other data sources, use Reconciliation Rules. These rules define which data source is trusted to update a particular attribute when multiple sources provide values.",
"title": "Control CI attribute updates using Reconciliation rules",
"topic": "/product/tmt-telecom-service-operations-mgt/task/control-ci-attribute-updates-using-reconciliation-rules.html",
"type": "task",
"url": null
}
],
"search_title": null,
"title": "Activate Telecom Discrepancy Identification and Reconciliation",
"topic_cluster": {
"clustered_by": {
"enabled": true,
"primary_key": "versions",
"primary_sort": "top-down",
"type": "subjecthead"
},
"clustered_labels": [
"versions"
],
"clustered_topics": [
{
"bundle_id": "yokohama-telecom-service-ops",
"clustering_title": "Yokohama",
"es_archived_content": false,
"page_id": "product/tmt-telecom-service-operations-mgt/task/configure-telecom-reconciliation.html"
}
],
"clustering_title": "Zurich"
},
"topic_html": "<article class=\"hascomments\" data-page=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/configure-telecom-reconciliation.html\" id=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/configure-telecom-reconciliation.html\"><body id=\"configure-telecom-reconciliation\"><main role=\"main\"><article role=\"article\" class=\"dita\" id=\"configure-telecom-reconciliation\" aria-labelledby=\"title_configure-telecom-reconciliation\">\n <h1 class=\"title topictitle1\" id=\"title_configure-telecom-reconciliation\">Activate Telecom Discrepancy Identification and Reconciliation</h1>\n \n \n <div class=\"body taskbody\"><p class=\"shortdesc\">Activate the Telecom Discrepancy Identification and Reconciliation feature (part of the Telecom Visibility plugin) to ensure consistency between telecom network resources discovered in the live network and the data\n represented in the CMDB or Telecom Network Inventory (TNI). This feature helps detect and remediate mismatches automatically, supporting service accuracy and data integrity across your telecom environment.</p>\n <section class=\"section prereq\" id=\"configure-telecom-reconciliation__task-prereq\"><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">Before you begin</p></div>\n <p class=\"p\">Role required: admin</p>\n <p class=\"p\">To use this feature, your organization must have an active subscription to TSOM. Telecom Discovery, Telecom Visibility, and this feature are licensed together.</p>\n </section>\n <section class=\"section context\" id=\"configure-telecom-reconciliation__context_act_dxn_xfc\"><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">About this task</p></div>\n <div class=\"p\">Plugin dependencies - Ensure the following plugins are installed and activated:<div class=\"table-wrap\"><table count-columns=\"3\" class=\"table\" id=\"configure-telecom-reconciliation__table_yk1_fxn_xfc\"><caption></caption><colgroup><col/><col/><col/></colgroup><thead class=\"thead\">\n <tr class=\"row\">\n <th class=\"entry\" id=\"configure-telecom-reconciliation__table_yk1_fxn_xfc__entry__1\">Plugin</th>\n <th class=\"entry\" id=\"configure-telecom-reconciliation__table_yk1_fxn_xfc__entry__2\">ID / App ID</th>\n <th class=\"entry\" id=\"configure-telecom-reconciliation__table_yk1_fxn_xfc__entry__3\">Type</th>\n </tr>\n </thead><tbody class=\"tbody\">\n <tr class=\"row\">\n <td class=\"entry\" headers=\"configure-telecom-reconciliation__table_yk1_fxn_xfc__entry__1\">Telecom Service Operation Core</td>\n <td class=\"entry\" headers=\"configure-telecom-reconciliation__table_yk1_fxn_xfc__entry__2\"><code class=\"ph codeph\">sn_tsom_core</code></td>\n <td class=\"entry\" headers=\"configure-telecom-reconciliation__table_yk1_fxn_xfc__entry__3\">Store</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry\" headers=\"configure-telecom-reconciliation__table_yk1_fxn_xfc__entry__1\">CMDB CI Class Models</td>\n <td class=\"entry\" headers=\"configure-telecom-reconciliation__table_yk1_fxn_xfc__entry__2\"><code class=\"ph codeph\">sn_cmdb_ci_class</code></td>\n <td class=\"entry\" headers=\"configure-telecom-reconciliation__table_yk1_fxn_xfc__entry__3\">Store</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry\" headers=\"configure-telecom-reconciliation__table_yk1_fxn_xfc__entry__1\">Expanded Model and Asset Classes</td>\n <td class=\"entry\" headers=\"configure-telecom-reconciliation__table_yk1_fxn_xfc__entry__2\"><code class=\"ph codeph\">sn_ent</code></td>\n <td class=\"entry\" headers=\"configure-telecom-reconciliation__table_yk1_fxn_xfc__entry__3\">Store</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry\" headers=\"configure-telecom-reconciliation__table_yk1_fxn_xfc__entry__1\">Visibility Content</td>\n <td class=\"entry\" headers=\"configure-telecom-reconciliation__table_yk1_fxn_xfc__entry__2\"><code class=\"ph codeph\">sn_pattern_design</code></td>\n <td class=\"entry\" headers=\"configure-telecom-reconciliation__table_yk1_fxn_xfc__entry__3\">Store</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry\" headers=\"configure-telecom-reconciliation__table_yk1_fxn_xfc__entry__1\">Integration Commons for CMDB</td>\n <td class=\"entry\" headers=\"configure-telecom-reconciliation__table_yk1_fxn_xfc__entry__2\"><code class=\"ph codeph\">sn_cmdb_int_util</code></td>\n <td class=\"entry\" headers=\"configure-telecom-reconciliation__table_yk1_fxn_xfc__entry__3\">Store</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry\" headers=\"configure-telecom-reconciliation__table_yk1_fxn_xfc__entry__1\">Discovery Core</td>\n <td class=\"entry\" headers=\"configure-telecom-reconciliation__table_yk1_fxn_xfc__entry__2\"><code class=\"ph codeph\">com.snc.discovery.core</code></td>\n <td class=\"entry\" headers=\"configure-telecom-reconciliation__table_yk1_fxn_xfc__entry__3\">Family</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry\" headers=\"configure-telecom-reconciliation__table_yk1_fxn_xfc__entry__1\">ITOM Discovery License</td>\n <td class=\"entry\" headers=\"configure-telecom-reconciliation__table_yk1_fxn_xfc__entry__2\"><code class=\"ph codeph\">com.snc.itom.discovery.license</code></td>\n <td class=\"entry\" headers=\"configure-telecom-reconciliation__table_yk1_fxn_xfc__entry__3\">Family</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry\" headers=\"configure-telecom-reconciliation__table_yk1_fxn_xfc__entry__1\">ITOM Licensing</td>\n <td class=\"entry\" headers=\"configure-telecom-reconciliation__table_yk1_fxn_xfc__entry__2\"><code class=\"ph codeph\">com.snc.itom.license</code></td>\n <td class=\"entry\" headers=\"configure-telecom-reconciliation__table_yk1_fxn_xfc__entry__3\">Family</td>\n </tr>\n </tbody></table></div></div>\n </section>\n <section id=\"configure-telecom-reconciliation__steps_c2l_hyg_yfc\"><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">Procedure</p></div><ol class=\"ol steps\" id=\"configure-telecom-reconciliation__steps_c2l_hyg_yfc\"><li class=\"li step\">\n <span class=\"ph cmd\">Ensure the sn_tsom_core plugin is automatically installed when you install Telecommunications Discovery Patterns or the Nokia Altiplano Service Graph Connector.</span>\n </li><li class=\"li step\">\n <span class=\"ph cmd\">Ensure the mentioned dependent plugins are activated.</span>\n </li></ol></section>\n </div>\n <nav role=\"navigation\"></nav><nav role=\"navigation\" class=\"tasksNavigation\"></nav><nav role=\"navigation\" class=\"related-links\"><div class=\"col-md-4\"><dt>Related tasks</dt><dd><ul><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/task/run-audits.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/run-audits.html\" class=\"link\" title=\"The Telecom Discrepancy Audit validates the integrity of configuration items (CIs) and relationships across your telecom inventory using the CMDB Compliance framework.\">Run Telecom Discrepancy audit</a></li><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/task/control-ci-attribute-updates-using-reconciliation-rules.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/control-ci-attribute-updates-using-reconciliation-rules.html\" class=\"link\" title=\"To prevent specific attributes of a Configuration Item (CI) from being overwritten by Discovery or other data sources, use Reconciliation Rules. These rules define which data source is trusted to update a particular attribute when multiple sources provide values.\">Control CI attribute updates using Reconciliation rules</a></li></ul></dd></div><div class=\"col-md-4\"><dt>Related concepts</dt><dd><ul><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept/discrepancy-identification-types-of-discrepancies.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/discrepancy-identification-types-of-discrepancies.html\" class=\"link\" title=\"The Telecom Discrepancy Identification and Reconciliation capability identifies and classifies mismatches between the network state (as discovered through TSOM Discovery or Service Graph Connectors) and the inventory data stored in the CMDB or TNI.\">Discrepancy identification – types of discrepancies</a></li><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept/system-properties-affecting-telecom-discrepancy-identification-reconciliation.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/system-properties-affecting-telecom-discrepancy-identification-reconciliation.html\" class=\"link\" title=\"The system properties are part of the TSOM Visibility plugin (sn_tsom_core) and control the Telecom Discrepancy Identification & Reconciliation log (TSOM CMDB Audit). The TSOM Visibility plugin serves as an enabler for the TSOM Visibility applications, containing logic that is shared across the Telecom Discovery and Telecom Discrepancy Identification & Reconciliation solution.\">System components installed with Telecom Discrepancy Identification & Reconciliation</a></li><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept/exploring-telecom-reconciliation.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/exploring-telecom-reconciliation.html\" class=\"link\" title=\"Use the Telecom Discrepancy Identification and Reconciliation capability to keep your CMDB or Telecommunications Network Inventory (TNI) in sync with your live telecom network. By continuously auditing and comparing discovered data with inventory records, this solution helps you detect, classify, and automatically remediate inconsistencies before they impact service quality, assurance, or fulfillment processes.\">Telecom Discrepancy Identification and Reconciliation</a></li></ul></dd></div></nav>\n</article></main></body></article>",
"topic_language": "enus",
"views": 0,
"your_rating": null
} | # Activate Telecom Discrepancy Identification and Reconciliation
Activate the Telecom Discrepancy Identification and Reconciliation feature (part of the Telecom Visibility plugin) to ensure consistency between telecom network resources discovered in the live network and the data
represented in the CMDB or Telecom Network Inventory (TNI). This feature helps detect and remediate mismatches automatically, supporting service accuracy and data integrity across your telecom environment.
## Before you begin
Role required: admin
To use this feature, your organization must have an active subscription to TSOM. Telecom Discovery, Telecom Visibility, and this feature are licensed together.
## About this task
Plugin dependencies - Ensure the following plugins are installed and activated:
| Plugin | ID / App ID | Type |
| --- | --- | --- |
| Telecom Service Operation Core | `sn_tsom_core` | Store |
| CMDB CI Class Models | `sn_cmdb_ci_class` | Store |
| Expanded Model and Asset Classes | `sn_ent` | Store |
| Visibility Content | `sn_pattern_design` | Store |
| Integration Commons for CMDB | `sn_cmdb_int_util` | Store |
| Discovery Core | `com.snc.discovery.core` | Family |
| ITOM Discovery License | `com.snc.itom.discovery.license` | Family |
| ITOM Licensing | `com.snc.itom.license` | Family |
## Procedure
1. Ensure the sn\_tsom\_core plugin is automatically installed when you install Telecommunications Discovery Patterns or the Nokia Altiplano Service Graph Connector.
2. Ensure the mentioned dependent plugins are activated.
| ---
title: Activate Telecom Discrepancy Identification and Reconciliation
description: Activate the Telecom Discrepancy Identification and Reconciliation feature
(part of the Telecom Visibility plugin) to ensure consistency between telecom network
resources discovered in the live network and the data represented in the CMDB or
Telecom Network Inventory (TNI). This feature
keywords: []
breadcrumbs:
- Telecommunications Service Operations Management
- Configuring Telecommunications Service Operations Management
- Set up Telecom Visibility
---
# Activate Telecom Discrepancy Identification and Reconciliation
Activate the Telecom Discrepancy Identification and Reconciliation feature (part of the Telecom Visibility plugin) to ensure consistency between telecom network resources discovered in the live network and the data
represented in the CMDB or Telecom Network Inventory (TNI). This feature helps detect and remediate mismatches automatically, supporting service accuracy and data integrity across your telecom environment.
## Before you begin
Role required: admin
To use this feature, your organization must have an active subscription to TSOM. Telecom Discovery, Telecom Visibility, and this feature are licensed together.
## About this task
Plugin dependencies - Ensure the following plugins are installed and activated:
| Plugin | ID / App ID | Type |
| --- | --- | --- |
| Telecom Service Operation Core | `sn_tsom_core` | Store |
| CMDB CI Class Models | `sn_cmdb_ci_class` | Store |
| Expanded Model and Asset Classes | `sn_ent` | Store |
| Visibility Content | `sn_pattern_design` | Store |
| Integration Commons for CMDB | `sn_cmdb_int_util` | Store |
| Discovery Core | `com.snc.discovery.core` | Family |
| ITOM Discovery License | `com.snc.itom.discovery.license` | Family |
| ITOM Licensing | `com.snc.itom.license` | Family |
## Procedure
1. Ensure the sn\_tsom\_core plugin is automatically installed when you install Telecommunications Discovery Patterns or the Nokia Altiplano Service Graph Connector.
2. Ensure the mentioned dependent plugins are activated.
|
https://www.servicenow.com/docs/en-US/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/configuring-tni-entiry-support-for-duplicated-etls.html | https://servicenow-be-prod.servicenow.com/api/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/configuring-tni-entiry-support-for-duplicated-etls.html | 2025-08-02 | daily | 0.5 | 268.xml | en-US | zurich-telecom-service-ops | product/tmt-telecom-service-operations-mgt/task/configuring-tni-entiry-support-for-duplicated-etls.html | zurich | Extend TNI entity support for duplicated ETLs | When Telecom Network Inventory (TNI) is enabled, every Configuration Item (CI) created by a duplicated ETL must have a corresponding TNI Entity. | [] | [
"Telecommunications Service Operations Management",
"Configuring Telecommunications Service Operations Management",
"Set up Telecom Visibility",
"Configuring the Telecom Discovery Builder framework ETL in a connector"
] | <article class="hascomments" data-page="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/configuring-tni-entiry-support-for-duplicated-etls.html" id="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/configuring-tni-entiry-support-for-duplicated-etls.html"><body id="configuring-tni-entiry-support-for-duplicated-etls"><main role="main"><article role="article" class="dita" id="configuring-tni-entiry-support-for-duplicated-etls" aria-labelledby="title_configuring-tni-entiry-support-for-duplicated-etls">
<h1 class="title topictitle1" id="title_configuring-tni-entiry-support-for-duplicated-etls">Extend TNI entity support for duplicated ETLs</h1>
<div class="body taskbody"><p class="shortdesc">When Telecom Network Inventory (TNI) is enabled, every Configuration Item (CI) created by a duplicated ETL must have a corresponding TNI Entity.</p>
<section class="section prereq" id="configuring-tni-entiry-support-for-duplicated-etls__task-prereq"><div class="tasklabel"><p class="sectiontitle tasklabel">Before you begin</p></div>
<p class="p">Role required: admin</p>
<div class="p">
<ul class="ul" id="configuring-tni-entiry-support-for-duplicated-etls__ul_edf_r1s_dfc">
<li class="li">Ensure TNI is installed and active in your instance.</li>
<li class="li">Complete the duplication of the Telecom Discovery Builder framework ETL into the target application scope.</li>
</ul>
</div>
</section>
<section><div class="tasklabel"><p class="sectiontitle tasklabel">Procedure</p></div><ol class="ol steps"><li class="li step stepexpand">
<span class="ph cmd">Navigate to <span class="ph menucascade"><span class="ph uicontrol">All</span><abbr> > </abbr><span class="ph uicontrol">IntegrationHub ETL</span></span>.</span>
</li><li class="li step stepexpand">
<span class="ph cmd">Select the CMDB Application associated with the duplicated ETL.</span>
<div class="itemgroup stepresult">The CMDB Integration Studio application in a new page</div>
</li><li class="li step stepexpand">
<span class="ph cmd">In the ETL configuration page, check the <span class="ph uicontrol">Execute Before Script</span> option.</span>
</li><li class="li step stepexpand">
<span class="ph cmd">Replace the default script with the following:</span>
<div class="itemgroup info">
<pre class="prettyprint language-plaintext"><code class="pre codeblock language-plaintext">(function(input, runId) {
new sn_tsom_core.TelcoGenericMappingHelper().checkAndUpdateIrePayloadForTni(input);
})(input, runId);</code></pre>
</div>
</li><li class="li step stepexpand">
<span class="ph cmd">Click <span class="ph uicontrol">Update</span> to save the changes.</span>
<div class="itemgroup stepresult">The duplicated ETL links TNI entities for discovered CIs.</div>
</li></ol></section>
</div>
</article></main></body></article> | {
"attachments": {
"all_attachments": null,
"topic_attachments": []
},
"available_languages": [
"enus"
],
"breadcrumbs": [
{
"title": "Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html"
},
{
"title": "Configuring Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/configuring-tsom.html"
},
{
"title": "Set up Telecom Visibility",
"topic_id": "product/tmt-telecom-service-operations-mgt/task/configuring-tsom-visibility.html"
},
{
"title": "Configuring the Telecom Discovery Builder framework ETL in a connector",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/configuring-the-telco-generic-schema-etl.html"
}
],
"breadcrumbs_html": "<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops\">Zurich Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html\">Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/configuring-tsom.html\">Configuring Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/configuring-tsom-visibility.html\">Set up Telecom Visibility</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/configuring-the-telco-generic-schema-etl.html\">Configuring the Telecom Discovery Builder framework ETL in a connector</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<span class=\"active\">Extend TNI entity support for duplicated ETLs</span>",
"bundle_id": "zurich-telecom-service-ops",
"bundle_key": 2733,
"bundle_landing_page": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html",
"bundle_subtitle": null,
"bundle_title": "Zurich Telecommunications Service Operations Management",
"canonical_link": null,
"dates": {
"Added on": "2025-08-02T00:48:08.794016Z",
"Created on": "2025-04-28T00:00:00Z",
"Initial upload": "2025-07-30T22:24:33.519043Z",
"Updated on": "2025-07-31T00:00:00Z"
},
"dislike_url": "https://servicenow-be-prod.servicenow.com/dislike/55686968",
"dislikes": 0,
"es_archived_content": false,
"is_in_fav": false,
"is_liked": null,
"is_watched": false,
"keywords": [
" zurich zurich"
],
"labels": [
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "zurich",
"navtitle": "Zurich",
"outputclasses": [],
"subjectHeadId": "versions",
"subjectheadNavtitle": "Versions",
"visibility": "show-facet"
},
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "tsom",
"navtitle": "Telecommunications Service Operations Management",
"outputclasses": [],
"subjectHeadId": "products",
"subjectheadNavtitle": "Products",
"visibility": "show-facet"
}
],
"labels_text": "Versions > Zurich; Products > CRM and Industry Products > Telecommunications Media and Technology Assurance > Telecommunications Service Operations Management",
"like_url": "https://servicenow-be-prod.servicenow.com/like/55686968",
"likes": 0,
"metadata": {
"AI Search": null,
"AI Search Assist": null,
"Application Insights": null,
"Capabilities": null,
"Code Signing": null,
"Contextual Search": null,
"DC.contributor": null,
"DC.coverage": null,
"DC.creator": "ServiceNow",
"DC.date.created": "2025-04-28T18:42:39+05:30",
"DC.date.modified": "2025-07-31",
"DC.format": "HTML5",
"DC.identifier": "configuring-tni-entiry-support-for-duplicated-etls",
"DC.language": null,
"DC.relation": null,
"DC.rights.owner": "(C) Copyright 2025",
"DC.subject": null,
"DC.type": "task",
"Data Discovery": null,
"Data Policy": null,
"Data Privacy": null,
"Discovery": null,
"External Content for AI Search": null,
"Field Administration": null,
"Field Normalization": null,
"Key Management Framework": null,
"Localization Framework": null,
"Now Platform": null,
"PlatSec": null,
"Platform": null,
"Platform Administration": null,
"Platform Performance": null,
"Platform Privacy": null,
"Proactive Triggers": null,
"Process Optimization": null,
"RN doc editing record number": null,
"Search Administration": null,
"Secrets Management": null,
"ServiceNow AI Platform": null,
"State Model": null,
"Subscription Management": null,
"Task Communications Management": null,
"Timeline Visualizations": null,
"User Administration": null,
"User Experience Analytics": null,
"Zing": null,
"ai-now-assist": null,
"app-name": null,
"app_route": null,
"azureapimanagemen": null,
"change-completed": null,
"change-item": null,
"change-request-id": null,
"change-request-reference": null,
"com.glide.embedded_help.category": null,
"component": null,
"copyright": "(C) Copyright 2025",
"crossroads": null,
"data": null,
"description": "When Telecom Network Inventory (TNI) is enabled, every Configuration Item (CI) created by a duplicated ETL must have a corresponding TNI Entity.",
"dominant_bundle": null,
"erp-canvas-video": null,
"fsm-mobile": null,
"fsm-route": null,
"fsm-sched-opt": null,
"fsm-wrk-order": null,
"genai-round-7": null,
"generator": "DITA-OT",
"glossPartOfSpeech": null,
"glossStatus": null,
"guided setup": null,
"guided tours": null,
"keywords": null,
"min-toc": null,
"mini": null,
"mini-to truec": null,
"mini-toc": null,
"mini_toc": null,
"minitoc": null,
"modification": null,
"now-assist-app-gen-video": null,
"order": null,
"page-type": null,
"page-type ": null,
"prodname": null,
"product": null,
"product_name": null,
"release": null,
"resourceID": null,
"roles": null,
"route_page": null,
"route_params_listId": null,
"route_params_table": null,
"route_params_type": null,
"route_type": null,
"setconfigurationproperties": null,
"topic": null,
"translation-type": "source",
"version": null,
"workflow": "Customer and Industry",
"workplace-srvc-delvry-ditamap": null
},
"page_id": "product/tmt-telecom-service-operations-mgt/task/configuring-tni-entiry-support-for-duplicated-etls.html",
"page_key": 55686968,
"preprocessed_PDF": "https://downloads.docs.servicenow.com/pdf/enus/servicenow-zurich-telecom-service-ops-enus.pdf",
"rating": null,
"read_time_data": {
"char_count": 851,
"img_count": 0,
"read_time": 1,
"video_links": [
""
],
"word_count": 118
},
"related_links": [],
"search_title": null,
"title": "Extend TNI entity support for duplicated ETLs",
"topic_cluster": {
"clustered_by": {
"enabled": true,
"primary_key": "versions",
"primary_sort": "top-down",
"type": "subjecthead"
},
"clustered_labels": [
"versions"
],
"clustered_topics": [],
"clustering_title": "Zurich"
},
"topic_html": "<article class=\"hascomments\" data-page=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/configuring-tni-entiry-support-for-duplicated-etls.html\" id=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/configuring-tni-entiry-support-for-duplicated-etls.html\"><body id=\"configuring-tni-entiry-support-for-duplicated-etls\"><main role=\"main\"><article role=\"article\" class=\"dita\" id=\"configuring-tni-entiry-support-for-duplicated-etls\" aria-labelledby=\"title_configuring-tni-entiry-support-for-duplicated-etls\">\n <h1 class=\"title topictitle1\" id=\"title_configuring-tni-entiry-support-for-duplicated-etls\">Extend TNI entity support for duplicated ETLs</h1>\n \n \n <div class=\"body taskbody\"><p class=\"shortdesc\">When Telecom Network Inventory (TNI) is enabled, every Configuration Item (CI) created by a duplicated ETL must have a corresponding TNI Entity.</p>\n <section class=\"section prereq\" id=\"configuring-tni-entiry-support-for-duplicated-etls__task-prereq\"><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">Before you begin</p></div>\n <p class=\"p\">Role required: admin</p>\n <div class=\"p\">\n <ul class=\"ul\" id=\"configuring-tni-entiry-support-for-duplicated-etls__ul_edf_r1s_dfc\">\n <li class=\"li\">Ensure TNI is installed and active in your instance.</li>\n <li class=\"li\">Complete the duplication of the Telecom Discovery Builder framework ETL into the target application scope.</li>\n </ul>\n </div>\n </section>\n <section><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">Procedure</p></div><ol class=\"ol steps\"><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">Navigate to <span class=\"ph menucascade\"><span class=\"ph uicontrol\">All</span><abbr> > </abbr><span class=\"ph uicontrol\">IntegrationHub ETL</span></span>.</span>\n </li><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">Select the CMDB Application associated with the duplicated ETL.</span>\n <div class=\"itemgroup stepresult\">The CMDB Integration Studio application in a new page</div>\n </li><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">In the ETL configuration page, check the <span class=\"ph uicontrol\">Execute Before Script</span> option.</span>\n </li><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">Replace the default script with the following:</span>\n <div class=\"itemgroup info\">\n <pre class=\"prettyprint language-plaintext\"><code class=\"pre codeblock language-plaintext\">(function(input, runId) {\n new sn_tsom_core.TelcoGenericMappingHelper().checkAndUpdateIrePayloadForTni(input);\n})(input, runId);</code></pre>\n </div>\n </li><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">Click <span class=\"ph uicontrol\">Update</span> to save the changes.</span>\n <div class=\"itemgroup stepresult\">The duplicated ETL links TNI entities for discovered CIs.</div>\n </li></ol></section>\n </div>\n</article></main></body></article>",
"topic_language": "enus",
"views": 0,
"your_rating": null
} | # Extend TNI entity support for duplicated ETLs
When Telecom Network Inventory (TNI) is enabled, every Configuration Item (CI) created by a duplicated ETL must have a corresponding TNI Entity.
## Before you begin
Role required: admin
* Ensure TNI is installed and active in your instance.
* Complete the duplication of the Telecom Discovery Builder framework ETL into the target application scope.
## Procedure
1. Navigate to All > IntegrationHub ETL.
2. Select the CMDB Application associated with the duplicated ETL.
The CMDB Integration Studio application in a new page
3. In the ETL configuration page, check the Execute Before Script option.
4. Replace the default script with the following:
```None
(function(input, runId) {
new sn_tsom_core.TelcoGenericMappingHelper().checkAndUpdateIrePayloadForTni(input);
})(input, runId);
```
5. Click Update to save the changes.
The duplicated ETL links TNI entities for discovered CIs.
| ---
title: Extend TNI entity support for duplicated ETLs
description: When Telecom Network Inventory (TNI) is enabled, every Configuration
Item (CI) created by a duplicated ETL must have a corresponding TNI Entity.
keywords: []
breadcrumbs:
- Telecommunications Service Operations Management
- Configuring Telecommunications Service Operations Management
- Set up Telecom Visibility
- Configuring the Telecom Discovery Builder framework ETL in a connector
---
# Extend TNI entity support for duplicated ETLs
When Telecom Network Inventory (TNI) is enabled, every Configuration Item (CI) created by a duplicated ETL must have a corresponding TNI Entity.
## Before you begin
Role required: admin
* Ensure TNI is installed and active in your instance.
* Complete the duplication of the Telecom Discovery Builder framework ETL into the target application scope.
## Procedure
1. Navigate to All > IntegrationHub ETL.
2. Select the CMDB Application associated with the duplicated ETL.
The CMDB Integration Studio application in a new page
3. In the ETL configuration page, check the Execute Before Script option.
4. Replace the default script with the following:
```None
(function(input, runId) {
new sn_tsom_core.TelcoGenericMappingHelper().checkAndUpdateIrePayloadForTni(input);
})(input, runId);
```
5. Click Update to save the changes.
The duplicated ETL links TNI entities for discovered CIs.
|
https://www.servicenow.com/docs/en-US/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/configuring-tsom-visibility.html | https://servicenow-be-prod.servicenow.com/api/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/configuring-tsom-visibility.html | 2025-08-02 | daily | 0.5 | 268.xml | en-US | zurich-telecom-service-ops | product/tmt-telecom-service-operations-mgt/task/configuring-tsom-visibility.html | zurich | Set up Telecom Visibility | Telecom Visibility provides foundational capabilities that support both Telecom Discovery and Telecom Discrepancy Identification & Reconciliation. It includes shared logic, enhanced CI class models, and Identification and Reconciliation Engine (IRE) updates tailored for telecom network elements. | [] | [
"Telecommunications Service Operations Management",
"Configuring Telecommunications Service Operations Management"
] | <article class="hascomments" data-page="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/configuring-tsom-visibility.html" id="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/configuring-tsom-visibility.html"><body id="configuring-tsom-visibility"><main role="main"><article role="article" class="dita" id="configuring-tsom-visibility" aria-labelledby="title_configuring-tsom-visibility">
<h1 class="title topictitle1" id="title_configuring-tsom-visibility">Set up Telecom Visibility</h1>
<div class="body taskbody"><p class="shortdesc">Telecom Visibility provides foundational capabilities that support both Telecom Discovery and Telecom Discrepancy Identification & Reconciliation. It includes shared logic, enhanced CI class models, and Identification and
Reconciliation Engine (IRE) updates tailored for telecom network elements.</p>
<section class="section prereq" id="configuring-tsom-visibility__task-prereq"><div class="tasklabel"><p class="sectiontitle tasklabel">Before you begin</p></div>
<p class="p">Role required: admin</p>
<p class="p">Confirm that:</p>
<ul class="ul" id="configuring-tsom-visibility__ul_okh_brh_vfc">
<li class="li">Your ServiceNow instance is licensed for TSOM.</li>
<li class="li">Your MID Server is operational and validated for discovery.</li>
<li class="li">You review any custom IRE rules applied to telecom CIs to help prevent overrides during upgrade.</li>
</ul>
</section>
<section class="section context" id="configuring-tsom-visibility__context_pb3_drh_vfc"><div class="tasklabel"><p class="sectiontitle tasklabel">About this task</p></div>
<div class="p">To configure Telecom Visibility, you must install the required plugins and update the CMDB CI Class Models to version 1.69.0, which introduces telecom-specific IRE identification rules. This confirms accurate CI
identification and reconciliation across telecom domains. <div class="note note note_note"><span class="note__title">Note:</span> If you have customized IRE identification rules for any of the affected telecom CIs, upgrading to version 1.69.0 may override or impact those rules.</div></div>
<div class="p">The following capabilities are included with the Telecom Visibility subscription:<div class="table-wrap"><table count-columns="3" class="table" id="configuring-tsom-visibility__table_kwq_drh_vfc"><caption></caption><colgroup><col/><col/><col/></colgroup><thead class="thead">
<tr class="row">
<th class="entry" id="configuring-tsom-visibility__table_kwq_drh_vfc__entry__1">Plugin Name</th>
<th class="entry" id="configuring-tsom-visibility__table_kwq_drh_vfc__entry__2">Description</th>
<th class="entry" id="configuring-tsom-visibility__table_kwq_drh_vfc__entry__3">Store App</th>
</tr>
</thead><tbody class="tbody">
<tr class="row">
<td class="entry" headers="configuring-tsom-visibility__table_kwq_drh_vfc__entry__1">Service Graph Connectors <code class="ph codeph">sn_sgc_altiplano_connector</code></td>
<td class="entry" headers="configuring-tsom-visibility__table_kwq_drh_vfc__entry__2">Service Graph Connector for Nokia Altiplano</td>
<td class="entry" headers="configuring-tsom-visibility__table_kwq_drh_vfc__entry__3">Yes</td>
</tr>
<tr class="row">
<td class="entry" headers="configuring-tsom-visibility__table_kwq_drh_vfc__entry__1">Telecommunications Discovery Patterns<code class="ph codeph">sn_tsom_patterns</code></td>
<td class="entry" headers="configuring-tsom-visibility__table_kwq_drh_vfc__entry__2">Telecommunication Discovery Patterns</td>
<td class="entry" headers="configuring-tsom-visibility__table_kwq_drh_vfc__entry__3">Yes</td>
</tr>
<tr class="row">
<td class="entry" headers="configuring-tsom-visibility__table_kwq_drh_vfc__entry__1">Telecom Visibility Plugin (Core logic)<code class="ph codeph">sn_tsom_core</code></td>
<td class="entry" headers="configuring-tsom-visibility__table_kwq_drh_vfc__entry__2">Core logic for Telecom Visibility and Discrepancy Reconciliation</td>
<td class="entry" headers="configuring-tsom-visibility__table_kwq_drh_vfc__entry__3">No</td>
</tr>
</tbody></table></div></div>
<div class="p">
<div class="note note note_note"><span class="note__title">Note:</span> These plugins automatically trigger the installation or update of the CMDB CI Class Models application to version 1.69.0.</div>
</div>
</section>
<section><div class="tasklabel"><p class="sectiontitle tasklabel">Procedure</p></div><ol class="ol steps"><li class="li step stepexpand">
<span class="ph cmd">Navigate to <span class="ph menucascade"><span class="ph uicontrol">All</span><abbr> > </abbr><span class="ph uicontrol">Plugins</span></span>.</span>
</li><li class="li step stepexpand">
<span class="ph cmd">Search for and install the following:</span>
<ol type="a" class="ol substeps">
<li class="li substep">
<span class="ph cmd">Service Graph Connector for Nokia Altiplano ( sn_sgc_altiplano_connector)</span>
</li>
<li class="li substep">
<span class="ph cmd">Telecommunication Discovery Patterns ( sn_tsom_patterns)</span>
</li>
<li class="li substep">
<span class="ph cmd">Telecom Visibility (plugin) ( sn_tsom_core)</span>
</li>
</ol>
</li><li class="li step stepexpand">(Optional)
<span class="ph cmd">Update the CMDB CI Class Models.</span>
<ol type="a" class="ol substeps" id="configuring-tsom-visibility__substeps_qmw_lth_vfc">
<li class="li substep">
<span class="ph cmd">Navigate to <span class="ph menucascade"><span class="ph uicontrol">All</span><abbr> > </abbr><span class="ph uicontrol">Available Applications</span></span> list in the ServiceNow Store.</span>
</li>
<li class="li substep">
<span class="ph cmd">Search for CMDB CI Class Models (sn_cmdb_ci_class).</span>
</li>
<li class="li substep">
<span class="ph cmd">Install or upgrade to version 1.69.0.</span>
</li>
</ol>
<div class="itemgroup info">
<div class="note note note_note"><span class="note__title">Note:</span> Installing any of the TSOM plugins listed above will automatically update or install version 1.69.0 of the CMDB CI Class Models app. If your instance doesn’t include TSOM plugins or you're on a pre-Yokohama release
(for example, Washington DC or Xanadu), you can manually install or upgrade the store app.</div>
</div>
</li><li class="li step stepexpand">
<span class="ph cmd">Navigate to <span class="ph menucascade"><span class="ph uicontrol">CMDB</span><abbr> > </abbr><span class="ph uicontrol">Identification Rules</span></span>.</span>
<ol type="a" class="ol substeps" id="configuring-tsom-visibility__substeps_gky_yxh_vfc">
<li class="li substep substepexpand">
<span class="ph cmd">Review rules related to:</span>
<div class="itemgroup info">
<ul class="ul" id="configuring-tsom-visibility__ul_wxz_jwh_vfc">
<li class="li"><code class="ph codeph">cmdb_ci_interface_card</code></li>
<li class="li"><code class="ph codeph">cmdb_ci_slot</code></li>
<li class="li"><code class="ph codeph">cmdb_ci_subslot</code></li>
<li class="li"><code class="ph codeph">cmdb_ci_network_adapter</code></li>
</ul>
</div>
</li>
<li class="li substep substepexpand">
<span class="ph cmd">Validate that your custom logic remains functional.</span>
</li>
<li class="li substep substepexpand">
<span class="ph cmd">Update or merge custom rules as needed.</span>
</li>
</ol>
</li></ol></section>
<section class="section result" id="configuring-tsom-visibility__result_wnc_vwh_vfc"><div class="tasklabel"><p class="sectiontitle tasklabel">Result</p></div>
<p class="p">Confirm that the following are listed as active:</p>
<ul class="ul" id="configuring-tsom-visibility__ul_xph_vwh_vfc">
<li class="li">Telecom Visibility (sn_tsom_core)</li>
<li class="li">Telecommunication Discovery Patterns (sn_tsom_patterns)</li>
<li class="li">Service Graph Connector for Nokia Altiplano (sn_sgc_altiplano_connector)</li>
<li class="li">CMDB CI Class Models version 1.69.0</li>
</ul>
</section>
</div>
<nav role="navigation"></nav><nav role="navigation" class="tasksNavigation"></nav><nav role="navigation" class="related-links"><div class="col-md-4"><dt>Related concepts</dt><dd><ul><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/concept/tsom-visibility.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/tsom-visibility.html" class="link" title="Telecom Visibility extends the discovery and reconciliation capabilities of ITOM Visibility to meet the specific needs of telecom service providers. It enables accurate, telecom-aware network inventory by discovering real-time network data, reconciling mismatches, and maintaining a consistent telecom model in your CMDB and TNI (Telecommunications Network Inventory).">Telecom Visibility</a></li></ul></dd></div></nav>
</article></main></body></article> | {
"attachments": {
"all_attachments": null,
"topic_attachments": []
},
"available_languages": [
"enus"
],
"breadcrumbs": [
{
"title": "Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html"
},
{
"title": "Configuring Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/configuring-tsom.html"
}
],
"breadcrumbs_html": "<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops\">Zurich Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html\">Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/configuring-tsom.html\">Configuring Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<span class=\"active\">Set up Telecom Visibility</span>",
"bundle_id": "zurich-telecom-service-ops",
"bundle_key": 2733,
"bundle_landing_page": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html",
"bundle_subtitle": null,
"bundle_title": "Zurich Telecommunications Service Operations Management",
"canonical_link": null,
"dates": {
"Added on": "2025-08-02T00:48:08.794016Z",
"Created on": "2025-06-30T00:00:00Z",
"Initial upload": "2025-07-30T22:24:33.519043Z",
"Updated on": "2025-07-31T00:00:00Z"
},
"dislike_url": "https://servicenow-be-prod.servicenow.com/dislike/55686969",
"dislikes": 0,
"es_archived_content": false,
"is_in_fav": false,
"is_liked": null,
"is_watched": false,
"keywords": [
" zurich zurich"
],
"labels": [
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "zurich",
"navtitle": "Zurich",
"outputclasses": [],
"subjectHeadId": "versions",
"subjectheadNavtitle": "Versions",
"visibility": "show-facet"
},
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "tsom",
"navtitle": "Telecommunications Service Operations Management",
"outputclasses": [],
"subjectHeadId": "products",
"subjectheadNavtitle": "Products",
"visibility": "show-facet"
}
],
"labels_text": "Versions > Zurich; Products > CRM and Industry Products > Telecommunications Media and Technology Assurance > Telecommunications Service Operations Management",
"like_url": "https://servicenow-be-prod.servicenow.com/like/55686969",
"likes": 0,
"metadata": {
"AI Search": null,
"AI Search Assist": null,
"Application Insights": null,
"Capabilities": null,
"Code Signing": null,
"Contextual Search": null,
"DC.contributor": null,
"DC.coverage": null,
"DC.creator": "ServiceNow",
"DC.date.created": "2025-06-30T17:04:50+05:30",
"DC.date.modified": "2025-07-31",
"DC.format": "HTML5",
"DC.identifier": "configuring-tsom-visibility",
"DC.language": null,
"DC.relation": "../concept/tsom-visibility.html",
"DC.rights.owner": "(C) Copyright 2025",
"DC.subject": null,
"DC.type": "task",
"Data Discovery": null,
"Data Policy": null,
"Data Privacy": null,
"Discovery": null,
"External Content for AI Search": null,
"Field Administration": null,
"Field Normalization": null,
"Key Management Framework": null,
"Localization Framework": null,
"Now Platform": null,
"PlatSec": null,
"Platform": null,
"Platform Administration": null,
"Platform Performance": null,
"Platform Privacy": null,
"Proactive Triggers": null,
"Process Optimization": null,
"RN doc editing record number": null,
"Search Administration": null,
"Secrets Management": null,
"ServiceNow AI Platform": null,
"State Model": null,
"Subscription Management": null,
"Task Communications Management": null,
"Timeline Visualizations": null,
"User Administration": null,
"User Experience Analytics": null,
"Zing": null,
"ai-now-assist": null,
"app-name": null,
"app_route": null,
"azureapimanagemen": null,
"change-completed": null,
"change-item": null,
"change-request-id": null,
"change-request-reference": null,
"com.glide.embedded_help.category": null,
"component": null,
"copyright": "(C) Copyright 2025",
"crossroads": null,
"data": null,
"description": "Telecom Visibility provides foundational capabilities that support both Telecom Discovery and Telecom Discrepancy Identification & Reconciliation. It includes shared logic, enhanced CI class models, and Identification and Reconciliation Engine (IRE) updates tailored for telecom network elements.",
"dominant_bundle": null,
"erp-canvas-video": null,
"fsm-mobile": null,
"fsm-route": null,
"fsm-sched-opt": null,
"fsm-wrk-order": null,
"genai-round-7": null,
"generator": "DITA-OT",
"glossPartOfSpeech": null,
"glossStatus": null,
"guided setup": null,
"guided tours": null,
"keywords": null,
"min-toc": null,
"mini": null,
"mini-to truec": null,
"mini-toc": null,
"mini_toc": null,
"minitoc": null,
"modification": null,
"now-assist-app-gen-video": null,
"order": null,
"page-type": null,
"page-type ": null,
"prodname": null,
"product": null,
"product_name": null,
"release": null,
"resourceID": null,
"roles": null,
"route_page": null,
"route_params_listId": null,
"route_params_table": null,
"route_params_type": null,
"route_type": null,
"setconfigurationproperties": null,
"topic": null,
"translation-type": "source",
"version": null,
"workflow": "Customer and Industry",
"workplace-srvc-delvry-ditamap": null
},
"page_id": "product/tmt-telecom-service-operations-mgt/task/configuring-tsom-visibility.html",
"page_key": 55686969,
"preprocessed_PDF": "https://downloads.docs.servicenow.com/pdf/enus/servicenow-zurich-telecom-service-ops-enus.pdf",
"rating": null,
"read_time_data": {
"char_count": 2825,
"img_count": 0,
"read_time": 2,
"video_links": [
""
],
"word_count": 374
},
"related_links": [
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "Telecom Visibility extends the discovery and reconciliation capabilities of ITOM Visibility to meet the specific needs of telecom service providers. It enables accurate, telecom-aware network inventory by discovering real-time network data, reconciling mismatches, and maintaining a consistent telecom model in your CMDB and TNI (Telecommunications Network Inventory).",
"title": "Telecom Visibility",
"topic": "/product/tmt-telecom-service-operations-mgt/concept/tsom-visibility.html",
"type": "concept",
"url": null
}
],
"search_title": null,
"title": "Set up Telecom Visibility",
"topic_cluster": {
"clustered_by": {
"enabled": true,
"primary_key": "versions",
"primary_sort": "top-down",
"type": "subjecthead"
},
"clustered_labels": [
"versions"
],
"clustered_topics": [],
"clustering_title": "Zurich"
},
"topic_html": "<article class=\"hascomments\" data-page=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/configuring-tsom-visibility.html\" id=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/configuring-tsom-visibility.html\"><body id=\"configuring-tsom-visibility\"><main role=\"main\"><article role=\"article\" class=\"dita\" id=\"configuring-tsom-visibility\" aria-labelledby=\"title_configuring-tsom-visibility\">\n <h1 class=\"title topictitle1\" id=\"title_configuring-tsom-visibility\">Set up Telecom Visibility</h1>\n \n \n <div class=\"body taskbody\"><p class=\"shortdesc\">Telecom Visibility provides foundational capabilities that support both Telecom Discovery and Telecom Discrepancy Identification & Reconciliation. It includes shared logic, enhanced CI class models, and Identification and\n Reconciliation Engine (IRE) updates tailored for telecom network elements.</p>\n <section class=\"section prereq\" id=\"configuring-tsom-visibility__task-prereq\"><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">Before you begin</p></div>\n <p class=\"p\">Role required: admin</p>\n <p class=\"p\">Confirm that:</p>\n <ul class=\"ul\" id=\"configuring-tsom-visibility__ul_okh_brh_vfc\">\n <li class=\"li\">Your ServiceNow instance is licensed for TSOM.</li>\n <li class=\"li\">Your MID Server is operational and validated for discovery.</li>\n <li class=\"li\">You review any custom IRE rules applied to telecom CIs to help prevent overrides during upgrade.</li>\n </ul>\n </section>\n <section class=\"section context\" id=\"configuring-tsom-visibility__context_pb3_drh_vfc\"><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">About this task</p></div>\n <div class=\"p\">To configure Telecom Visibility, you must install the required plugins and update the CMDB CI Class Models to version 1.69.0, which introduces telecom-specific IRE identification rules. This confirms accurate CI\n identification and reconciliation across telecom domains. <div class=\"note note note_note\"><span class=\"note__title\">Note:</span> If you have customized IRE identification rules for any of the affected telecom CIs, upgrading to version 1.69.0 may override or impact those rules.</div></div>\n <div class=\"p\">The following capabilities are included with the Telecom Visibility subscription:<div class=\"table-wrap\"><table count-columns=\"3\" class=\"table\" id=\"configuring-tsom-visibility__table_kwq_drh_vfc\"><caption></caption><colgroup><col/><col/><col/></colgroup><thead class=\"thead\">\n <tr class=\"row\">\n <th class=\"entry\" id=\"configuring-tsom-visibility__table_kwq_drh_vfc__entry__1\">Plugin Name</th>\n <th class=\"entry\" id=\"configuring-tsom-visibility__table_kwq_drh_vfc__entry__2\">Description</th>\n <th class=\"entry\" id=\"configuring-tsom-visibility__table_kwq_drh_vfc__entry__3\">Store App</th>\n </tr>\n </thead><tbody class=\"tbody\">\n <tr class=\"row\">\n <td class=\"entry\" headers=\"configuring-tsom-visibility__table_kwq_drh_vfc__entry__1\">Service Graph Connectors <code class=\"ph codeph\">sn_sgc_altiplano_connector</code></td>\n <td class=\"entry\" headers=\"configuring-tsom-visibility__table_kwq_drh_vfc__entry__2\">Service Graph Connector for Nokia Altiplano</td>\n <td class=\"entry\" headers=\"configuring-tsom-visibility__table_kwq_drh_vfc__entry__3\">Yes</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry\" headers=\"configuring-tsom-visibility__table_kwq_drh_vfc__entry__1\">Telecommunications Discovery Patterns<code class=\"ph codeph\">sn_tsom_patterns</code></td>\n <td class=\"entry\" headers=\"configuring-tsom-visibility__table_kwq_drh_vfc__entry__2\">Telecommunication Discovery Patterns</td>\n <td class=\"entry\" headers=\"configuring-tsom-visibility__table_kwq_drh_vfc__entry__3\">Yes</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry\" headers=\"configuring-tsom-visibility__table_kwq_drh_vfc__entry__1\">Telecom Visibility Plugin (Core logic)<code class=\"ph codeph\">sn_tsom_core</code></td>\n <td class=\"entry\" headers=\"configuring-tsom-visibility__table_kwq_drh_vfc__entry__2\">Core logic for Telecom Visibility and Discrepancy Reconciliation</td>\n <td class=\"entry\" headers=\"configuring-tsom-visibility__table_kwq_drh_vfc__entry__3\">No</td>\n </tr>\n </tbody></table></div></div>\n <div class=\"p\">\n <div class=\"note note note_note\"><span class=\"note__title\">Note:</span> These plugins automatically trigger the installation or update of the CMDB CI Class Models application to version 1.69.0.</div>\n </div>\n </section>\n <section><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">Procedure</p></div><ol class=\"ol steps\"><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">Navigate to <span class=\"ph menucascade\"><span class=\"ph uicontrol\">All</span><abbr> > </abbr><span class=\"ph uicontrol\">Plugins</span></span>.</span>\n </li><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">Search for and install the following:</span>\n <ol type=\"a\" class=\"ol substeps\">\n <li class=\"li substep\">\n <span class=\"ph cmd\">Service Graph Connector for Nokia Altiplano ( sn_sgc_altiplano_connector)</span>\n </li>\n <li class=\"li substep\">\n <span class=\"ph cmd\">Telecommunication Discovery Patterns ( sn_tsom_patterns)</span>\n </li>\n <li class=\"li substep\">\n <span class=\"ph cmd\">Telecom Visibility (plugin) ( sn_tsom_core)</span>\n </li>\n </ol>\n </li><li class=\"li step stepexpand\">(Optional) \n <span class=\"ph cmd\">Update the CMDB CI Class Models.</span>\n <ol type=\"a\" class=\"ol substeps\" id=\"configuring-tsom-visibility__substeps_qmw_lth_vfc\">\n <li class=\"li substep\">\n <span class=\"ph cmd\">Navigate to <span class=\"ph menucascade\"><span class=\"ph uicontrol\">All</span><abbr> > </abbr><span class=\"ph uicontrol\">Available Applications</span></span> list in the ServiceNow Store.</span>\n </li>\n <li class=\"li substep\">\n <span class=\"ph cmd\">Search for CMDB CI Class Models (sn_cmdb_ci_class).</span>\n </li>\n <li class=\"li substep\">\n <span class=\"ph cmd\">Install or upgrade to version 1.69.0.</span>\n </li>\n </ol>\n <div class=\"itemgroup info\">\n <div class=\"note note note_note\"><span class=\"note__title\">Note:</span> Installing any of the TSOM plugins listed above will automatically update or install version 1.69.0 of the CMDB CI Class Models app. If your instance doesn’t include TSOM plugins or you're on a pre-Yokohama release\n (for example, Washington DC or Xanadu), you can manually install or upgrade the store app.</div>\n </div>\n </li><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">Navigate to <span class=\"ph menucascade\"><span class=\"ph uicontrol\">CMDB</span><abbr> > </abbr><span class=\"ph uicontrol\">Identification Rules</span></span>.</span>\n <ol type=\"a\" class=\"ol substeps\" id=\"configuring-tsom-visibility__substeps_gky_yxh_vfc\">\n <li class=\"li substep substepexpand\">\n <span class=\"ph cmd\">Review rules related to:</span>\n <div class=\"itemgroup info\">\n <ul class=\"ul\" id=\"configuring-tsom-visibility__ul_wxz_jwh_vfc\">\n <li class=\"li\"><code class=\"ph codeph\">cmdb_ci_interface_card</code></li>\n <li class=\"li\"><code class=\"ph codeph\">cmdb_ci_slot</code></li>\n <li class=\"li\"><code class=\"ph codeph\">cmdb_ci_subslot</code></li>\n <li class=\"li\"><code class=\"ph codeph\">cmdb_ci_network_adapter</code></li>\n </ul>\n </div>\n </li>\n <li class=\"li substep substepexpand\">\n <span class=\"ph cmd\">Validate that your custom logic remains functional.</span>\n </li>\n <li class=\"li substep substepexpand\">\n <span class=\"ph cmd\">Update or merge custom rules as needed.</span>\n </li>\n </ol>\n </li></ol></section>\n <section class=\"section result\" id=\"configuring-tsom-visibility__result_wnc_vwh_vfc\"><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">Result</p></div>\n <p class=\"p\">Confirm that the following are listed as active:</p>\n <ul class=\"ul\" id=\"configuring-tsom-visibility__ul_xph_vwh_vfc\">\n <li class=\"li\">Telecom Visibility (sn_tsom_core)</li>\n <li class=\"li\">Telecommunication Discovery Patterns (sn_tsom_patterns)</li>\n <li class=\"li\">Service Graph Connector for Nokia Altiplano (sn_sgc_altiplano_connector)</li>\n <li class=\"li\">CMDB CI Class Models version 1.69.0</li>\n </ul>\n </section>\n </div>\n <nav role=\"navigation\"></nav><nav role=\"navigation\" class=\"tasksNavigation\"></nav><nav role=\"navigation\" class=\"related-links\"><div class=\"col-md-4\"><dt>Related concepts</dt><dd><ul><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept/tsom-visibility.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/tsom-visibility.html\" class=\"link\" title=\"Telecom Visibility extends the discovery and reconciliation capabilities of ITOM Visibility to meet the specific needs of telecom service providers. It enables accurate, telecom-aware network inventory by discovering real-time network data, reconciling mismatches, and maintaining a consistent telecom model in your CMDB and TNI (Telecommunications Network Inventory).\">Telecom Visibility</a></li></ul></dd></div></nav>\n</article></main></body></article>",
"topic_language": "enus",
"views": 0,
"your_rating": null
} | # Set up Telecom Visibility
Telecom Visibility provides foundational capabilities that support both Telecom Discovery and Telecom Discrepancy Identification & Reconciliation. It includes shared logic, enhanced CI class models, and Identification and
Reconciliation Engine (IRE) updates tailored for telecom network elements.
## Before you begin
Role required: admin
Confirm that:
* Your ServiceNow instance is licensed for TSOM.
* Your MID Server is operational and validated for discovery.
* You review any custom IRE rules applied to telecom CIs to help prevent overrides during upgrade.
## About this task
To configure Telecom Visibility, you must install the required plugins and update the CMDB CI Class Models to version 1.69.0, which introduces telecom-specific IRE identification rules. This confirms accurate CI
identification and reconciliation across telecom domains. Note: If you have customized IRE identification rules for any of the affected telecom CIs, upgrading to version 1.69.0 may override or impact those rules.
The following capabilities are included with the Telecom Visibility subscription:
| Plugin Name | Description | Store App |
| --- | --- | --- |
| Service Graph Connectors `sn_sgc_altiplano_connector` | Service Graph Connector for Nokia Altiplano | Yes |
| Telecommunications Discovery Patterns`sn_tsom_patterns` | Telecommunication Discovery Patterns | Yes |
| Telecom Visibility Plugin (Core logic)`sn_tsom_core` | Core logic for Telecom Visibility and Discrepancy Reconciliation | No |
Note: These plugins automatically trigger the installation or update of the CMDB CI Class Models application to version 1.69.0.
## Procedure
1. Navigate to All > Plugins.
2. Search for and install the following:
1. Service Graph Connector for Nokia Altiplano ( sn\_sgc\_altiplano\_connector)
2. Telecommunication Discovery Patterns ( sn\_tsom\_patterns)
3. Telecom Visibility (plugin) ( sn\_tsom\_core)
3. (Optional)
Update the CMDB CI Class Models.
1. Navigate to All > Available Applications list in the ServiceNow Store.
2. Search for CMDB CI Class Models (sn\_cmdb\_ci\_class).
3. Install or upgrade to version 1.69.0.
Note: Installing any of the TSOM plugins listed above will automatically update or install version 1.69.0 of the CMDB CI Class Models app. If your instance doesn’t include TSOM plugins or you're on a pre-Yokohama release
(for example, Washington DC or Xanadu), you can manually install or upgrade the store app.
4. Navigate to CMDB > Identification Rules.
1. Review rules related to:
* `cmdb_ci_interface_card`
* `cmdb_ci_slot`
* `cmdb_ci_subslot`
* `cmdb_ci_network_adapter`
2. Validate that your custom logic remains functional.
3. Update or merge custom rules as needed.
### Result
Confirm that the following are listed as active:
* Telecom Visibility (sn\_tsom\_core)
* Telecommunication Discovery Patterns (sn\_tsom\_patterns)
* Service Graph Connector for Nokia Altiplano (sn\_sgc\_altiplano\_connector)
* CMDB CI Class Models version 1.69.0
| ---
title: Set up Telecom Visibility
description: Telecom Visibility provides foundational capabilities that support both
Telecom Discovery and Telecom Discrepancy Identification & Reconciliation. It includes
shared logic, enhanced CI class models, and Identification and Reconciliation Engine
(IRE) updates tailored for telecom network elements.
keywords: []
breadcrumbs:
- Telecommunications Service Operations Management
- Configuring Telecommunications Service Operations Management
---
# Set up Telecom Visibility
Telecom Visibility provides foundational capabilities that support both Telecom Discovery and Telecom Discrepancy Identification & Reconciliation. It includes shared logic, enhanced CI class models, and Identification and
Reconciliation Engine (IRE) updates tailored for telecom network elements.
## Before you begin
Role required: admin
Confirm that:
* Your ServiceNow instance is licensed for TSOM.
* Your MID Server is operational and validated for discovery.
* You review any custom IRE rules applied to telecom CIs to help prevent overrides during upgrade.
## About this task
To configure Telecom Visibility, you must install the required plugins and update the CMDB CI Class Models to version 1.69.0, which introduces telecom-specific IRE identification rules. This confirms accurate CI
identification and reconciliation across telecom domains. Note: If you have customized IRE identification rules for any of the affected telecom CIs, upgrading to version 1.69.0 may override or impact those rules.
The following capabilities are included with the Telecom Visibility subscription:
| Plugin Name | Description | Store App |
| --- | --- | --- |
| Service Graph Connectors `sn_sgc_altiplano_connector` | Service Graph Connector for Nokia Altiplano | Yes |
| Telecommunications Discovery Patterns`sn_tsom_patterns` | Telecommunication Discovery Patterns | Yes |
| Telecom Visibility Plugin (Core logic)`sn_tsom_core` | Core logic for Telecom Visibility and Discrepancy Reconciliation | No |
Note: These plugins automatically trigger the installation or update of the CMDB CI Class Models application to version 1.69.0.
## Procedure
1. Navigate to All > Plugins.
2. Search for and install the following:
1. Service Graph Connector for Nokia Altiplano ( sn\_sgc\_altiplano\_connector)
2. Telecommunication Discovery Patterns ( sn\_tsom\_patterns)
3. Telecom Visibility (plugin) ( sn\_tsom\_core)
3. (Optional)
Update the CMDB CI Class Models.
1. Navigate to All > Available Applications list in the ServiceNow Store.
2. Search for CMDB CI Class Models (sn\_cmdb\_ci\_class).
3. Install or upgrade to version 1.69.0.
Note: Installing any of the TSOM plugins listed above will automatically update or install version 1.69.0 of the CMDB CI Class Models app. If your instance doesn’t include TSOM plugins or you're on a pre-Yokohama release
(for example, Washington DC or Xanadu), you can manually install or upgrade the store app.
4. Navigate to CMDB > Identification Rules.
1. Review rules related to:
* `cmdb_ci_interface_card`
* `cmdb_ci_slot`
* `cmdb_ci_subslot`
* `cmdb_ci_network_adapter`
2. Validate that your custom logic remains functional.
3. Update or merge custom rules as needed.
### Result
Confirm that the following are listed as active:
* Telecom Visibility (sn\_tsom\_core)
* Telecommunication Discovery Patterns (sn\_tsom\_patterns)
* Service Graph Connector for Nokia Altiplano (sn\_sgc\_altiplano\_connector)
* CMDB CI Class Models version 1.69.0
|
https://www.servicenow.com/docs/en-US/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/control-ci-attribute-updates-using-reconciliation-rules.html | https://servicenow-be-prod.servicenow.com/api/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/control-ci-attribute-updates-using-reconciliation-rules.html | 2025-08-02 | daily | 0.5 | 268.xml | en-US | zurich-telecom-service-ops | product/tmt-telecom-service-operations-mgt/task/control-ci-attribute-updates-using-reconciliation-rules.html | zurich | Control CI attribute updates using Reconciliation rules | To prevent specific attributes of a Configuration Item (CI) from being overwritten by Discovery or other data sources, use Reconciliation Rules. These rules define which data source is trusted to update a particular attribute when multiple sources provide values. | [] | [
"Telecommunications Service Operations Management",
"Configuring Telecommunications Service Operations Management",
"Set up Telecom Visibility",
"Activate Telecom Discrepancy Identification and Reconciliation"
] | <article class="hascomments" data-page="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/control-ci-attribute-updates-using-reconciliation-rules.html" id="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/control-ci-attribute-updates-using-reconciliation-rules.html"><body id="control-ci-attribute-updates-using-reconciliation-rules"><main role="main"><article role="article" class="dita" id="control-ci-attribute-updates-using-reconciliation-rules" aria-labelledby="title_control-ci-attribute-updates-using-reconciliation-rules">
<h1 class="title topictitle1" id="title_control-ci-attribute-updates-using-reconciliation-rules">Control CI attribute updates using Reconciliation rules</h1>
<div class="body taskbody"><p class="shortdesc">To prevent specific attributes of a Configuration Item (CI) from being overwritten by Discovery or other data sources, use Reconciliation Rules. These rules define which data source is trusted to update a particular attribute
when multiple sources provide values.</p>
<section class="section prereq" id="control-ci-attribute-updates-using-reconciliation-rules__task-prereq"><div class="tasklabel"><p class="sectiontitle tasklabel">Before you begin</p></div>
<p class="p">Role required: admin</p>
</section>
<section class="section context" id="control-ci-attribute-updates-using-reconciliation-rules__context_x4b_x5b_1gc"><div class="tasklabel"><p class="sectiontitle tasklabel">About this task</p></div>
<p class="p">Reconciliation Rules are processed by the Identification and Reconciliation Engine (IRE) and are essential for maintaining data integrity in the CMDB.</p>
<div class="p">Use Case: If you want to prevent Discovery from updating a set of attributes while allowing another source (like SCCM or manual entry) to update them, define a rule that excludes the Discovery source.<div class="note note note_note"><span class="note__title">Note:</span> Only one
Reconciliation Rule should be active for a specific CI class and attribute combination to avoid conflicts.</div></div>
</section>
<section><div class="tasklabel"><p class="sectiontitle tasklabel">Procedure</p></div><ol class="ol steps"><li class="li step">
<span class="ph cmd">Navigate to <span class="ph menucascade"><span class="ph uicontrol">All</span><abbr> > </abbr><span class="ph uicontrol">CI Class Manager</span></span>.</span>
</li><li class="li step">
<span class="ph cmd">Select the target CI class (e.g., cmdb_ci_computer).</span>
</li><li class="li step">
<span class="ph cmd">In the <span class="ph uicontrol">Reconciliation Rules</span> tab, click <span class="ph uicontrol">New</span> to create a rule.</span>
</li><li class="li step">
<span class="ph cmd">Provide the rule name and select the Discovery source to apply the rule to.</span>
</li><li class="li step">
<span class="ph cmd">Specify the attributes that this rule will govern.</span>
</li><li class="li step">
<span class="ph cmd">Set the source precedence to allow only the selected sources to update the specified attributes.</span>
</li></ol></section>
<section class="section result" id="control-ci-attribute-updates-using-reconciliation-rules__result_axv_hvb_1gc"><div class="tasklabel"><p class="sectiontitle tasklabel">Result</p></div>
<p class="p">Certain CI attributes will no longer be updated by untrusted or lower-priority data sources like Discovery. Only the sources defined in the rule (e.g., SCCM, manual updates) will be allowed to update those attributes.</p>
</section>
</div>
<nav role="navigation"></nav><nav role="navigation" class="tasksNavigation"></nav><nav role="navigation" class="related-links"><div class="col-md-4"><dt>Related tasks</dt><dd><ul><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/task/configure-attribute-value-discrepancy-in-cmdb-360.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/configure-attribute-value-discrepancy-in-cmdb-360.html" class="link" title="Configure attribute comparison settings in CMDB 360 to detect data inconsistencies across multiple discovery sources.">Configure attribute value discrepancy in CMDB 360</a></li></ul></dd></div></nav>
</article></main></body></article> | {
"attachments": {
"all_attachments": null,
"topic_attachments": []
},
"available_languages": [
"enus"
],
"breadcrumbs": [
{
"title": "Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html"
},
{
"title": "Configuring Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/configuring-tsom.html"
},
{
"title": "Set up Telecom Visibility",
"topic_id": "product/tmt-telecom-service-operations-mgt/task/configuring-tsom-visibility.html"
},
{
"title": "Activate Telecom Discrepancy Identification and Reconciliation",
"topic_id": "product/tmt-telecom-service-operations-mgt/task/configure-telecom-reconciliation.html"
}
],
"breadcrumbs_html": "<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops\">Zurich Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html\">Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/configuring-tsom.html\">Configuring Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/configuring-tsom-visibility.html\">Set up Telecom Visibility</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/configure-telecom-reconciliation.html\">Activate Telecom Discrepancy Identification and Reconciliation</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<span class=\"active\">Control CI attribute updates using Reconciliation rules</span>",
"bundle_id": "zurich-telecom-service-ops",
"bundle_key": 2733,
"bundle_landing_page": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html",
"bundle_subtitle": null,
"bundle_title": "Zurich Telecommunications Service Operations Management",
"canonical_link": null,
"dates": {
"Added on": "2025-08-02T00:48:08.794016Z",
"Created on": "2025-07-17T00:00:00Z",
"Initial upload": "2025-07-30T22:24:33.519043Z",
"Updated on": "2025-07-31T00:00:00Z"
},
"dislike_url": "https://servicenow-be-prod.servicenow.com/dislike/55686970",
"dislikes": 0,
"es_archived_content": false,
"is_in_fav": false,
"is_liked": null,
"is_watched": false,
"keywords": [
" zurich zurich"
],
"labels": [
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "zurich",
"navtitle": "Zurich",
"outputclasses": [],
"subjectHeadId": "versions",
"subjectheadNavtitle": "Versions",
"visibility": "show-facet"
},
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "tsom",
"navtitle": "Telecommunications Service Operations Management",
"outputclasses": [],
"subjectHeadId": "products",
"subjectheadNavtitle": "Products",
"visibility": "show-facet"
}
],
"labels_text": "Versions > Zurich; Products > CRM and Industry Products > Telecommunications Media and Technology Assurance > Telecommunications Service Operations Management",
"like_url": "https://servicenow-be-prod.servicenow.com/like/55686970",
"likes": 0,
"metadata": {
"AI Search": null,
"AI Search Assist": null,
"Application Insights": null,
"Capabilities": null,
"Code Signing": null,
"Contextual Search": null,
"DC.contributor": null,
"DC.coverage": null,
"DC.creator": "ServiceNow",
"DC.date.created": "2025-07-17T18:49:38+05:30",
"DC.date.modified": "2025-07-31",
"DC.format": "HTML5",
"DC.identifier": "control-ci-attribute-updates-using-reconciliation-rules",
"DC.language": null,
"DC.relation": "configure-attribute-value-discrepancy-in-cmdb-360.html",
"DC.rights.owner": "(C) Copyright 2025",
"DC.subject": null,
"DC.type": "task",
"Data Discovery": null,
"Data Policy": null,
"Data Privacy": null,
"Discovery": null,
"External Content for AI Search": null,
"Field Administration": null,
"Field Normalization": null,
"Key Management Framework": null,
"Localization Framework": null,
"Now Platform": null,
"PlatSec": null,
"Platform": null,
"Platform Administration": null,
"Platform Performance": null,
"Platform Privacy": null,
"Proactive Triggers": null,
"Process Optimization": null,
"RN doc editing record number": null,
"Search Administration": null,
"Secrets Management": null,
"ServiceNow AI Platform": null,
"State Model": null,
"Subscription Management": null,
"Task Communications Management": null,
"Timeline Visualizations": null,
"User Administration": null,
"User Experience Analytics": null,
"Zing": null,
"ai-now-assist": null,
"app-name": null,
"app_route": null,
"azureapimanagemen": null,
"change-completed": null,
"change-item": null,
"change-request-id": null,
"change-request-reference": null,
"com.glide.embedded_help.category": null,
"component": null,
"copyright": "(C) Copyright 2025",
"crossroads": null,
"data": null,
"description": "To prevent specific attributes of a Configuration Item (CI) from being overwritten by Discovery or other data sources, use Reconciliation Rules. These rules define which data source is trusted to update a particular attribute when multiple sources provide values.",
"dominant_bundle": null,
"erp-canvas-video": null,
"fsm-mobile": null,
"fsm-route": null,
"fsm-sched-opt": null,
"fsm-wrk-order": null,
"genai-round-7": null,
"generator": "DITA-OT",
"glossPartOfSpeech": null,
"glossStatus": null,
"guided setup": null,
"guided tours": null,
"keywords": null,
"min-toc": null,
"mini": null,
"mini-to truec": null,
"mini-toc": null,
"mini_toc": null,
"minitoc": null,
"modification": null,
"now-assist-app-gen-video": null,
"order": null,
"page-type": null,
"page-type ": null,
"prodname": null,
"product": null,
"product_name": null,
"release": null,
"resourceID": null,
"roles": null,
"route_page": null,
"route_params_listId": null,
"route_params_table": null,
"route_params_type": null,
"route_type": null,
"setconfigurationproperties": null,
"topic": null,
"translation-type": "source",
"version": null,
"workflow": "Customer and Industry",
"workplace-srvc-delvry-ditamap": null
},
"page_id": "product/tmt-telecom-service-operations-mgt/task/control-ci-attribute-updates-using-reconciliation-rules.html",
"page_key": 55686970,
"preprocessed_PDF": "https://downloads.docs.servicenow.com/pdf/enus/servicenow-zurich-telecom-service-ops-enus.pdf",
"rating": null,
"read_time_data": {
"char_count": 1429,
"img_count": 0,
"read_time": 1,
"video_links": [
""
],
"word_count": 221
},
"related_links": [
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "Configure attribute comparison settings in CMDB 360 to detect data inconsistencies across multiple discovery sources.",
"title": "Configure attribute value discrepancy in CMDB 360",
"topic": "/product/tmt-telecom-service-operations-mgt/task/configure-attribute-value-discrepancy-in-cmdb-360.html",
"type": "task",
"url": null
}
],
"search_title": null,
"title": "Control CI attribute updates using Reconciliation rules",
"topic_cluster": {
"clustered_by": {
"enabled": true,
"primary_key": "versions",
"primary_sort": "top-down",
"type": "subjecthead"
},
"clustered_labels": [
"versions"
],
"clustered_topics": [],
"clustering_title": "Zurich"
},
"topic_html": "<article class=\"hascomments\" data-page=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/control-ci-attribute-updates-using-reconciliation-rules.html\" id=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/control-ci-attribute-updates-using-reconciliation-rules.html\"><body id=\"control-ci-attribute-updates-using-reconciliation-rules\"><main role=\"main\"><article role=\"article\" class=\"dita\" id=\"control-ci-attribute-updates-using-reconciliation-rules\" aria-labelledby=\"title_control-ci-attribute-updates-using-reconciliation-rules\">\n <h1 class=\"title topictitle1\" id=\"title_control-ci-attribute-updates-using-reconciliation-rules\">Control CI attribute updates using Reconciliation rules</h1>\n \n \n <div class=\"body taskbody\"><p class=\"shortdesc\">To prevent specific attributes of a Configuration Item (CI) from being overwritten by Discovery or other data sources, use Reconciliation Rules. These rules define which data source is trusted to update a particular attribute\n when multiple sources provide values.</p>\n <section class=\"section prereq\" id=\"control-ci-attribute-updates-using-reconciliation-rules__task-prereq\"><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">Before you begin</p></div>\n <p class=\"p\">Role required: admin</p>\n </section>\n <section class=\"section context\" id=\"control-ci-attribute-updates-using-reconciliation-rules__context_x4b_x5b_1gc\"><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">About this task</p></div>\n <p class=\"p\">Reconciliation Rules are processed by the Identification and Reconciliation Engine (IRE) and are essential for maintaining data integrity in the CMDB.</p>\n <div class=\"p\">Use Case: If you want to prevent Discovery from updating a set of attributes while allowing another source (like SCCM or manual entry) to update them, define a rule that excludes the Discovery source.<div class=\"note note note_note\"><span class=\"note__title\">Note:</span> Only one\n Reconciliation Rule should be active for a specific CI class and attribute combination to avoid conflicts.</div></div>\n </section>\n <section><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">Procedure</p></div><ol class=\"ol steps\"><li class=\"li step\">\n <span class=\"ph cmd\">Navigate to <span class=\"ph menucascade\"><span class=\"ph uicontrol\">All</span><abbr> > </abbr><span class=\"ph uicontrol\">CI Class Manager</span></span>.</span>\n </li><li class=\"li step\">\n <span class=\"ph cmd\">Select the target CI class (e.g., cmdb_ci_computer).</span>\n </li><li class=\"li step\">\n <span class=\"ph cmd\">In the <span class=\"ph uicontrol\">Reconciliation Rules</span> tab, click <span class=\"ph uicontrol\">New</span> to create a rule.</span>\n </li><li class=\"li step\">\n <span class=\"ph cmd\">Provide the rule name and select the Discovery source to apply the rule to.</span>\n </li><li class=\"li step\">\n <span class=\"ph cmd\">Specify the attributes that this rule will govern.</span>\n </li><li class=\"li step\">\n <span class=\"ph cmd\">Set the source precedence to allow only the selected sources to update the specified attributes.</span>\n </li></ol></section>\n <section class=\"section result\" id=\"control-ci-attribute-updates-using-reconciliation-rules__result_axv_hvb_1gc\"><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">Result</p></div>\n <p class=\"p\">Certain CI attributes will no longer be updated by untrusted or lower-priority data sources like Discovery. Only the sources defined in the rule (e.g., SCCM, manual updates) will be allowed to update those attributes.</p>\n </section>\n </div>\n <nav role=\"navigation\"></nav><nav role=\"navigation\" class=\"tasksNavigation\"></nav><nav role=\"navigation\" class=\"related-links\"><div class=\"col-md-4\"><dt>Related tasks</dt><dd><ul><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/task/configure-attribute-value-discrepancy-in-cmdb-360.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/configure-attribute-value-discrepancy-in-cmdb-360.html\" class=\"link\" title=\"Configure attribute comparison settings in CMDB 360 to detect data inconsistencies across multiple discovery sources.\">Configure attribute value discrepancy in CMDB 360</a></li></ul></dd></div></nav>\n</article></main></body></article>",
"topic_language": "enus",
"views": 0,
"your_rating": null
} | # Control CI attribute updates using Reconciliation rules
To prevent specific attributes of a Configuration Item (CI) from being overwritten by Discovery or other data sources, use Reconciliation Rules. These rules define which data source is trusted to update a particular attribute
when multiple sources provide values.
## Before you begin
Role required: admin
## About this task
Reconciliation Rules are processed by the Identification and Reconciliation Engine (IRE) and are essential for maintaining data integrity in the CMDB.
Use Case: If you want to prevent Discovery from updating a set of attributes while allowing another source (like SCCM or manual entry) to update them, define a rule that excludes the Discovery source.Note: Only one
Reconciliation Rule should be active for a specific CI class and attribute combination to avoid conflicts.
## Procedure
1. Navigate to All > CI Class Manager.
2. Select the target CI class (e.g., cmdb\_ci\_computer).
3. In the Reconciliation Rules tab, click New to create a rule.
4. Provide the rule name and select the Discovery source to apply the rule to.
5. Specify the attributes that this rule will govern.
6. Set the source precedence to allow only the selected sources to update the specified attributes.
### Result
Certain CI attributes will no longer be updated by untrusted or lower-priority data sources like Discovery. Only the sources defined in the rule (e.g., SCCM, manual updates) will be allowed to update those attributes.
| ---
title: Control CI attribute updates using Reconciliation rules
description: To prevent specific attributes of a Configuration Item (CI) from being
overwritten by Discovery or other data sources, use Reconciliation Rules. These
rules define which data source is trusted to update a particular attribute when
multiple sources provide values.
keywords: []
breadcrumbs:
- Telecommunications Service Operations Management
- Configuring Telecommunications Service Operations Management
- Set up Telecom Visibility
- Activate Telecom Discrepancy Identification and Reconciliation
---
# Control CI attribute updates using Reconciliation rules
To prevent specific attributes of a Configuration Item (CI) from being overwritten by Discovery or other data sources, use Reconciliation Rules. These rules define which data source is trusted to update a particular attribute
when multiple sources provide values.
## Before you begin
Role required: admin
## About this task
Reconciliation Rules are processed by the Identification and Reconciliation Engine (IRE) and are essential for maintaining data integrity in the CMDB.
Use Case: If you want to prevent Discovery from updating a set of attributes while allowing another source (like SCCM or manual entry) to update them, define a rule that excludes the Discovery source.Note: Only one
Reconciliation Rule should be active for a specific CI class and attribute combination to avoid conflicts.
## Procedure
1. Navigate to All > CI Class Manager.
2. Select the target CI class (e.g., cmdb\_ci\_computer).
3. In the Reconciliation Rules tab, click New to create a rule.
4. Provide the rule name and select the Discovery source to apply the rule to.
5. Specify the attributes that this rule will govern.
6. Set the source precedence to allow only the selected sources to update the specified attributes.
### Result
Certain CI attributes will no longer be updated by untrusted or lower-priority data sources like Discovery. Only the sources defined in the rule (e.g., SCCM, manual updates) will be allowed to update those attributes.
|
https://www.servicenow.com/docs/en-US/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/create-a-data-source-similar-to-tsom-core-data-source.html | https://servicenow-be-prod.servicenow.com/api/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/create-a-data-source-similar-to-tsom-core-data-source.html | 2025-08-02 | daily | 0.5 | 268.xml | en-US | zurich-telecom-service-ops | product/tmt-telecom-service-operations-mgt/task/create-a-data-source-similar-to-tsom-core-data-source.html | zurich | Create a data source similar to Telecom core data source | Set up a schema-compliant data source in the connector’s application scope to simulate telecom data and ensure successful testing and validation of the Telecom Discovery Builder framework ETL before integrating with live device data. | [] | [
"Telecommunications Service Operations Management",
"Configuring Telecommunications Service Operations Management",
"Set up Telecom Visibility",
"Configuring the Telecom Discovery Builder framework ETL in a connector"
] | <article class="hascomments" data-page="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/create-a-data-source-similar-to-tsom-core-data-source.html" id="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/create-a-data-source-similar-to-tsom-core-data-source.html"><body id="create-a-data-source-similar-to-tsom-core-data-source"><main role="main"><article role="article" class="dita" id="create-a-data-source-similar-to-tsom-core-data-source" aria-labelledby="title_create-a-data-source-similar-to-tsom-core-data-source">
<h1 class="title topictitle1" id="title_create-a-data-source-similar-to-tsom-core-data-source">Create a data source similar to Telecom core data source</h1>
<div class="body taskbody"><p class="shortdesc">Set up a schema-compliant data source in the connector’s application scope to simulate telecom data and ensure successful testing and validation of the Telecom Discovery Builder framework ETL before integrating with live
device data.</p>
<section class="section prereq" id="create-a-data-source-similar-to-tsom-core-data-source__task-prereq"><div class="tasklabel"><p class="sectiontitle tasklabel">Before you begin</p></div>
<p class="p">Role required: admin</p>
<div class="p">Ensure the following:<ul class="ul" id="create-a-data-source-similar-to-tsom-core-data-source__ul_ifr_tpz_dfc">
<li class="li">Access to the TSOM Core application and its data sources.</li>
<li class="li">Switch to the connector’s application scope.</li>
<li class="li">Have a sample payload that conforms to the Telco Generic Schema (optional, but recommended for testing).</li>
</ul></div>
</section>
<section class="section context" id="create-a-data-source-similar-to-tsom-core-data-source__context_u4w_5pz_dfc"><div class="tasklabel"><p class="sectiontitle tasklabel">About this task</p></div>
<p class="p">When duplicating the Telecom Discovery Builder framework ETL into a Service Graph Connector (SGC) application scope, you must first create a data source that replicates the exact structure of the TSOM Core data source. This
duplicated data source provides the required schema and structure for testing and validating the ETL before connecting it to live telecom data.</p>
<p class="p">The Telecom Discovery Builder framework expects data that conforms to the Telco Generic Schema, as defined in the Telecom Core. Duplicating the original TSOM data source ensures:</p>
<ul class="ul" id="create-a-data-source-similar-to-tsom-core-data-source__ul_q4f_ypz_dfc">
<li class="li">Schema alignment during ETL duplication.</li>
<li class="li">A valid import set structure for testing.</li>
<li class="li">Separation of core and connector scopes for customization and upgrade safety.</li>
</ul>
<p class="p">When to create a data source similar to the TSOM Core data source:</p>
<ul class="ul" id="create-a-data-source-similar-to-tsom-core-data-source__ul_oqy_zpz_dfc">
<li class="li">Before duplicating the Telecom Discovery Builder framework ETL.</li>
<li class="li">When you want to run a test load using simulated or placeholder telecom data.</li>
<li class="li">When preparing the connector’s application scope for ingestion configuration.</li>
</ul>
<p class="p">The following screenshot can help you understand to fill the field values while you create the data source.<img src="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/../images/datasource.png?_LANG=enus" class="image" id="create-a-data-source-similar-to-tsom-core-data-source__image_hn1_2cw_vfc" alt="Create data source user interface"/></p>
</section>
<section><div class="tasklabel"><p class="sectiontitle tasklabel">Procedure</p></div><ol class="ol steps"><li class="li step stepexpand">
<span class="ph cmd">Navigate to <span class="ph menucascade"><span class="ph uicontrol">All</span><abbr> > </abbr><span class="ph uicontrol">System Import Sets</span><abbr> > </abbr><span class="ph uicontrol">Administration</span><abbr> > </abbr><span class="ph uicontrol">Data Sources</span></span>.</span>
</li><li class="li step stepexpand">
<span class="ph cmd">Find the <span class="ph uicontrol">Generic Schema Multi Source v2</span> or a similar baseline source provided with TSOM Core.</span>
</li><li class="li step stepexpand">
<span class="ph cmd">Open the TSOM Core data source record and copy the script from the <span class="ph uicontrol">Data Loader</span> field.</span>
</li><li class="li step stepexpand">
<span class="ph cmd">Create a data source by clicking <span class="ph uicontrol">New</span>.</span>
</li><li class="li step stepexpand">
<span class="ph cmd">On the form, fill in the fields</span>
<div class="itemgroup info">For more information, see <a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/task//csh" href="https://servicenow-be-prod.servicenow.com/csh?topicname=create-custom-type-data-source&version=zurich&pubname=zurich-integrate-applications" class="xref">Create a Custom (Load by Script) type data source</a>.</div>
</li><li class="li step stepexpand">
<span class="ph cmd">In the <span class="ph uicontrol">Type</span> field, select <span class="ph uicontrol">Custom (Load by Script)</span>.</span>
</li><li class="li step stepexpand">
<span class="ph cmd">Select the <span class="ph uicontrol">Data in single column</span> field.</span>
</li><li class="li step stepexpand">
<span class="ph cmd">In the <span class="ph uicontrol">Data Loader</span> field, paste the copied script.</span>
</li><li class="li step stepexpand">
<span class="ph cmd">Select <span class="ph uicontrol">Submit</span>.</span>
<div class="itemgroup stepresult">The data source is created.</div>
</li><li class="li step stepexpand">(Optional)
<span class="ph cmd">To test load the data source:</span>
<ol type="a" class="ol substeps" id="create-a-data-source-similar-to-tsom-core-data-source__substeps_srr_cw4_ffc">
<li class="li substep">
<span class="ph cmd">Click Test Load 20 Records (or similar) to generate an import set.</span>
</li>
<li class="li substep">
<span class="ph cmd">Ensure that records are created without errors.</span>
</li>
<li class="li substep">
<span class="ph cmd">Confirm that classes like Logical Composite, Network Gear, or Port appear in the staging table.</span>
</li>
</ol>
</li></ol></section>
<section class="section postreq" id="create-a-data-source-similar-to-tsom-core-data-source__postreq_jdg_jw4_ffc"><div class="tasklabel"><p class="sectiontitle tasklabel">What to do next</p></div>
<p class="p">After the data source is created and tested:</p>
<ul class="ul" id="create-a-data-source-similar-to-tsom-core-data-source__ul_if5_jw4_ffc">
<li class="li">Use it as the import source when duplicating the Telco Generic ETL.</li>
<li class="li">Replace it with the actual connector-specific data source once simulation and validation are complete.</li>
</ul>
</section>
</div>
<nav role="navigation"></nav><nav role="navigation" class="tasksNavigation"></nav><nav role="navigation" class="related-links"><div class="col-md-4"><dt>Related tasks</dt><dd><ul><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/task/duplicate-the-generic-etl-to-use-a-specific-connector.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/duplicate-the-generic-etl-to-use-a-specific-connector.html" class="link" title="The Telecom Discovery Builder framework ETL enables Service Graph Connector (SGC) teams to rapidly adopt a standardized, schema-compliant data ingestion pipeline without building ETL logic from scratch.">Duplicate the Telecom Discovery Builder framework ETL into a connector scope</a></li></ul></dd></div><div class="col-md-4"><dt>Related concepts</dt><dd><ul><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/concept/overview-of-standardized-json-common-data-set.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/overview-of-standardized-json-common-data-set.html" class="link" title="Use the TSOM architecture to support standardized Service Graph Connectors using a unified schema and reusable ETL logic. This reduces onboarding time for new connectors and simplifies integration with CMDB.">Standardized JSON common data set to support all service graph connectors</a></li></ul></dd></div></nav>
</article></main></body></article> | {
"attachments": {
"all_attachments": null,
"topic_attachments": []
},
"available_languages": [
"enus"
],
"breadcrumbs": [
{
"title": "Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html"
},
{
"title": "Configuring Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/configuring-tsom.html"
},
{
"title": "Set up Telecom Visibility",
"topic_id": "product/tmt-telecom-service-operations-mgt/task/configuring-tsom-visibility.html"
},
{
"title": "Configuring the Telecom Discovery Builder framework ETL in a connector",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/configuring-the-telco-generic-schema-etl.html"
}
],
"breadcrumbs_html": "<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops\">Zurich Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html\">Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/configuring-tsom.html\">Configuring Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/configuring-tsom-visibility.html\">Set up Telecom Visibility</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/configuring-the-telco-generic-schema-etl.html\">Configuring the Telecom Discovery Builder framework ETL in a connector</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<span class=\"active\">Create a data source similar to Telecom core data source</span>",
"bundle_id": "zurich-telecom-service-ops",
"bundle_key": 2733,
"bundle_landing_page": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html",
"bundle_subtitle": null,
"bundle_title": "Zurich Telecommunications Service Operations Management",
"canonical_link": null,
"dates": {
"Added on": "2025-08-02T00:48:08.794016Z",
"Created on": "2025-04-29T00:00:00Z",
"Initial upload": "2025-07-30T22:24:33.519043Z",
"Updated on": "2025-07-31T00:00:00Z"
},
"dislike_url": "https://servicenow-be-prod.servicenow.com/dislike/55686971",
"dislikes": 0,
"es_archived_content": false,
"is_in_fav": false,
"is_liked": null,
"is_watched": false,
"keywords": [
" zurich zurich"
],
"labels": [
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "zurich",
"navtitle": "Zurich",
"outputclasses": [],
"subjectHeadId": "versions",
"subjectheadNavtitle": "Versions",
"visibility": "show-facet"
},
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "tsom",
"navtitle": "Telecommunications Service Operations Management",
"outputclasses": [],
"subjectHeadId": "products",
"subjectheadNavtitle": "Products",
"visibility": "show-facet"
}
],
"labels_text": "Versions > Zurich; Products > CRM and Industry Products > Telecommunications Media and Technology Assurance > Telecommunications Service Operations Management",
"like_url": "https://servicenow-be-prod.servicenow.com/like/55686971",
"likes": 0,
"metadata": {
"AI Search": null,
"AI Search Assist": null,
"Application Insights": null,
"Capabilities": null,
"Code Signing": null,
"Contextual Search": null,
"DC.contributor": null,
"DC.coverage": null,
"DC.creator": "ServiceNow",
"DC.date.created": "2025-04-29T19:40:42+05:30",
"DC.date.modified": "2025-07-31",
"DC.format": "HTML5",
"DC.identifier": "create-a-data-source-similar-to-tsom-core-data-source",
"DC.language": null,
"DC.relation": "../concept/overview-of-standardized-json-common-data-set.html",
"DC.rights.owner": "(C) Copyright 2025",
"DC.subject": null,
"DC.type": "task",
"Data Discovery": null,
"Data Policy": null,
"Data Privacy": null,
"Discovery": null,
"External Content for AI Search": null,
"Field Administration": null,
"Field Normalization": null,
"Key Management Framework": null,
"Localization Framework": null,
"Now Platform": null,
"PlatSec": null,
"Platform": null,
"Platform Administration": null,
"Platform Performance": null,
"Platform Privacy": null,
"Proactive Triggers": null,
"Process Optimization": null,
"RN doc editing record number": null,
"Search Administration": null,
"Secrets Management": null,
"ServiceNow AI Platform": null,
"State Model": null,
"Subscription Management": null,
"Task Communications Management": null,
"Timeline Visualizations": null,
"User Administration": null,
"User Experience Analytics": null,
"Zing": null,
"ai-now-assist": null,
"app-name": null,
"app_route": null,
"azureapimanagemen": null,
"change-completed": null,
"change-item": null,
"change-request-id": null,
"change-request-reference": null,
"com.glide.embedded_help.category": null,
"component": null,
"copyright": "(C) Copyright 2025",
"crossroads": null,
"data": null,
"description": "Set up a schema-compliant data source in the connector’s application scope to simulate telecom data and ensure successful testing and validation of the Telecom Discovery Builder framework ETL before integrating with live device data.",
"dominant_bundle": null,
"erp-canvas-video": null,
"fsm-mobile": null,
"fsm-route": null,
"fsm-sched-opt": null,
"fsm-wrk-order": null,
"genai-round-7": null,
"generator": "DITA-OT",
"glossPartOfSpeech": null,
"glossStatus": null,
"guided setup": null,
"guided tours": null,
"keywords": null,
"min-toc": null,
"mini": null,
"mini-to truec": null,
"mini-toc": null,
"mini_toc": null,
"minitoc": null,
"modification": null,
"now-assist-app-gen-video": null,
"order": null,
"page-type": null,
"page-type ": null,
"prodname": null,
"product": null,
"product_name": null,
"release": null,
"resourceID": null,
"roles": null,
"route_page": null,
"route_params_listId": null,
"route_params_table": null,
"route_params_type": null,
"route_type": null,
"setconfigurationproperties": null,
"topic": null,
"translation-type": "source",
"version": null,
"workflow": "Customer and Industry",
"workplace-srvc-delvry-ditamap": null
},
"page_id": "product/tmt-telecom-service-operations-mgt/task/create-a-data-source-similar-to-tsom-core-data-source.html",
"page_key": 55686971,
"preprocessed_PDF": "https://downloads.docs.servicenow.com/pdf/enus/servicenow-zurich-telecom-service-ops-enus.pdf",
"rating": null,
"read_time_data": {
"char_count": 2725,
"img_count": 1,
"read_time": 2,
"video_links": [
""
],
"word_count": 435
},
"related_links": [
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "Use the TSOM architecture to support standardized Service Graph Connectors using a unified schema and reusable ETL logic. This reduces onboarding time for new connectors and simplifies integration with CMDB.",
"title": "Standardized JSON common data set to support all service graph connectors",
"topic": "/product/tmt-telecom-service-operations-mgt/concept/overview-of-standardized-json-common-data-set.html",
"type": "concept",
"url": null
},
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "The Telecom Discovery Builder framework ETL enables Service Graph Connector (SGC) teams to rapidly adopt a standardized, schema-compliant data ingestion pipeline without building ETL logic from scratch.",
"title": "Duplicate the Telecom Discovery Builder framework ETL into a connector scope",
"topic": "/product/tmt-telecom-service-operations-mgt/task/duplicate-the-generic-etl-to-use-a-specific-connector.html",
"type": "task",
"url": null
}
],
"search_title": null,
"title": "Create a data source similar to Telecom core data source",
"topic_cluster": {
"clustered_by": {
"enabled": true,
"primary_key": "versions",
"primary_sort": "top-down",
"type": "subjecthead"
},
"clustered_labels": [
"versions"
],
"clustered_topics": [],
"clustering_title": "Zurich"
},
"topic_html": "<article class=\"hascomments\" data-page=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/create-a-data-source-similar-to-tsom-core-data-source.html\" id=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/create-a-data-source-similar-to-tsom-core-data-source.html\"><body id=\"create-a-data-source-similar-to-tsom-core-data-source\"><main role=\"main\"><article role=\"article\" class=\"dita\" id=\"create-a-data-source-similar-to-tsom-core-data-source\" aria-labelledby=\"title_create-a-data-source-similar-to-tsom-core-data-source\">\n <h1 class=\"title topictitle1\" id=\"title_create-a-data-source-similar-to-tsom-core-data-source\">Create a data source similar to Telecom core data source</h1>\n \n \n <div class=\"body taskbody\"><p class=\"shortdesc\">Set up a schema-compliant data source in the connector’s application scope to simulate telecom data and ensure successful testing and validation of the Telecom Discovery Builder framework ETL before integrating with live\n device data.</p>\n <section class=\"section prereq\" id=\"create-a-data-source-similar-to-tsom-core-data-source__task-prereq\"><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">Before you begin</p></div>\n <p class=\"p\">Role required: admin</p>\n <div class=\"p\">Ensure the following:<ul class=\"ul\" id=\"create-a-data-source-similar-to-tsom-core-data-source__ul_ifr_tpz_dfc\">\n <li class=\"li\">Access to the TSOM Core application and its data sources.</li>\n <li class=\"li\">Switch to the connector’s application scope.</li>\n <li class=\"li\">Have a sample payload that conforms to the Telco Generic Schema (optional, but recommended for testing).</li>\n </ul></div>\n </section>\n <section class=\"section context\" id=\"create-a-data-source-similar-to-tsom-core-data-source__context_u4w_5pz_dfc\"><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">About this task</p></div>\n <p class=\"p\">When duplicating the Telecom Discovery Builder framework ETL into a Service Graph Connector (SGC) application scope, you must first create a data source that replicates the exact structure of the TSOM Core data source. This\n duplicated data source provides the required schema and structure for testing and validating the ETL before connecting it to live telecom data.</p>\n <p class=\"p\">The Telecom Discovery Builder framework expects data that conforms to the Telco Generic Schema, as defined in the Telecom Core. Duplicating the original TSOM data source ensures:</p>\n <ul class=\"ul\" id=\"create-a-data-source-similar-to-tsom-core-data-source__ul_q4f_ypz_dfc\">\n <li class=\"li\">Schema alignment during ETL duplication.</li>\n <li class=\"li\">A valid import set structure for testing.</li>\n <li class=\"li\">Separation of core and connector scopes for customization and upgrade safety.</li>\n </ul>\n <p class=\"p\">When to create a data source similar to the TSOM Core data source:</p>\n <ul class=\"ul\" id=\"create-a-data-source-similar-to-tsom-core-data-source__ul_oqy_zpz_dfc\">\n <li class=\"li\">Before duplicating the Telecom Discovery Builder framework ETL.</li>\n <li class=\"li\">When you want to run a test load using simulated or placeholder telecom data.</li>\n <li class=\"li\">When preparing the connector’s application scope for ingestion configuration.</li>\n </ul>\n <p class=\"p\">The following screenshot can help you understand to fill the field values while you create the data source.<img src=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/../images/datasource.png?_LANG=enus\" class=\"image\" id=\"create-a-data-source-similar-to-tsom-core-data-source__image_hn1_2cw_vfc\" alt=\"Create data source user interface\"/></p>\n </section>\n <section><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">Procedure</p></div><ol class=\"ol steps\"><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">Navigate to <span class=\"ph menucascade\"><span class=\"ph uicontrol\">All</span><abbr> > </abbr><span class=\"ph uicontrol\">System Import Sets</span><abbr> > </abbr><span class=\"ph uicontrol\">Administration</span><abbr> > </abbr><span class=\"ph uicontrol\">Data Sources</span></span>.</span>\n </li><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">Find the <span class=\"ph uicontrol\">Generic Schema Multi Source v2</span> or a similar baseline source provided with TSOM Core.</span>\n </li><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">Open the TSOM Core data source record and copy the script from the <span class=\"ph uicontrol\">Data Loader</span> field.</span>\n </li><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">Create a data source by clicking <span class=\"ph uicontrol\">New</span>.</span>\n </li><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">On the form, fill in the fields</span>\n <div class=\"itemgroup info\">For more information, see <a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/task//csh\" href=\"https://servicenow-be-prod.servicenow.com/csh?topicname=create-custom-type-data-source&version=zurich&pubname=zurich-integrate-applications\" class=\"xref\">Create a Custom (Load by Script) type data source</a>.</div>\n </li><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">In the <span class=\"ph uicontrol\">Type</span> field, select <span class=\"ph uicontrol\">Custom (Load by Script)</span>.</span>\n </li><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">Select the <span class=\"ph uicontrol\">Data in single column</span> field.</span>\n </li><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">In the <span class=\"ph uicontrol\">Data Loader</span> field, paste the copied script.</span>\n </li><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">Select <span class=\"ph uicontrol\">Submit</span>.</span>\n <div class=\"itemgroup stepresult\">The data source is created.</div>\n </li><li class=\"li step stepexpand\">(Optional) \n <span class=\"ph cmd\">To test load the data source:</span>\n <ol type=\"a\" class=\"ol substeps\" id=\"create-a-data-source-similar-to-tsom-core-data-source__substeps_srr_cw4_ffc\">\n <li class=\"li substep\">\n <span class=\"ph cmd\">Click Test Load 20 Records (or similar) to generate an import set.</span>\n </li>\n <li class=\"li substep\">\n <span class=\"ph cmd\">Ensure that records are created without errors.</span>\n </li>\n <li class=\"li substep\">\n <span class=\"ph cmd\">Confirm that classes like Logical Composite, Network Gear, or Port appear in the staging table.</span>\n </li>\n </ol>\n </li></ol></section>\n <section class=\"section postreq\" id=\"create-a-data-source-similar-to-tsom-core-data-source__postreq_jdg_jw4_ffc\"><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">What to do next</p></div>\n <p class=\"p\">After the data source is created and tested:</p>\n <ul class=\"ul\" id=\"create-a-data-source-similar-to-tsom-core-data-source__ul_if5_jw4_ffc\">\n <li class=\"li\">Use it as the import source when duplicating the Telco Generic ETL.</li>\n <li class=\"li\">Replace it with the actual connector-specific data source once simulation and validation are complete.</li>\n </ul>\n </section>\n </div>\n <nav role=\"navigation\"></nav><nav role=\"navigation\" class=\"tasksNavigation\"></nav><nav role=\"navigation\" class=\"related-links\"><div class=\"col-md-4\"><dt>Related tasks</dt><dd><ul><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/task/duplicate-the-generic-etl-to-use-a-specific-connector.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/duplicate-the-generic-etl-to-use-a-specific-connector.html\" class=\"link\" title=\"The Telecom Discovery Builder framework ETL enables Service Graph Connector (SGC) teams to rapidly adopt a standardized, schema-compliant data ingestion pipeline without building ETL logic from scratch.\">Duplicate the Telecom Discovery Builder framework ETL into a connector scope</a></li></ul></dd></div><div class=\"col-md-4\"><dt>Related concepts</dt><dd><ul><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept/overview-of-standardized-json-common-data-set.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/overview-of-standardized-json-common-data-set.html\" class=\"link\" title=\"Use the TSOM architecture to support standardized Service Graph Connectors using a unified schema and reusable ETL logic. This reduces onboarding time for new connectors and simplifies integration with CMDB.\">Standardized JSON common data set to support all service graph connectors</a></li></ul></dd></div></nav>\n</article></main></body></article>",
"topic_language": "enus",
"views": 0,
"your_rating": null
} | # Create a data source similar to Telecom core data source
Set up a schema-compliant data source in the connector’s application scope to simulate telecom data and ensure successful testing and validation of the Telecom Discovery Builder framework ETL before integrating with live
device data.
## Before you begin
Role required: admin
Ensure the following:
* Access to the TSOM Core application and its data sources.
* Switch to the connector’s application scope.
* Have a sample payload that conforms to the Telco Generic Schema (optional, but recommended for testing).
## About this task
When duplicating the Telecom Discovery Builder framework ETL into a Service Graph Connector (SGC) application scope, you must first create a data source that replicates the exact structure of the TSOM Core data source. This
duplicated data source provides the required schema and structure for testing and validating the ETL before connecting it to live telecom data.
The Telecom Discovery Builder framework expects data that conforms to the Telco Generic Schema, as defined in the Telecom Core. Duplicating the original TSOM data source ensures:
* Schema alignment during ETL duplication.
* A valid import set structure for testing.
* Separation of core and connector scopes for customization and upgrade safety.
When to create a data source similar to the TSOM Core data source:
* Before duplicating the Telecom Discovery Builder framework ETL.
* When you want to run a test load using simulated or placeholder telecom data.
* When preparing the connector’s application scope for ingestion configuration.
The following screenshot can help you understand to fill the field values while you create the data source.
## Procedure
1. Navigate to All > System Import Sets > Administration > Data Sources.
2. Find the Generic Schema Multi Source v2 or a similar baseline source provided with TSOM Core.
3. Open the TSOM Core data source record and copy the script from the Data Loader field.
4. Create a data source by clicking New.
5. On the form, fill in the fields
For more information, see Create a Custom (Load by Script) type data source.
6. In the Type field, select Custom (Load by Script).
7. Select the Data in single column field.
8. In the Data Loader field, paste the copied script.
9. Select Submit.
The data source is created.
10. (Optional)
To test load the data source:
1. Click Test Load 20 Records (or similar) to generate an import set.
2. Ensure that records are created without errors.
3. Confirm that classes like Logical Composite, Network Gear, or Port appear in the staging table.
### What to do next
After the data source is created and tested:
* Use it as the import source when duplicating the Telco Generic ETL.
* Replace it with the actual connector-specific data source once simulation and validation are complete.
| ---
title: Create a data source similar to Telecom core data source
description: "Set up a schema-compliant data source in the connector\u2019s application\
\ scope to simulate telecom data and ensure successful testing and validation of\
\ the Telecom Discovery Builder framework ETL before integrating with live device\
\ data."
keywords: []
breadcrumbs:
- Telecommunications Service Operations Management
- Configuring Telecommunications Service Operations Management
- Set up Telecom Visibility
- Configuring the Telecom Discovery Builder framework ETL in a connector
---
# Create a data source similar to Telecom core data source
Set up a schema-compliant data source in the connector’s application scope to simulate telecom data and ensure successful testing and validation of the Telecom Discovery Builder framework ETL before integrating with live
device data.
## Before you begin
Role required: admin
Ensure the following:
* Access to the TSOM Core application and its data sources.
* Switch to the connector’s application scope.
* Have a sample payload that conforms to the Telco Generic Schema (optional, but recommended for testing).
## About this task
When duplicating the Telecom Discovery Builder framework ETL into a Service Graph Connector (SGC) application scope, you must first create a data source that replicates the exact structure of the TSOM Core data source. This
duplicated data source provides the required schema and structure for testing and validating the ETL before connecting it to live telecom data.
The Telecom Discovery Builder framework expects data that conforms to the Telco Generic Schema, as defined in the Telecom Core. Duplicating the original TSOM data source ensures:
* Schema alignment during ETL duplication.
* A valid import set structure for testing.
* Separation of core and connector scopes for customization and upgrade safety.
When to create a data source similar to the TSOM Core data source:
* Before duplicating the Telecom Discovery Builder framework ETL.
* When you want to run a test load using simulated or placeholder telecom data.
* When preparing the connector’s application scope for ingestion configuration.
The following screenshot can help you understand to fill the field values while you create the data source.
## Procedure
1. Navigate to All > System Import Sets > Administration > Data Sources.
2. Find the Generic Schema Multi Source v2 or a similar baseline source provided with TSOM Core.
3. Open the TSOM Core data source record and copy the script from the Data Loader field.
4. Create a data source by clicking New.
5. On the form, fill in the fields
For more information, see Create a Custom (Load by Script) type data source.
6. In the Type field, select Custom (Load by Script).
7. Select the Data in single column field.
8. In the Data Loader field, paste the copied script.
9. Select Submit.
The data source is created.
10. (Optional)
To test load the data source:
1. Click Test Load 20 Records (or similar) to generate an import set.
2. Ensure that records are created without errors.
3. Confirm that classes like Logical Composite, Network Gear, or Port appear in the staging table.
### What to do next
After the data source is created and tested:
* Use it as the import source when duplicating the Telco Generic ETL.
* Replace it with the actual connector-specific data source once simulation and validation are complete.
|
https://www.servicenow.com/docs/en-US/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/deploy-a-new-service-graph-connector-with-duplicated-etl.html | https://servicenow-be-prod.servicenow.com/api/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/deploy-a-new-service-graph-connector-with-duplicated-etl.html | 2025-08-02 | daily | 0.5 | 268.xml | en-US | zurich-telecom-service-ops | product/tmt-telecom-service-operations-mgt/task/deploy-a-new-service-graph-connector-with-duplicated-etl.html | zurich | Deploy a new service graph connector with existing ETL | Associate a new Service Graph Connector (SGC) with an existing ETL. | [] | [
"Telecommunications Service Operations Management",
"Configuring Telecommunications Service Operations Management",
"Set up Telecom Visibility",
"Configuring the Telecom Discovery Builder framework ETL in a connector"
] | <article class="hascomments" data-page="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/deploy-a-new-service-graph-connector-with-duplicated-etl.html" id="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/deploy-a-new-service-graph-connector-with-duplicated-etl.html"><body id="deploy-a-new-service-graph-connector-with-duplicated-etl"><main role="main"><article role="article" class="dita" id="deploy-a-new-service-graph-connector-with-duplicated-etl" aria-labelledby="title_deploy-a-new-service-graph-connector-with-duplicated-etl">
<h1 class="title topictitle1" id="title_deploy-a-new-service-graph-connector-with-duplicated-etl">Deploy a new service graph connector with existing ETL</h1>
<div class="body taskbody"><p class="shortdesc">Associate a new Service Graph Connector (SGC) with an existing ETL.</p>
<section class="section prereq" id="deploy-a-new-service-graph-connector-with-duplicated-etl__task-prereq"><div class="tasklabel"><p class="sectiontitle tasklabel">Before you begin</p></div>
<p class="p">Role required: admin</p>
<p class="p">Ensure the required Service Graph Connector plugin is activated.</p>
</section>
<section><div class="tasklabel"><p class="sectiontitle tasklabel">Procedure</p></div><ol class="ol steps"><li class="li step">
<span class="ph cmd">Navigate to <span class="ph menucascade"><span class="ph uicontrol">All</span><abbr> > </abbr><span class="ph uicontrol">IntegrationHub ETL</span></span>.</span>
</li><li class="li step">
<span class="ph cmd">Open the duplicated ETL configuration.</span>
</li><li class="li step">
<span class="ph cmd">Select the data source of the service graph connector and click <span class="ph uicontrol">Save</span>.</span>
</li><li class="li step">
<span class="ph cmd">Select <span class="ph uicontrol">Import Schedules</span> to execute the ETL to transform and load the data from the new SGC.</span>
</li><li class="li step">
<span class="ph cmd">Monitor execution status.</span>
</li></ol></section>
<section class="section result" id="deploy-a-new-service-graph-connector-with-duplicated-etl__result_gm2_xny_pfc"><div class="tasklabel"><p class="sectiontitle tasklabel">Result</p></div>
<p class="p">Verify that CI records and relationships are created in the CMDB using CMDB Maps or list views.</p>
</section>
</div>
</article></main></body></article> | {
"attachments": {
"all_attachments": null,
"topic_attachments": []
},
"available_languages": [
"enus"
],
"breadcrumbs": [
{
"title": "Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html"
},
{
"title": "Configuring Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/configuring-tsom.html"
},
{
"title": "Set up Telecom Visibility",
"topic_id": "product/tmt-telecom-service-operations-mgt/task/configuring-tsom-visibility.html"
},
{
"title": "Configuring the Telecom Discovery Builder framework ETL in a connector",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/configuring-the-telco-generic-schema-etl.html"
}
],
"breadcrumbs_html": "<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops\">Zurich Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html\">Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/configuring-tsom.html\">Configuring Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/configuring-tsom-visibility.html\">Set up Telecom Visibility</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/configuring-the-telco-generic-schema-etl.html\">Configuring the Telecom Discovery Builder framework ETL in a connector</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<span class=\"active\">Deploy a new service graph connector with existing ETL</span>",
"bundle_id": "zurich-telecom-service-ops",
"bundle_key": 2733,
"bundle_landing_page": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html",
"bundle_subtitle": null,
"bundle_title": "Zurich Telecommunications Service Operations Management",
"canonical_link": null,
"dates": {
"Added on": "2025-08-02T00:48:08.794016Z",
"Created on": "2025-04-14T00:00:00Z",
"Initial upload": "2025-07-30T22:24:33.519043Z",
"Updated on": "2025-07-31T00:00:00Z"
},
"dislike_url": "https://servicenow-be-prod.servicenow.com/dislike/55686974",
"dislikes": 0,
"es_archived_content": false,
"is_in_fav": false,
"is_liked": null,
"is_watched": false,
"keywords": [
" zurich zurich"
],
"labels": [
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "zurich",
"navtitle": "Zurich",
"outputclasses": [],
"subjectHeadId": "versions",
"subjectheadNavtitle": "Versions",
"visibility": "show-facet"
},
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "tsom",
"navtitle": "Telecommunications Service Operations Management",
"outputclasses": [],
"subjectHeadId": "products",
"subjectheadNavtitle": "Products",
"visibility": "show-facet"
}
],
"labels_text": "Versions > Zurich; Products > CRM and Industry Products > Telecommunications Media and Technology Assurance > Telecommunications Service Operations Management",
"like_url": "https://servicenow-be-prod.servicenow.com/like/55686974",
"likes": 0,
"metadata": {
"AI Search": null,
"AI Search Assist": null,
"Application Insights": null,
"Capabilities": null,
"Code Signing": null,
"Contextual Search": null,
"DC.contributor": null,
"DC.coverage": null,
"DC.creator": "ServiceNow",
"DC.date.created": "2025-04-14T15:44:18+05:30",
"DC.date.modified": "2025-07-31",
"DC.format": "HTML5",
"DC.identifier": "deploy-a-new-service-graph-connector-with-duplicated-etl",
"DC.language": null,
"DC.relation": null,
"DC.rights.owner": "(C) Copyright 2025",
"DC.subject": null,
"DC.type": "task",
"Data Discovery": null,
"Data Policy": null,
"Data Privacy": null,
"Discovery": null,
"External Content for AI Search": null,
"Field Administration": null,
"Field Normalization": null,
"Key Management Framework": null,
"Localization Framework": null,
"Now Platform": null,
"PlatSec": null,
"Platform": null,
"Platform Administration": null,
"Platform Performance": null,
"Platform Privacy": null,
"Proactive Triggers": null,
"Process Optimization": null,
"RN doc editing record number": null,
"Search Administration": null,
"Secrets Management": null,
"ServiceNow AI Platform": null,
"State Model": null,
"Subscription Management": null,
"Task Communications Management": null,
"Timeline Visualizations": null,
"User Administration": null,
"User Experience Analytics": null,
"Zing": null,
"ai-now-assist": null,
"app-name": null,
"app_route": null,
"azureapimanagemen": null,
"change-completed": null,
"change-item": null,
"change-request-id": null,
"change-request-reference": null,
"com.glide.embedded_help.category": null,
"component": null,
"copyright": "(C) Copyright 2025",
"crossroads": null,
"data": null,
"description": "Associate a new Service Graph Connector (SGC) with an existing ETL.",
"dominant_bundle": null,
"erp-canvas-video": null,
"fsm-mobile": null,
"fsm-route": null,
"fsm-sched-opt": null,
"fsm-wrk-order": null,
"genai-round-7": null,
"generator": "DITA-OT",
"glossPartOfSpeech": null,
"glossStatus": null,
"guided setup": null,
"guided tours": null,
"keywords": null,
"min-toc": null,
"mini": null,
"mini-to truec": null,
"mini-toc": null,
"mini_toc": null,
"minitoc": null,
"modification": null,
"now-assist-app-gen-video": null,
"order": null,
"page-type": null,
"page-type ": null,
"prodname": null,
"product": null,
"product_name": null,
"release": null,
"resourceID": null,
"roles": null,
"route_page": null,
"route_params_listId": null,
"route_params_table": null,
"route_params_type": null,
"route_type": null,
"setconfigurationproperties": null,
"topic": null,
"translation-type": "source",
"version": null,
"workflow": "Customer and Industry",
"workplace-srvc-delvry-ditamap": null
},
"page_id": "product/tmt-telecom-service-operations-mgt/task/deploy-a-new-service-graph-connector-with-duplicated-etl.html",
"page_key": 55686974,
"preprocessed_PDF": "https://downloads.docs.servicenow.com/pdf/enus/servicenow-zurich-telecom-service-ops-enus.pdf",
"rating": null,
"read_time_data": {
"char_count": 550,
"img_count": 0,
"read_time": 1,
"video_links": [
""
],
"word_count": 90
},
"related_links": [],
"search_title": null,
"title": "Deploy a new service graph connector with existing ETL",
"topic_cluster": {
"clustered_by": {
"enabled": true,
"primary_key": "versions",
"primary_sort": "top-down",
"type": "subjecthead"
},
"clustered_labels": [
"versions"
],
"clustered_topics": [],
"clustering_title": "Zurich"
},
"topic_html": "<article class=\"hascomments\" data-page=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/deploy-a-new-service-graph-connector-with-duplicated-etl.html\" id=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/deploy-a-new-service-graph-connector-with-duplicated-etl.html\"><body id=\"deploy-a-new-service-graph-connector-with-duplicated-etl\"><main role=\"main\"><article role=\"article\" class=\"dita\" id=\"deploy-a-new-service-graph-connector-with-duplicated-etl\" aria-labelledby=\"title_deploy-a-new-service-graph-connector-with-duplicated-etl\">\n <h1 class=\"title topictitle1\" id=\"title_deploy-a-new-service-graph-connector-with-duplicated-etl\">Deploy a new service graph connector with existing ETL</h1>\n \n \n <div class=\"body taskbody\"><p class=\"shortdesc\">Associate a new Service Graph Connector (SGC) with an existing ETL.</p>\n <section class=\"section prereq\" id=\"deploy-a-new-service-graph-connector-with-duplicated-etl__task-prereq\"><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">Before you begin</p></div>\n <p class=\"p\">Role required: admin</p>\n <p class=\"p\">Ensure the required Service Graph Connector plugin is activated.</p>\n </section>\n <section><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">Procedure</p></div><ol class=\"ol steps\"><li class=\"li step\">\n <span class=\"ph cmd\">Navigate to <span class=\"ph menucascade\"><span class=\"ph uicontrol\">All</span><abbr> > </abbr><span class=\"ph uicontrol\">IntegrationHub ETL</span></span>.</span>\n </li><li class=\"li step\">\n <span class=\"ph cmd\">Open the duplicated ETL configuration.</span>\n </li><li class=\"li step\">\n <span class=\"ph cmd\">Select the data source of the service graph connector and click <span class=\"ph uicontrol\">Save</span>.</span>\n </li><li class=\"li step\">\n <span class=\"ph cmd\">Select <span class=\"ph uicontrol\">Import Schedules</span> to execute the ETL to transform and load the data from the new SGC.</span>\n </li><li class=\"li step\">\n <span class=\"ph cmd\">Monitor execution status.</span>\n </li></ol></section>\n <section class=\"section result\" id=\"deploy-a-new-service-graph-connector-with-duplicated-etl__result_gm2_xny_pfc\"><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">Result</p></div>\n <p class=\"p\">Verify that CI records and relationships are created in the CMDB using CMDB Maps or list views.</p>\n </section>\n </div>\n</article></main></body></article>",
"topic_language": "enus",
"views": 0,
"your_rating": null
} | # Deploy a new service graph connector with existing ETL
Associate a new Service Graph Connector (SGC) with an existing ETL.
## Before you begin
Role required: admin
Ensure the required Service Graph Connector plugin is activated.
## Procedure
1. Navigate to All > IntegrationHub ETL.
2. Open the duplicated ETL configuration.
3. Select the data source of the service graph connector and click Save.
4. Select Import Schedules to execute the ETL to transform and load the data from the new SGC.
5. Monitor execution status.
### Result
Verify that CI records and relationships are created in the CMDB using CMDB Maps or list views.
| ---
title: Deploy a new service graph connector with existing ETL
description: Associate a new Service Graph Connector (SGC) with an existing ETL.
keywords: []
breadcrumbs:
- Telecommunications Service Operations Management
- Configuring Telecommunications Service Operations Management
- Set up Telecom Visibility
- Configuring the Telecom Discovery Builder framework ETL in a connector
---
# Deploy a new service graph connector with existing ETL
Associate a new Service Graph Connector (SGC) with an existing ETL.
## Before you begin
Role required: admin
Ensure the required Service Graph Connector plugin is activated.
## Procedure
1. Navigate to All > IntegrationHub ETL.
2. Open the duplicated ETL configuration.
3. Select the data source of the service graph connector and click Save.
4. Select Import Schedules to execute the ETL to transform and load the data from the new SGC.
5. Monitor execution status.
### Result
Verify that CI records and relationships are created in the CMDB using CMDB Maps or list views.
|
https://www.servicenow.com/docs/en-US/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/duplicate-the-generic-etl-to-use-a-specific-connector.html | https://servicenow-be-prod.servicenow.com/api/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/duplicate-the-generic-etl-to-use-a-specific-connector.html | 2025-08-02 | daily | 0.5 | 268.xml | en-US | zurich-telecom-service-ops | product/tmt-telecom-service-operations-mgt/task/duplicate-the-generic-etl-to-use-a-specific-connector.html | zurich | Duplicate the Telecom Discovery Builder framework ETL into a connector scope | The Telecom Discovery Builder framework ETL enables Service Graph Connector (SGC) teams to rapidly adopt a standardized, schema-compliant data ingestion pipeline without building ETL logic from scratch. | [] | [
"Telecommunications Service Operations Management",
"Configuring Telecommunications Service Operations Management",
"Set up Telecom Visibility",
"Configuring the Telecom Discovery Builder framework ETL in a connector"
] | <article class="hascomments" data-page="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/duplicate-the-generic-etl-to-use-a-specific-connector.html" id="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/duplicate-the-generic-etl-to-use-a-specific-connector.html"><body id="duplicate-the-generic-etl-to-use-a-specific-connector"><main role="main"><article role="article" class="dita" id="duplicate-the-generic-etl-to-use-a-specific-connector" aria-labelledby="title_duplicate-the-generic-etl-to-use-a-specific-connector">
<h1 class="title topictitle1" id="title_duplicate-the-generic-etl-to-use-a-specific-connector">Duplicate the Telecom Discovery Builder framework ETL into a connector scope</h1>
<div class="body taskbody"><p class="shortdesc">The Telecom Discovery Builder framework ETL enables Service Graph Connector (SGC) teams to rapidly adopt a standardized, schema-compliant data ingestion pipeline without building ETL logic from scratch.</p>
<section class="section prereq" id="duplicate-the-generic-etl-to-use-a-specific-connector__task-prereq"><div class="tasklabel"><p class="sectiontitle tasklabel">Before you begin</p></div>
<p class="p">Role required: admin</p>
<div class="p">Ensure that:<ul class="ul" id="duplicate-the-generic-etl-to-use-a-specific-connector__ul_kds_hpy_dfc">
<li class="li">The Telecom Core plugin is activated and the Telco Generic ETL v2 (automatically installed) is available.</li>
<li class="li">You have admin access to IntegrationHub ETL Studio.</li>
<li class="li">You have created a temporary data source in the connector’s application scope. After creating a temporary data source, you can duplicate the Generic ETL into your connector’s application scope to customize and extend
it for your specific use case.</li>
</ul></div>
</section>
<section class="section context" id="duplicate-the-generic-etl-to-use-a-specific-connector__context_qzw_2py_dfc"><div class="tasklabel"><p class="sectiontitle tasklabel">About this task</p></div>
<div class="p">Duplicating the Telco Generic ETL allows you to:<ul class="ul" id="duplicate-the-generic-etl-to-use-a-specific-connector__ul_yqs_fpy_dfc">
<li class="li">Reuse standardized ETL mappings across multiple connectors.</li>
<li class="li">Customize ETL behavior without altering the original baseline provided by the Telecom Service Operations Management (TSOM) Core.</li>
<li class="li">Align with the Telco Generic Schema for consistency and TNI compliance.</li>
<li class="li">Save time and reduce errors by working with a tested and proven ETL framework.</li>
</ul></div>
<p class="p">The following screenshot can help you duplicate the ETL Transform Map.<img src="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/../images/createduplicate.png?_LANG=enus" class="image" id="duplicate-the-generic-etl-to-use-a-specific-connector__image_ekz_qcw_vfc" alt="Duplicate ETL Transform Map user interface displaying field information to duplicate the Telco Generic Schema V2 to Nokia NSP ETL."/></p>
</section>
<section><div class="tasklabel"><p class="sectiontitle tasklabel">Procedure</p></div><ol class="ol steps"><li class="li step stepexpand">
<span class="ph cmd">Navigate to <span class="ph menucascade"><span class="ph uicontrol">All</span><abbr> > </abbr><span class="ph uicontrol">IntegrationHub ETL</span></span>.</span>
</li><li class="li step stepexpand">
<span class="ph cmd">On the <span class="ph uicontrol">IntegrationHub ETL</span> page, select the connector's application scope.</span>
<div class="itemgroup info">
<div class="note note note_note"><span class="note__title">Note:</span> For example, <span class="ph uicontrol">Service Graph Connector for Nokia NSP</span>.</div>
</div>
</li><li class="li step stepexpand">
<span class="ph cmd">Expand the CMDB Application Telco Generic Schema and select <span class="ph uicontrol">Telco Generic Schema</span> record.</span>
</li><li class="li step stepexpand">
<span class="ph cmd">Click <span class="ph uicontrol">Duplicate</span>.</span>
<div class="itemgroup stepresult">The Duplicate ETL Transform Map page appears.</div>
</li><li class="li step stepexpand">
<span class="ph cmd">Configure the duplicated ETL transform map</span>
<ol type="a" class="ol substeps" id="duplicate-the-generic-etl-to-use-a-specific-connector__substeps_gsf_5ty_dfc">
<li class="li substep substepexpand">
<span class="ph cmd">In the <span class="ph uicontrol">Duplicate From</span> field, ensure Telco Generic Schema is selected.</span>
</li>
<li class="li substep substepexpand">
<span class="ph cmd">Select an existing CMDB Application or click <span class="ph uicontrol">Add new...</span> to add a new CMDB Application.</span>
</li>
<li class="li substep substepexpand">
<span class="ph cmd">For a new CMDB Application, enter the CMDB application name (for example, Nokia NSP Generic ETL v2)</span>
</li>
<li class="li substep substepexpand">
<span class="ph cmd">In the <span class="ph uicontrol">Discovery Source</span> field, select the import set.</span>
</li>
<li class="li substep substepexpand">
<span class="ph cmd">In the <span class="ph uicontrol">Name</span> field, enter a name for the duplicate ETL.</span>
</li>
<li class="li substep substepexpand">
<span class="ph cmd">In the <span class="ph uicontrol">Description</span> field, enter a description for the duplicate ETL.</span>
</li>
<li class="li substep substepexpand">
<span class="ph cmd">Select the data source that is used for the duplicate ETL transform map.</span>
<div class="itemgroup info">
<div class="note note note_note"><span class="note__title">Note:</span> This needs to be different than the existing default Data Source that is attached to the Telco Generic Schema ETL. For more information, see <a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/task/create-a-data-source-similar-to-tsom-core-data-source.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/create-a-data-source-similar-to-tsom-core-data-source.html" class="xref" title="Set up a schema-compliant data source in the connector’s application scope to simulate telecom data and ensure successful testing and validation of the Telecom Discovery Builder framework ETL before integrating with live device data.">Create a data source similar to Telecom core data source</a>.</div>
</div>
</li>
<li class="li substep substepexpand">
<span class="ph cmd">Enable <span class="ph uicontrol">Auto-pull a new import set</span> option to automatically pull data into a new import set.</span>
</li>
<li class="li substep substepexpand">
<span class="ph cmd">In the <span class="ph uicontrol">Preview Size Override</span> field, set a custom preview size for testing and validation.</span>
</li>
</ol>
</li><li class="li step stepexpand">
<span class="ph cmd">Select <span class="ph uicontrol">Create Duplicate</span>.</span>
<div class="itemgroup stepresult">A duplicate ETL of Telco Generic ETL is created.</div>
</li><li class="li step stepexpand">(Optional)
<span class="ph cmd">Open the duplicated ETL record and review the mappings and settings.</span>
</li></ol></section>
<section class="section postreq" id="duplicate-the-generic-etl-to-use-a-specific-connector__postreq_n5m_nvy_dfc"><div class="tasklabel"><p class="sectiontitle tasklabel">What to do next</p></div>
<div class="p">
<ol class="ol" id="duplicate-the-generic-etl-to-use-a-specific-connector__ol_gwp_lxy_dfc">
<li class="li">Test the duplicated ETL (optional but recommended):<ul class="ul" id="duplicate-the-generic-etl-to-use-a-specific-connector__ul_smf_4vy_dfc">
<li class="li">Run a test load or a simulation using the temporary data source.</li>
<li class="li">Verify that import sets are processed successfully, CIs are created according to the Telco Generic Schema, and relationships are established properly.</li>
</ul></li>
<li class="li">After successful duplication and testing:<ul class="ul" id="duplicate-the-generic-etl-to-use-a-specific-connector__ul_iff_pxy_dfc">
<li class="li">Update the ETL’s data source configuration to point to the actual production data source (for real device data).</li>
<li class="li">Deploy the connector integration into a test or production environment.</li>
<li class="li">Monitor import runs to validate that inventory data is ingested into the CMDB correctly.</li>
</ul></li>
</ol>
</div>
</section>
</div>
<nav role="navigation"></nav><nav role="navigation" class="tasksNavigation"></nav><nav role="navigation" class="related-links"><div class="col-md-4"><dt>Related tasks</dt><dd><ul><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/task/update-data-source-of-the-connector.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/update-data-source-of-the-connector.html" class="link" title="Link the duplicated ETL to a valid data source for your specific connector.">Update the data source of the connector</a></li></ul></dd></div></nav>
</article></main></body></article> | {
"attachments": {
"all_attachments": null,
"topic_attachments": []
},
"available_languages": [
"enus"
],
"breadcrumbs": [
{
"title": "Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html"
},
{
"title": "Configuring Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/configuring-tsom.html"
},
{
"title": "Set up Telecom Visibility",
"topic_id": "product/tmt-telecom-service-operations-mgt/task/configuring-tsom-visibility.html"
},
{
"title": "Configuring the Telecom Discovery Builder framework ETL in a connector",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/configuring-the-telco-generic-schema-etl.html"
}
],
"breadcrumbs_html": "<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops\">Zurich Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html\">Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/configuring-tsom.html\">Configuring Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/configuring-tsom-visibility.html\">Set up Telecom Visibility</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/configuring-the-telco-generic-schema-etl.html\">Configuring the Telecom Discovery Builder framework ETL in a connector</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<span class=\"active\">Duplicate the Telecom Discovery Builder framework ETL into a connector scope</span>",
"bundle_id": "zurich-telecom-service-ops",
"bundle_key": 2733,
"bundle_landing_page": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html",
"bundle_subtitle": null,
"bundle_title": "Zurich Telecommunications Service Operations Management",
"canonical_link": null,
"dates": {
"Added on": "2025-08-02T00:48:08.794016Z",
"Created on": "2025-04-14T00:00:00Z",
"Initial upload": "2025-07-30T22:24:33.519043Z",
"Updated on": "2025-07-31T00:00:00Z"
},
"dislike_url": "https://servicenow-be-prod.servicenow.com/dislike/55686975",
"dislikes": 0,
"es_archived_content": false,
"is_in_fav": false,
"is_liked": null,
"is_watched": false,
"keywords": [
" zurich zurich"
],
"labels": [
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "zurich",
"navtitle": "Zurich",
"outputclasses": [],
"subjectHeadId": "versions",
"subjectheadNavtitle": "Versions",
"visibility": "show-facet"
},
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "tsom",
"navtitle": "Telecommunications Service Operations Management",
"outputclasses": [],
"subjectHeadId": "products",
"subjectheadNavtitle": "Products",
"visibility": "show-facet"
}
],
"labels_text": "Versions > Zurich; Products > CRM and Industry Products > Telecommunications Media and Technology Assurance > Telecommunications Service Operations Management",
"like_url": "https://servicenow-be-prod.servicenow.com/like/55686975",
"likes": 0,
"metadata": {
"AI Search": null,
"AI Search Assist": null,
"Application Insights": null,
"Capabilities": null,
"Code Signing": null,
"Contextual Search": null,
"DC.contributor": null,
"DC.coverage": null,
"DC.creator": "ServiceNow",
"DC.date.created": "2025-04-14T13:35:15+05:30",
"DC.date.modified": "2025-07-31",
"DC.format": "HTML5",
"DC.identifier": "duplicate-the-generic-etl-to-use-a-specific-connector",
"DC.language": null,
"DC.relation": "update-data-source-of-the-connector.html",
"DC.rights.owner": "(C) Copyright 2025",
"DC.subject": null,
"DC.type": "task",
"Data Discovery": null,
"Data Policy": null,
"Data Privacy": null,
"Discovery": null,
"External Content for AI Search": null,
"Field Administration": null,
"Field Normalization": null,
"Key Management Framework": null,
"Localization Framework": null,
"Now Platform": null,
"PlatSec": null,
"Platform": null,
"Platform Administration": null,
"Platform Performance": null,
"Platform Privacy": null,
"Proactive Triggers": null,
"Process Optimization": null,
"RN doc editing record number": null,
"Search Administration": null,
"Secrets Management": null,
"ServiceNow AI Platform": null,
"State Model": null,
"Subscription Management": null,
"Task Communications Management": null,
"Timeline Visualizations": null,
"User Administration": null,
"User Experience Analytics": null,
"Zing": null,
"ai-now-assist": null,
"app-name": null,
"app_route": null,
"azureapimanagemen": null,
"change-completed": null,
"change-item": null,
"change-request-id": null,
"change-request-reference": null,
"com.glide.embedded_help.category": null,
"component": null,
"copyright": "(C) Copyright 2025",
"crossroads": null,
"data": null,
"description": "The Telecom Discovery Builder framework ETL enables Service Graph Connector (SGC) teams to rapidly adopt a standardized, schema-compliant data ingestion pipeline without building ETL logic from scratch.",
"dominant_bundle": null,
"erp-canvas-video": null,
"fsm-mobile": null,
"fsm-route": null,
"fsm-sched-opt": null,
"fsm-wrk-order": null,
"genai-round-7": null,
"generator": "DITA-OT",
"glossPartOfSpeech": null,
"glossStatus": null,
"guided setup": null,
"guided tours": null,
"keywords": null,
"min-toc": null,
"mini": null,
"mini-to truec": null,
"mini-toc": null,
"mini_toc": null,
"minitoc": null,
"modification": null,
"now-assist-app-gen-video": null,
"order": null,
"page-type": null,
"page-type ": null,
"prodname": null,
"product": null,
"product_name": null,
"release": null,
"resourceID": null,
"roles": null,
"route_page": null,
"route_params_listId": null,
"route_params_table": null,
"route_params_type": null,
"route_type": null,
"setconfigurationproperties": null,
"topic": null,
"translation-type": "source",
"version": null,
"workflow": "Customer and Industry",
"workplace-srvc-delvry-ditamap": null
},
"page_id": "product/tmt-telecom-service-operations-mgt/task/duplicate-the-generic-etl-to-use-a-specific-connector.html",
"page_key": 55686975,
"preprocessed_PDF": "https://downloads.docs.servicenow.com/pdf/enus/servicenow-zurich-telecom-service-ops-enus.pdf",
"rating": null,
"read_time_data": {
"char_count": 3187,
"img_count": 1,
"read_time": 3,
"video_links": [
""
],
"word_count": 496
},
"related_links": [
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "Link the duplicated ETL to a valid data source for your specific connector.",
"title": "Update the data source of the connector",
"topic": "/product/tmt-telecom-service-operations-mgt/task/update-data-source-of-the-connector.html",
"type": "task",
"url": null
}
],
"search_title": null,
"title": "Duplicate the Telecom Discovery Builder framework ETL into a connector scope",
"topic_cluster": {
"clustered_by": {
"enabled": true,
"primary_key": "versions",
"primary_sort": "top-down",
"type": "subjecthead"
},
"clustered_labels": [
"versions"
],
"clustered_topics": [],
"clustering_title": "Zurich"
},
"topic_html": "<article class=\"hascomments\" data-page=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/duplicate-the-generic-etl-to-use-a-specific-connector.html\" id=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/duplicate-the-generic-etl-to-use-a-specific-connector.html\"><body id=\"duplicate-the-generic-etl-to-use-a-specific-connector\"><main role=\"main\"><article role=\"article\" class=\"dita\" id=\"duplicate-the-generic-etl-to-use-a-specific-connector\" aria-labelledby=\"title_duplicate-the-generic-etl-to-use-a-specific-connector\">\n <h1 class=\"title topictitle1\" id=\"title_duplicate-the-generic-etl-to-use-a-specific-connector\">Duplicate the Telecom Discovery Builder framework ETL into a connector scope</h1>\n \n \n <div class=\"body taskbody\"><p class=\"shortdesc\">The Telecom Discovery Builder framework ETL enables Service Graph Connector (SGC) teams to rapidly adopt a standardized, schema-compliant data ingestion pipeline without building ETL logic from scratch.</p>\n <section class=\"section prereq\" id=\"duplicate-the-generic-etl-to-use-a-specific-connector__task-prereq\"><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">Before you begin</p></div>\n <p class=\"p\">Role required: admin</p>\n <div class=\"p\">Ensure that:<ul class=\"ul\" id=\"duplicate-the-generic-etl-to-use-a-specific-connector__ul_kds_hpy_dfc\">\n <li class=\"li\">The Telecom Core plugin is activated and the Telco Generic ETL v2 (automatically installed) is available.</li>\n <li class=\"li\">You have admin access to IntegrationHub ETL Studio.</li>\n <li class=\"li\">You have created a temporary data source in the connector’s application scope. After creating a temporary data source, you can duplicate the Generic ETL into your connector’s application scope to customize and extend\n it for your specific use case.</li>\n </ul></div>\n </section>\n <section class=\"section context\" id=\"duplicate-the-generic-etl-to-use-a-specific-connector__context_qzw_2py_dfc\"><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">About this task</p></div>\n <div class=\"p\">Duplicating the Telco Generic ETL allows you to:<ul class=\"ul\" id=\"duplicate-the-generic-etl-to-use-a-specific-connector__ul_yqs_fpy_dfc\">\n <li class=\"li\">Reuse standardized ETL mappings across multiple connectors.</li>\n <li class=\"li\">Customize ETL behavior without altering the original baseline provided by the Telecom Service Operations Management (TSOM) Core.</li>\n <li class=\"li\">Align with the Telco Generic Schema for consistency and TNI compliance.</li>\n <li class=\"li\">Save time and reduce errors by working with a tested and proven ETL framework.</li>\n </ul></div>\n <p class=\"p\">The following screenshot can help you duplicate the ETL Transform Map.<img src=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/../images/createduplicate.png?_LANG=enus\" class=\"image\" id=\"duplicate-the-generic-etl-to-use-a-specific-connector__image_ekz_qcw_vfc\" alt=\"Duplicate ETL Transform Map user interface displaying field information to duplicate the Telco Generic Schema V2 to Nokia NSP ETL.\"/></p>\n </section>\n <section><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">Procedure</p></div><ol class=\"ol steps\"><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">Navigate to <span class=\"ph menucascade\"><span class=\"ph uicontrol\">All</span><abbr> > </abbr><span class=\"ph uicontrol\">IntegrationHub ETL</span></span>.</span>\n </li><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">On the <span class=\"ph uicontrol\">IntegrationHub ETL</span> page, select the connector's application scope.</span>\n <div class=\"itemgroup info\">\n <div class=\"note note note_note\"><span class=\"note__title\">Note:</span> For example, <span class=\"ph uicontrol\">Service Graph Connector for Nokia NSP</span>.</div>\n </div>\n </li><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">Expand the CMDB Application Telco Generic Schema and select <span class=\"ph uicontrol\">Telco Generic Schema</span> record.</span>\n </li><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">Click <span class=\"ph uicontrol\">Duplicate</span>.</span>\n <div class=\"itemgroup stepresult\">The Duplicate ETL Transform Map page appears.</div>\n </li><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">Configure the duplicated ETL transform map</span>\n <ol type=\"a\" class=\"ol substeps\" id=\"duplicate-the-generic-etl-to-use-a-specific-connector__substeps_gsf_5ty_dfc\">\n <li class=\"li substep substepexpand\">\n <span class=\"ph cmd\">In the <span class=\"ph uicontrol\">Duplicate From</span> field, ensure Telco Generic Schema is selected.</span>\n </li>\n <li class=\"li substep substepexpand\">\n <span class=\"ph cmd\">Select an existing CMDB Application or click <span class=\"ph uicontrol\">Add new...</span> to add a new CMDB Application.</span>\n </li>\n <li class=\"li substep substepexpand\">\n <span class=\"ph cmd\">For a new CMDB Application, enter the CMDB application name (for example, Nokia NSP Generic ETL v2)</span>\n </li>\n <li class=\"li substep substepexpand\">\n <span class=\"ph cmd\">In the <span class=\"ph uicontrol\">Discovery Source</span> field, select the import set.</span>\n </li>\n <li class=\"li substep substepexpand\">\n <span class=\"ph cmd\">In the <span class=\"ph uicontrol\">Name</span> field, enter a name for the duplicate ETL.</span>\n </li>\n <li class=\"li substep substepexpand\">\n <span class=\"ph cmd\">In the <span class=\"ph uicontrol\">Description</span> field, enter a description for the duplicate ETL.</span>\n </li>\n <li class=\"li substep substepexpand\">\n <span class=\"ph cmd\">Select the data source that is used for the duplicate ETL transform map.</span>\n <div class=\"itemgroup info\">\n <div class=\"note note note_note\"><span class=\"note__title\">Note:</span> This needs to be different than the existing default Data Source that is attached to the Telco Generic Schema ETL. For more information, see <a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/task/create-a-data-source-similar-to-tsom-core-data-source.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/create-a-data-source-similar-to-tsom-core-data-source.html\" class=\"xref\" title=\"Set up a schema-compliant data source in the connector’s application scope to simulate telecom data and ensure successful testing and validation of the Telecom Discovery Builder framework ETL before integrating with live device data.\">Create a data source similar to Telecom core data source</a>.</div>\n </div>\n </li>\n <li class=\"li substep substepexpand\">\n <span class=\"ph cmd\">Enable <span class=\"ph uicontrol\">Auto-pull a new import set</span> option to automatically pull data into a new import set.</span>\n </li>\n <li class=\"li substep substepexpand\">\n <span class=\"ph cmd\">In the <span class=\"ph uicontrol\">Preview Size Override</span> field, set a custom preview size for testing and validation.</span>\n </li>\n </ol>\n </li><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">Select <span class=\"ph uicontrol\">Create Duplicate</span>.</span>\n <div class=\"itemgroup stepresult\">A duplicate ETL of Telco Generic ETL is created.</div>\n </li><li class=\"li step stepexpand\">(Optional) \n <span class=\"ph cmd\">Open the duplicated ETL record and review the mappings and settings.</span>\n </li></ol></section>\n <section class=\"section postreq\" id=\"duplicate-the-generic-etl-to-use-a-specific-connector__postreq_n5m_nvy_dfc\"><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">What to do next</p></div>\n <div class=\"p\">\n <ol class=\"ol\" id=\"duplicate-the-generic-etl-to-use-a-specific-connector__ol_gwp_lxy_dfc\">\n <li class=\"li\">Test the duplicated ETL (optional but recommended):<ul class=\"ul\" id=\"duplicate-the-generic-etl-to-use-a-specific-connector__ul_smf_4vy_dfc\">\n <li class=\"li\">Run a test load or a simulation using the temporary data source.</li>\n <li class=\"li\">Verify that import sets are processed successfully, CIs are created according to the Telco Generic Schema, and relationships are established properly.</li>\n </ul></li>\n <li class=\"li\">After successful duplication and testing:<ul class=\"ul\" id=\"duplicate-the-generic-etl-to-use-a-specific-connector__ul_iff_pxy_dfc\">\n <li class=\"li\">Update the ETL’s data source configuration to point to the actual production data source (for real device data).</li>\n <li class=\"li\">Deploy the connector integration into a test or production environment.</li>\n <li class=\"li\">Monitor import runs to validate that inventory data is ingested into the CMDB correctly.</li>\n </ul></li>\n </ol>\n </div>\n </section>\n </div>\n <nav role=\"navigation\"></nav><nav role=\"navigation\" class=\"tasksNavigation\"></nav><nav role=\"navigation\" class=\"related-links\"><div class=\"col-md-4\"><dt>Related tasks</dt><dd><ul><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/task/update-data-source-of-the-connector.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/update-data-source-of-the-connector.html\" class=\"link\" title=\"Link the duplicated ETL to a valid data source for your specific connector.\">Update the data source of the connector</a></li></ul></dd></div></nav>\n</article></main></body></article>",
"topic_language": "enus",
"views": 0,
"your_rating": null
} | # Duplicate the Telecom Discovery Builder framework ETL into a connector scope
The Telecom Discovery Builder framework ETL enables Service Graph Connector (SGC) teams to rapidly adopt a standardized, schema-compliant data ingestion pipeline without building ETL logic from scratch.
## Before you begin
Role required: admin
Ensure that:
* The Telecom Core plugin is activated and the Telco Generic ETL v2 (automatically installed) is available.
* You have admin access to IntegrationHub ETL Studio.
* You have created a temporary data source in the connector’s application scope. After creating a temporary data source, you can duplicate the Generic ETL into your connector’s application scope to customize and extend
it for your specific use case.
## About this task
Duplicating the Telco Generic ETL allows you to:
* Reuse standardized ETL mappings across multiple connectors.
* Customize ETL behavior without altering the original baseline provided by the Telecom Service Operations Management (TSOM) Core.
* Align with the Telco Generic Schema for consistency and TNI compliance.
* Save time and reduce errors by working with a tested and proven ETL framework.
The following screenshot can help you duplicate the ETL Transform Map.
## Procedure
1. Navigate to All > IntegrationHub ETL.
2. On the IntegrationHub ETL page, select the connector's application scope.
Note: For example, Service Graph Connector for Nokia NSP.
3. Expand the CMDB Application Telco Generic Schema and select Telco Generic Schema record.
4. Click Duplicate.
The Duplicate ETL Transform Map page appears.
5. Configure the duplicated ETL transform map
1. In the Duplicate From field, ensure Telco Generic Schema is selected.
2. Select an existing CMDB Application or click Add new... to add a new CMDB Application.
3. For a new CMDB Application, enter the CMDB application name (for example, Nokia NSP Generic ETL v2)
4. In the Discovery Source field, select the import set.
5. In the Name field, enter a name for the duplicate ETL.
6. In the Description field, enter a description for the duplicate ETL.
7. Select the data source that is used for the duplicate ETL transform map.
Note: This needs to be different than the existing default Data Source that is attached to the Telco Generic Schema ETL. For more information, see Create a data source similar to Telecom core data source.
8. Enable Auto-pull a new import set option to automatically pull data into a new import set.
9. In the Preview Size Override field, set a custom preview size for testing and validation.
6. Select Create Duplicate.
A duplicate ETL of Telco Generic ETL is created.
7. (Optional)
Open the duplicated ETL record and review the mappings and settings.
### What to do next
1. Test the duplicated ETL (optional but recommended):
* Run a test load or a simulation using the temporary data source.
* Verify that import sets are processed successfully, CIs are created according to the Telco Generic Schema, and relationships are established properly.
2. After successful duplication and testing:
* Update the ETL’s data source configuration to point to the actual production data source (for real device data).
* Deploy the connector integration into a test or production environment.
* Monitor import runs to validate that inventory data is ingested into the CMDB correctly.
| ---
title: Duplicate the Telecom Discovery Builder framework ETL into a connector scope
description: The Telecom Discovery Builder framework ETL enables Service Graph Connector
(SGC) teams to rapidly adopt a standardized, schema-compliant data ingestion pipeline
without building ETL logic from scratch.
keywords: []
breadcrumbs:
- Telecommunications Service Operations Management
- Configuring Telecommunications Service Operations Management
- Set up Telecom Visibility
- Configuring the Telecom Discovery Builder framework ETL in a connector
---
# Duplicate the Telecom Discovery Builder framework ETL into a connector scope
The Telecom Discovery Builder framework ETL enables Service Graph Connector (SGC) teams to rapidly adopt a standardized, schema-compliant data ingestion pipeline without building ETL logic from scratch.
## Before you begin
Role required: admin
Ensure that:
* The Telecom Core plugin is activated and the Telco Generic ETL v2 (automatically installed) is available.
* You have admin access to IntegrationHub ETL Studio.
* You have created a temporary data source in the connector’s application scope. After creating a temporary data source, you can duplicate the Generic ETL into your connector’s application scope to customize and extend
it for your specific use case.
## About this task
Duplicating the Telco Generic ETL allows you to:
* Reuse standardized ETL mappings across multiple connectors.
* Customize ETL behavior without altering the original baseline provided by the Telecom Service Operations Management (TSOM) Core.
* Align with the Telco Generic Schema for consistency and TNI compliance.
* Save time and reduce errors by working with a tested and proven ETL framework.
The following screenshot can help you duplicate the ETL Transform Map.
## Procedure
1. Navigate to All > IntegrationHub ETL.
2. On the IntegrationHub ETL page, select the connector's application scope.
Note: For example, Service Graph Connector for Nokia NSP.
3. Expand the CMDB Application Telco Generic Schema and select Telco Generic Schema record.
4. Click Duplicate.
The Duplicate ETL Transform Map page appears.
5. Configure the duplicated ETL transform map
1. In the Duplicate From field, ensure Telco Generic Schema is selected.
2. Select an existing CMDB Application or click Add new... to add a new CMDB Application.
3. For a new CMDB Application, enter the CMDB application name (for example, Nokia NSP Generic ETL v2)
4. In the Discovery Source field, select the import set.
5. In the Name field, enter a name for the duplicate ETL.
6. In the Description field, enter a description for the duplicate ETL.
7. Select the data source that is used for the duplicate ETL transform map.
Note: This needs to be different than the existing default Data Source that is attached to the Telco Generic Schema ETL. For more information, see Create a data source similar to Telecom core data source.
8. Enable Auto-pull a new import set option to automatically pull data into a new import set.
9. In the Preview Size Override field, set a custom preview size for testing and validation.
6. Select Create Duplicate.
A duplicate ETL of Telco Generic ETL is created.
7. (Optional)
Open the duplicated ETL record and review the mappings and settings.
### What to do next
1. Test the duplicated ETL (optional but recommended):
* Run a test load or a simulation using the temporary data source.
* Verify that import sets are processed successfully, CIs are created according to the Telco Generic Schema, and relationships are established properly.
2. After successful duplication and testing:
* Update the ETL’s data source configuration to point to the actual production data source (for real device data).
* Deploy the connector integration into a test or production environment.
* Monitor import runs to validate that inventory data is ingested into the CMDB correctly.
|
https://www.servicenow.com/docs/en-US/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/initial-setup-procedure.html | https://servicenow-be-prod.servicenow.com/api/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/initial-setup-procedure.html | 2025-08-02 | daily | 0.5 | 268.xml | en-US | zurich-telecom-service-ops | product/tmt-telecom-service-operations-mgt/task/initial-setup-procedure.html | zurich | Install and configure the Nokia Altiplano | Learn how to install and configure the Service Graph Connector for Nokia Altiplano, including optional demo data, connectivity setup, and data collection schedules. | [] | [
"Telecommunications Service Operations Management",
"Configuring Telecommunications Service Operations Management",
"Set up Telecom Visibility",
"Configuring Nokia Altiplano service graph connector"
] | <article class="hascomments" data-page="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/initial-setup-procedure.html" id="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/initial-setup-procedure.html"><body id="initial-setup-procedure"><main role="main"><article role="article" class="dita" id="initial-setup-procedure" aria-labelledby="title_initial-setup-procedure">
<h1 class="title topictitle1" id="title_initial-setup-procedure">Install and configure the Nokia Altiplano</h1>
<div class="body taskbody"><p class="shortdesc">Learn how to install and configure the Service Graph Connector for Nokia Altiplano, including optional demo data, connectivity setup, and data collection schedules.</p>
<section class="section prereq" id="initial-setup-procedure__task-prereq"><div class="tasklabel"><p class="sectiontitle tasklabel">Before you begin</p></div>
<p class="p">Role required: admin</p>
</section>
<section class="section context" id="initial-setup-procedure__context_qbq_2zd_wfc"><div class="tasklabel"><p class="sectiontitle tasklabel">About this task</p></div>
<div class="p">Confirm you are operating in the Service Graph Connector for the Nokia Altiplano application scope. To switch to the Service Graph Connector for Nokia Altiplano scope:<ol class="ol" id="initial-setup-procedure__ol_rzl_2xd_wfc">
<li class="li">Select the application picker (<svg class="image svg decorative" viewBox="0 0 24 24" fill="none" id="initial-setup-procedure__image_eln_3vt_b2c" width="24" height="24">
<path fill-rule="evenodd" clip-rule="evenodd" d="M12 23C18.0751 23 23 18.0751 23 12C23 5.92487 18.0751 1 12 1C5.92487 1 1 5.92487 1 12C1 18.0751 5.92487 23 12 23ZM12 3C11.2021 3 10.2106 3.67281 9.35889 5.37615C8.98686 6.12021 8.67317 7.00713 8.44124 8H15.5588C15.3268 7.00713 15.0131 6.12021 14.6411 5.37615C13.7894 3.67281 12.7979 3 12 3ZM7.57004 4.48172C7.06327 5.49526 6.66327 6.68873 6.39385 8H3.93552C4.77736 6.30602 6.13722 4.91491 7.80783 4.03392C7.72515 4.18059 7.64587 4.33006 7.57004 4.48172ZM6.09517 10H3.22302C3.07706 10.6432 3 11.3126 3 12C3 12.6874 3.07706 13.3568 3.22302 14H6.09517C6.0325 13.3499 6 12.6812 6 12C6 11.3188 6.0325 10.6501 6.09517 10ZM6.39385 16H3.93552C4.77736 17.694 6.13722 19.0851 7.80783 19.9661C7.72515 19.8194 7.64587 19.6699 7.57004 19.5183C7.06327 18.5047 6.66327 17.3113 6.39385 16ZM8.44124 16H15.5588C15.3268 16.9929 15.0131 17.8798 14.6411 18.6239C13.7894 20.3272 12.7979 21 12 21C11.2021 21 10.2106 20.3272 9.35889 18.6239C8.98686 17.8798 8.67317 16.9929 8.44124 16ZM15.8946 14H8.10541C8.03664 13.3585 8 12.6894 8 12C8 11.3106 8.03664 10.6415 8.10541 10H15.8946C15.9634 10.6415 16 11.3106 16 12C16 12.6894 15.9634 13.3585 15.8946 14ZM17.6061 16C17.3367 17.3113 16.9367 18.5047 16.43 19.5183C16.3541 19.6699 16.2748 19.8194 16.1922 19.9661C17.8628 19.0851 19.2226 17.694 20.0645 16H17.6061ZM20.777 14H17.9048C17.9675 13.3499 18 12.6812 18 12C18 11.3188 17.9675 10.6501 17.9048 10H20.777C20.9229 10.6432 21 11.3126 21 12C21 12.6874 20.9229 13.3568 20.777 14ZM16.1922 4.03392C17.8628 4.9149 19.2226 6.30602 20.0645 8H17.6061C17.3367 6.68873 16.9367 5.49526 16.43 4.48172C16.3541 4.33006 16.2748 4.18059 16.1922 4.03392Z" fill="black"></path>
</svg>) in the header.</li>
<li class="li">Search for <span class="ph uicontrol">Nokia Altiplano</span>.</li>
<li class="li">Select Service Graph Connector for Nokia Altiplano from the list.</li>
</ol></div>
</section>
<section><div class="tasklabel"><p class="sectiontitle tasklabel">Procedure</p></div><ol class="ol steps"><li class="li step stepexpand">
<span class="ph cmd">Navigate to <span class="ph menucascade"><span class="ph uicontrol">All</span><abbr> > </abbr><span class="ph uicontrol">Service Graph Connectors</span><abbr> > </abbr><span class="ph uicontrol">Nokia Altiplano</span><abbr> > </abbr><span class="ph uicontrol">Setup</span></span>.</span>
</li><li class="li step stepexpand">
<span class="ph cmd">On the Getting started page, select <span class="ph uicontrol">Get Started</span>.</span>
<div class="itemgroup stepresult">The Guided Setup home page opens in a new tab.</div>
</li><li class="li step stepexpand">(Optional)
<span class="ph cmd">Create and configure <span class="ph">MID Server</span> or skip based on your environment.</span>
<ol type="a" class="ol substeps" id="initial-setup-procedure__substeps_l42_x1y_12c">
<li class="li substep substepexpand">
<span class="ph cmd">Select <span class="ph uicontrol">Configure</span> to complete the process.</span>
</li>
<li class="li substep substepexpand">
<span class="ph cmd">Follow the on-screen instructions to download and install.</span>
</li>
<li class="li substep substepexpand">
<span class="ph cmd">Select <span class="ph uicontrol">Mark as Complete</span> when done.</span>
<div class="itemgroup info">
<div class="note note note_note"><span class="note__title">Note:</span> For more information on how to install and configure MID Server, see <a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/task//csh" href="https://servicenow-be-prod.servicenow.com/csh?topicname=configure-mid-server&version=zurich&pubname=zurich-servicenow-platform" class="xref">Configuring MID Server</a>.</div>
</div>
</li>
<li class="li substep substepexpand">
<span class="ph cmd">Configure or skip the validation step.</span>
</li>
<li class="li substep substepexpand">
<span class="ph cmd">Select <span class="ph uicontrol">Mark as Complete</span> when validated.</span>
<div class="itemgroup stepresult">Once all MID Server steps are complete, proceed to <span class="ph uicontrol">Configure Connectivity</span>.</div>
</li>
</ol>
</li><li class="li step stepexpand">
<span class="ph cmd">Create connection aliases, credentials, and HTTP connections to your Nokia Altiplano instance with <span class="ph uicontrol">Configure Connectivity</span></span>
<ol type="a" class="ol substeps" id="initial-setup-procedure__substeps_pqx_gby_12c">
<li class="li substep substepexpand">
<span class="ph cmd">Select <span class="ph uicontrol">Get Started</span>.</span>
</li>
<li class="li substep substepexpand">
<span class="ph cmd">Create and configure aliases for the connections and credentials:</span>
<div class="itemgroup info">
<ol class="ol" type="i" id="initial-setup-procedure__ol_qsm_nby_12c">
<li class="li">Select <span class="ph uicontrol">Configure</span>.</li>
<li class="li">In the <span class="ph uicontrol">Name</span> field, specify the alias name.</li>
<li class="li">Leave the rest of the fields as default, select <span class="ph uicontrol">Submit</span> and then <span class="ph uicontrol">Mark as Complete</span>.</li>
</ol>
<div class="note note note_note"><span class="note__title">Note:</span> This enables using the connection by name rather than directly, enabling the collector to extract all active aliases from the CMDB and start performing data collection on the HTTP connection bound to
it.</div>
</div>
</li>
<li class="li substep substepexpand">
<span class="ph cmd">Create the credentials to access the Nokia Altiplano Controller by selecting <span class="ph uicontrol">Configure</span>.</span>
<div class="itemgroup info">
<ol class="ol" type="i" id="initial-setup-procedure__ol_nsm_1cy_12c">
<li class="li">In the <span class="ph uicontrol">Name</span> field, specify the alias name.</li>
<li class="li">In the <span class="ph uicontrol">User name</span> field, specify your Nokia Altiplano instance user name.</li>
<li class="li">In the <span class="ph uicontrol">Password</span> field, specify your Nokia Altiplano instance password.<div class="note note note_note"><span class="note__title">Note:</span> Other authentication fields may be required depending on the authentication methods used in your Nokia
Altiplano instance. By default, we use <a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/task//csh" href="https://servicenow-be-prod.servicenow.com/csh?topicname=r_BasicAuthCredentialsForm&version=zurich&pubname=zurich-platform-security" class="xref">Basic authentication credentials</a> (as part of the Guided setup).</div></li>
<li class="li">Leave the rest of the fields as default, select <span class="ph uicontrol">Submit</span> and then select <span class="ph uicontrol">Mark as Complete</span>.</li>
</ol>
</div>
</li>
<li class="li substep substepexpand">
<span class="ph cmd">Create HTTP Connection by selecting <span class="ph uicontrol">Configure</span></span>
<div class="itemgroup info">
<ol class="ol" type="i" id="initial-setup-procedure__ol_opw_1dy_12c">
<li class="li">In the <span class="ph uicontrol">Name</span> field, specify the connection name.</li>
<li class="li">Choose the <span class="ph uicontrol">Credentials</span> and <span class="ph uicontrol">Connection Alias</span> created earlier.</li>
<li class="li">Specify the <span class="ph uicontrol">Connection URL</span> for Nokia Altiplano.</li>
<li class="li">Check <span class="ph uicontrol">Use MID Server</span> and choose either:<ul class="ul" id="initial-setup-procedure__ul_tp4_412_wfc">
<li class="li">Auto-select</li>
<li class="li">Specific MID Server</li>
<li class="li">Specific MID Cluster</li>
</ul></li>
<li class="li">Leave the rest of the fields as default, select <span class="ph uicontrol">Submit</span> and then select <span class="ph uicontrol">Mark as Complete</span>.</li>
</ol>
</div>
</li>
</ol>
</li><li class="li step stepexpand">
<span class="ph cmd">Configure Data Collection Schedule either for bulk discovery or filtered discovery by clicking <span class="ph uicontrol">Get Started</span>and then click <span class="ph uicontrol">Configure</span>.</span>
<div class="table-wrap"><table count-columns="2" border="1" frame="hsides" rules="rows" cellpadding="4" cellspacing="0" summary="" class="simpletable choicetable choicetableborder" id="initial-setup-procedure__choicetable_h3d_ndy_yfc"><colgroup><col style="width:50%"/><col style="width:50%"/></colgroup><thead class="thead"><tr class="sthead chhead"><th scope="col" class="stentry choptionhd" style="vertical-align:bottom;text-align:left;">To</th><th scope="col" class="stentry chdeschd" style="vertical-align:bottom;text-align:left;">Do the following</th></tr></thead><tbody><tr class="strow chrow">
<td style="vertical-align:top;" headers="d7716e346-option" id="d7716e359" class="stentry choption">Schedule data collection for bulk discovery (Use bulk discovery data source for all devices in connection alias)</td>
<td style="vertical-align:top;" class="stentry chdesc">
<ul class="ul" id="initial-setup-procedure__ul_npf_gh5_xfc">
<li class="li">Provide a <span class="ph uicontrol">Name</span> for the scheduler. </li>
<li class="li">Ensure the bulk data source SGC-Nokia Altipano Bulk Discovery is selected.</li>
<li class="li">Set <span class="ph uicontrol">Active</span> the scheduler automatically runs as mentioned in the <span class="ph uicontrol">Run</span> and <span class="ph uicontrol">Time</span> fields. If inactive, you must manually execute.</li>
<li class="li">Select <span class="ph uicontrol">Use Connection.</span></li>
<li class="li">In the <span class="ph uicontrol">Connection</span> field, select connection alias. For example, sn_sgc_altiplano.Atiplano_Alias.</li>
<li class="li">In the <span class="ph uicontrol">Run</span> field, select the frequency. Specify when you want this schedule to run: Daily, Weekly, Monthly, Periodically, After Parent Runs, or Once.</li>
<li class="li">In the <span class="ph uicontrol">Time</span> field, enter the time in hours, minutes, and seconds.</li>
</ul>
</td>
</tr><tr class="strow chrow">
<td style="vertical-align:top;" headers="d7716e346-option" id="d7716e416" class="stentry choption">Schedule data collection for filtered discovery (Use Filtering Discovery data source for specific OLT filter criteria for each connection alias)</td>
<td style="vertical-align:top;" class="stentry chdesc">
<ol class="ol" type="a" id="initial-setup-procedure__ol_oyc_1zs_xfc">
<li class="li">Add Filtering Parameters<ol class="ol" type="i" id="initial-setup-procedure__ol_fm1_zdy_yfc">
<li class="li">In the <span class="ph uicontrol">Connection Alias</span> field, choose a connection alias.</li>
<li class="li">Optionally, in the <span class="ph uicontrol">Filtered IPs</span> field, add IP filters in various formats defined as following:<ul class="ul" id="initial-setup-procedure__ul_qmm_3j2_wfc">
<li class="li">Single IP: <code class="ph codeph">10.10.10.10</code></li>
<li class="li">List: <code class="ph codeph">10.10.10.10, 10.10.10.20</code></li>
<li class="li">Ranges: <code class="ph codeph">10.10.10.30-10.10.10.40</code></li>
<li class="li">CIDR: <code class="ph codeph">10.10.10.0/24</code></li>
<li class="li">Mask: <code class="ph codeph">10.10.10.0:255.255.255.0</code></li>
</ul></li>
<li class="li">Optionally, add name filters to search by device name or part of the name. You can specify a single string or a list of names to filter the results.</li>
</ol></li>
<li class="li">Schedule filtered Collection<ul class="ul" id="initial-setup-procedure__ul_rmm_3j2_wfc">
<li class="li">Provide a <span class="ph uicontrol">Name</span> for the scheduler.</li>
<li class="li">Ensure the data source SGC-Nokia Altipano Filtering Discovery is selected.</li>
<li class="li">Set <span class="ph uicontrol">Active</span> the scheduler automatically runs as mentioned in the <span class="ph uicontrol">Run</span> and <span class="ph uicontrol">Time</span> fields. If inactive, you must manually
execute.</li>
<li class="li">In the <span class="ph uicontrol">Run</span> field, select the frequency. Specify when you want this schedule to run: Daily, Weekly, Monthly, Periodically, After Parent Runs, or Once.</li>
<li class="li">In the <span class="ph uicontrol">Time</span> field, enter the time in hours, minutes, and seconds.</li>
<li class="li">Select <span class="ph uicontrol">Use Connection.</span>.</li>
<li class="li">In the <span class="ph uicontrol">Connection</span> field, select connection alias. For example, sn_sgc_altiplano.Atiplano_Alias.</li>
</ul></li>
</ol>
</td>
</tr></tbody></table></div>
</li><li class="li step stepexpand">
<span class="ph cmd">Select <span class="ph uicontrol">Submit</span> and then select <span class="ph uicontrol">Mark as Complete</span>.</span>
</li></ol></section>
<section class="section result" id="initial-setup-procedure__result_nrl_tfy_yfc"><div class="tasklabel"><p class="sectiontitle tasklabel">Result</p></div>
<p class="p">The configured connections, aliases, credentials, and import schedules can also be accessed from the navigation Navigate to <span class="ph menucascade"><span class="ph uicontrol">All</span><abbr> > </abbr><span class="ph uicontrol">Service Graph Connectors</span><abbr> > </abbr><span class="ph uicontrol">Nokia Altiplano</span></span>. </p>
<p class="p">The following snapshot helps you confirm the configuration set up of Nokia Altiplano service graph connector.</p>
<p class="p"><img src="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/../images/Complete-guided-setup.png?_LANG=enus" class="image" id="initial-setup-procedure__image_s4s_2gy_yfc" alt="Nokia Altiplano guided setup that has completed all the steps."/></p>
</section>
</div>
<nav role="navigation"></nav><nav role="navigation" class="tasksNavigation"></nav><nav role="navigation" class="related-links"><div class="col-md-4"><dt>Related tasks</dt><dd><ul><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/task/multi-instance-setup.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/multi-instance-setup.html" class="link" title="Learn how to configure and manage multiple Nokia Altiplano instances within a single ServiceNow environment. This enables administrators and integrators to create independent connection aliases and import schedules customized to specific filtering or frequency needs.">Set up multiple Nokia Altiplano instances</a></li><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/task/configure-concurrent-import-and-parallel-loading.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/configure-concurrent-import-and-parallel-loading.html" class="link" title="Improve the efficiency of large data imports from Nokia Altiplano by configuring concurrent imports and enabling parallel loading. This configuration allows the platform to run multiple data import and transformation jobs simultaneously.">Configure concurrent import and parallel loading for Nokia Altiplano</a></li></ul></dd></div><div class="col-md-4"><dt>Related concepts</dt><dd><ul><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/concept/data-mapping.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/data-mapping.html" class="link" title="Use the Service Graph Connector for Nokia Altiplano to map discovered physical and logical network resources to telecom-aligned Configuration Item (CI) classes in the CMDB. The connector supports consistent service modeling, visibility into chassis-level components, and automation of logical and physical relationships.">Mapping Nokia Altiplano CIs and Relationships in CMDB</a></li></ul></dd></div><div class="col-md-4"><dt>Related reference</dt><dd><ul><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/reference/properties-installed-with-nokia-altiplano.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/reference/properties-installed-with-nokia-altiplano.html" class="link" title="System properties control how the connector operates, including discovery options and performance settings.">System components installed with Nokia Altiplano</a></li></ul></dd></div></nav>
</article></main></body></article> | {
"attachments": {
"all_attachments": null,
"topic_attachments": []
},
"available_languages": [
"enus"
],
"breadcrumbs": [
{
"title": "Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html"
},
{
"title": "Configuring Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/configuring-tsom.html"
},
{
"title": "Set up Telecom Visibility",
"topic_id": "product/tmt-telecom-service-operations-mgt/task/configuring-tsom-visibility.html"
},
{
"title": "Configuring Nokia Altiplano service graph connector",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/configuring-service-graph-connector-nokia-altiplano.html"
}
],
"breadcrumbs_html": "<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops\">Zurich Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html\">Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/configuring-tsom.html\">Configuring Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/configuring-tsom-visibility.html\">Set up Telecom Visibility</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/configuring-service-graph-connector-nokia-altiplano.html\">Configuring Nokia Altiplano service graph connector</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<span class=\"active\">Install and configure the Nokia Altiplano</span>",
"bundle_id": "zurich-telecom-service-ops",
"bundle_key": 2733,
"bundle_landing_page": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html",
"bundle_subtitle": null,
"bundle_title": "Zurich Telecommunications Service Operations Management",
"canonical_link": null,
"dates": {
"Added on": "2025-08-02T00:48:08.794016Z",
"Created on": "2025-01-15T00:00:00Z",
"Initial upload": "2025-07-30T22:24:33.519043Z",
"Updated on": "2025-07-31T00:00:00Z"
},
"dislike_url": "https://servicenow-be-prod.servicenow.com/dislike/55686976",
"dislikes": 0,
"es_archived_content": false,
"is_in_fav": false,
"is_liked": null,
"is_watched": false,
"keywords": [
" zurich zurich"
],
"labels": [
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "zurich",
"navtitle": "Zurich",
"outputclasses": [],
"subjectHeadId": "versions",
"subjectheadNavtitle": "Versions",
"visibility": "show-facet"
},
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "tsom",
"navtitle": "Telecommunications Service Operations Management",
"outputclasses": [],
"subjectHeadId": "products",
"subjectheadNavtitle": "Products",
"visibility": "show-facet"
}
],
"labels_text": "Versions > Zurich; Products > CRM and Industry Products > Telecommunications Media and Technology Assurance > Telecommunications Service Operations Management",
"like_url": "https://servicenow-be-prod.servicenow.com/like/55686976",
"likes": 0,
"metadata": {
"AI Search": null,
"AI Search Assist": null,
"Application Insights": null,
"Capabilities": null,
"Code Signing": null,
"Contextual Search": null,
"DC.contributor": null,
"DC.coverage": null,
"DC.creator": "ServiceNow",
"DC.date.created": "2025-01-15T14:07:35+05:30",
"DC.date.modified": "2025-07-31",
"DC.format": "HTML5",
"DC.identifier": "initial-setup-procedure",
"DC.language": null,
"DC.relation": "multi-instance-setup.html",
"DC.rights.owner": "(C) Copyright 2025",
"DC.subject": null,
"DC.type": "task",
"Data Discovery": null,
"Data Policy": null,
"Data Privacy": null,
"Discovery": null,
"External Content for AI Search": null,
"Field Administration": null,
"Field Normalization": null,
"Key Management Framework": null,
"Localization Framework": null,
"Now Platform": null,
"PlatSec": null,
"Platform": null,
"Platform Administration": null,
"Platform Performance": null,
"Platform Privacy": null,
"Proactive Triggers": null,
"Process Optimization": null,
"RN doc editing record number": null,
"Search Administration": null,
"Secrets Management": null,
"ServiceNow AI Platform": null,
"State Model": null,
"Subscription Management": null,
"Task Communications Management": null,
"Timeline Visualizations": null,
"User Administration": null,
"User Experience Analytics": null,
"Zing": null,
"ai-now-assist": null,
"app-name": null,
"app_route": null,
"azureapimanagemen": null,
"change-completed": null,
"change-item": null,
"change-request-id": null,
"change-request-reference": null,
"com.glide.embedded_help.category": null,
"component": null,
"copyright": "(C) Copyright 2025",
"crossroads": null,
"data": null,
"description": "Learn how to install and configure the Service Graph Connector for Nokia Altiplano, including optional demo data, connectivity setup, and data collection schedules.",
"dominant_bundle": null,
"erp-canvas-video": null,
"fsm-mobile": null,
"fsm-route": null,
"fsm-sched-opt": null,
"fsm-wrk-order": null,
"genai-round-7": null,
"generator": "DITA-OT",
"glossPartOfSpeech": null,
"glossStatus": null,
"guided setup": null,
"guided tours": null,
"keywords": null,
"min-toc": null,
"mini": null,
"mini-to truec": null,
"mini-toc": null,
"mini_toc": null,
"minitoc": null,
"modification": null,
"now-assist-app-gen-video": null,
"order": null,
"page-type": null,
"page-type ": null,
"prodname": null,
"product": null,
"product_name": null,
"release": null,
"resourceID": null,
"roles": null,
"route_page": null,
"route_params_listId": null,
"route_params_table": null,
"route_params_type": null,
"route_type": null,
"setconfigurationproperties": null,
"topic": null,
"translation-type": "source",
"version": null,
"workflow": "Customer and Industry",
"workplace-srvc-delvry-ditamap": null
},
"page_id": "product/tmt-telecom-service-operations-mgt/task/initial-setup-procedure.html",
"page_key": 55686976,
"preprocessed_PDF": "https://downloads.docs.servicenow.com/pdf/enus/servicenow-zurich-telecom-service-ops-enus.pdf",
"rating": null,
"read_time_data": {
"char_count": 5187,
"img_count": 1,
"read_time": 4,
"video_links": [
""
],
"word_count": 780
},
"related_links": [
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "Learn how to configure and manage multiple Nokia Altiplano instances within a single ServiceNow environment. This enables administrators and integrators to create independent connection aliases and import schedules customized to specific filtering or frequency needs.",
"title": "Set up multiple Nokia Altiplano instances",
"topic": "/product/tmt-telecom-service-operations-mgt/task/multi-instance-setup.html",
"type": "task",
"url": null
},
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "Improve the efficiency of large data imports from Nokia Altiplano by configuring concurrent imports and enabling parallel loading. This configuration allows the platform to run multiple data import and transformation jobs simultaneously.",
"title": "Configure concurrent import and parallel loading for Nokia Altiplano",
"topic": "/product/tmt-telecom-service-operations-mgt/task/configure-concurrent-import-and-parallel-loading.html",
"type": "task",
"url": null
},
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "Use the Service Graph Connector for Nokia Altiplano to map discovered physical and logical network resources to telecom-aligned Configuration Item (CI) classes in the CMDB. The connector supports consistent service modeling, visibility into chassis-level components, and automation of logical and physical relationships.",
"title": "Mapping Nokia Altiplano CIs and Relationships in CMDB",
"topic": "/product/tmt-telecom-service-operations-mgt/concept/data-mapping.html",
"type": "concept",
"url": null
},
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "System properties control how the connector operates, including discovery options and performance settings.",
"title": "System components installed with Nokia Altiplano",
"topic": "/product/tmt-telecom-service-operations-mgt/reference/properties-installed-with-nokia-altiplano.html",
"type": "reference",
"url": null
}
],
"search_title": null,
"title": "Install and configure the Nokia Altiplano",
"topic_cluster": {
"clustered_by": {
"enabled": true,
"primary_key": "versions",
"primary_sort": "top-down",
"type": "subjecthead"
},
"clustered_labels": [
"versions"
],
"clustered_topics": [],
"clustering_title": "Zurich"
},
"topic_html": "<article class=\"hascomments\" data-page=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/initial-setup-procedure.html\" id=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/initial-setup-procedure.html\"><body id=\"initial-setup-procedure\"><main role=\"main\"><article role=\"article\" class=\"dita\" id=\"initial-setup-procedure\" aria-labelledby=\"title_initial-setup-procedure\">\n <h1 class=\"title topictitle1\" id=\"title_initial-setup-procedure\">Install and configure the Nokia Altiplano</h1>\n \n \n <div class=\"body taskbody\"><p class=\"shortdesc\">Learn how to install and configure the Service Graph Connector for Nokia Altiplano, including optional demo data, connectivity setup, and data collection schedules.</p>\n <section class=\"section prereq\" id=\"initial-setup-procedure__task-prereq\"><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">Before you begin</p></div>\n <p class=\"p\">Role required: admin</p>\n </section>\n <section class=\"section context\" id=\"initial-setup-procedure__context_qbq_2zd_wfc\"><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">About this task</p></div>\n <div class=\"p\">Confirm you are operating in the Service Graph Connector for the Nokia Altiplano application scope. To switch to the Service Graph Connector for Nokia Altiplano scope:<ol class=\"ol\" id=\"initial-setup-procedure__ol_rzl_2xd_wfc\">\n <li class=\"li\">Select the application picker (<svg class=\"image svg decorative\" viewBox=\"0 0 24 24\" fill=\"none\" id=\"initial-setup-procedure__image_eln_3vt_b2c\" width=\"24\" height=\"24\">\n<path fill-rule=\"evenodd\" clip-rule=\"evenodd\" d=\"M12 23C18.0751 23 23 18.0751 23 12C23 5.92487 18.0751 1 12 1C5.92487 1 1 5.92487 1 12C1 18.0751 5.92487 23 12 23ZM12 3C11.2021 3 10.2106 3.67281 9.35889 5.37615C8.98686 6.12021 8.67317 7.00713 8.44124 8H15.5588C15.3268 7.00713 15.0131 6.12021 14.6411 5.37615C13.7894 3.67281 12.7979 3 12 3ZM7.57004 4.48172C7.06327 5.49526 6.66327 6.68873 6.39385 8H3.93552C4.77736 6.30602 6.13722 4.91491 7.80783 4.03392C7.72515 4.18059 7.64587 4.33006 7.57004 4.48172ZM6.09517 10H3.22302C3.07706 10.6432 3 11.3126 3 12C3 12.6874 3.07706 13.3568 3.22302 14H6.09517C6.0325 13.3499 6 12.6812 6 12C6 11.3188 6.0325 10.6501 6.09517 10ZM6.39385 16H3.93552C4.77736 17.694 6.13722 19.0851 7.80783 19.9661C7.72515 19.8194 7.64587 19.6699 7.57004 19.5183C7.06327 18.5047 6.66327 17.3113 6.39385 16ZM8.44124 16H15.5588C15.3268 16.9929 15.0131 17.8798 14.6411 18.6239C13.7894 20.3272 12.7979 21 12 21C11.2021 21 10.2106 20.3272 9.35889 18.6239C8.98686 17.8798 8.67317 16.9929 8.44124 16ZM15.8946 14H8.10541C8.03664 13.3585 8 12.6894 8 12C8 11.3106 8.03664 10.6415 8.10541 10H15.8946C15.9634 10.6415 16 11.3106 16 12C16 12.6894 15.9634 13.3585 15.8946 14ZM17.6061 16C17.3367 17.3113 16.9367 18.5047 16.43 19.5183C16.3541 19.6699 16.2748 19.8194 16.1922 19.9661C17.8628 19.0851 19.2226 17.694 20.0645 16H17.6061ZM20.777 14H17.9048C17.9675 13.3499 18 12.6812 18 12C18 11.3188 17.9675 10.6501 17.9048 10H20.777C20.9229 10.6432 21 11.3126 21 12C21 12.6874 20.9229 13.3568 20.777 14ZM16.1922 4.03392C17.8628 4.9149 19.2226 6.30602 20.0645 8H17.6061C17.3367 6.68873 16.9367 5.49526 16.43 4.48172C16.3541 4.33006 16.2748 4.18059 16.1922 4.03392Z\" fill=\"black\"></path>\n</svg>) in the header.</li>\n <li class=\"li\">Search for <span class=\"ph uicontrol\">Nokia Altiplano</span>.</li>\n <li class=\"li\">Select Service Graph Connector for Nokia Altiplano from the list.</li>\n </ol></div>\n </section>\n <section><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">Procedure</p></div><ol class=\"ol steps\"><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">Navigate to <span class=\"ph menucascade\"><span class=\"ph uicontrol\">All</span><abbr> > </abbr><span class=\"ph uicontrol\">Service Graph Connectors</span><abbr> > </abbr><span class=\"ph uicontrol\">Nokia Altiplano</span><abbr> > </abbr><span class=\"ph uicontrol\">Setup</span></span>.</span>\n </li><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">On the Getting started page, select <span class=\"ph uicontrol\">Get Started</span>.</span>\n <div class=\"itemgroup stepresult\">The Guided Setup home page opens in a new tab.</div>\n </li><li class=\"li step stepexpand\">(Optional) \n <span class=\"ph cmd\">Create and configure <span class=\"ph\">MID Server</span> or skip based on your environment.</span>\n <ol type=\"a\" class=\"ol substeps\" id=\"initial-setup-procedure__substeps_l42_x1y_12c\">\n <li class=\"li substep substepexpand\">\n <span class=\"ph cmd\">Select <span class=\"ph uicontrol\">Configure</span> to complete the process.</span>\n </li>\n <li class=\"li substep substepexpand\">\n <span class=\"ph cmd\">Follow the on-screen instructions to download and install.</span>\n </li>\n <li class=\"li substep substepexpand\">\n <span class=\"ph cmd\">Select <span class=\"ph uicontrol\">Mark as Complete</span> when done.</span>\n <div class=\"itemgroup info\">\n <div class=\"note note note_note\"><span class=\"note__title\">Note:</span> For more information on how to install and configure MID Server, see <a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/task//csh\" href=\"https://servicenow-be-prod.servicenow.com/csh?topicname=configure-mid-server&version=zurich&pubname=zurich-servicenow-platform\" class=\"xref\">Configuring MID Server</a>.</div>\n </div>\n </li>\n <li class=\"li substep substepexpand\">\n <span class=\"ph cmd\">Configure or skip the validation step.</span>\n </li>\n <li class=\"li substep substepexpand\">\n <span class=\"ph cmd\">Select <span class=\"ph uicontrol\">Mark as Complete</span> when validated.</span>\n <div class=\"itemgroup stepresult\">Once all MID Server steps are complete, proceed to <span class=\"ph uicontrol\">Configure Connectivity</span>.</div>\n </li>\n </ol>\n </li><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">Create connection aliases, credentials, and HTTP connections to your Nokia Altiplano instance with <span class=\"ph uicontrol\">Configure Connectivity</span></span>\n <ol type=\"a\" class=\"ol substeps\" id=\"initial-setup-procedure__substeps_pqx_gby_12c\">\n <li class=\"li substep substepexpand\">\n <span class=\"ph cmd\">Select <span class=\"ph uicontrol\">Get Started</span>.</span>\n </li>\n <li class=\"li substep substepexpand\">\n <span class=\"ph cmd\">Create and configure aliases for the connections and credentials:</span>\n <div class=\"itemgroup info\">\n <ol class=\"ol\" type=\"i\" id=\"initial-setup-procedure__ol_qsm_nby_12c\">\n <li class=\"li\">Select <span class=\"ph uicontrol\">Configure</span>.</li>\n <li class=\"li\">In the <span class=\"ph uicontrol\">Name</span> field, specify the alias name.</li>\n <li class=\"li\">Leave the rest of the fields as default, select <span class=\"ph uicontrol\">Submit</span> and then <span class=\"ph uicontrol\">Mark as Complete</span>.</li>\n </ol>\n <div class=\"note note note_note\"><span class=\"note__title\">Note:</span> This enables using the connection by name rather than directly, enabling the collector to extract all active aliases from the CMDB and start performing data collection on the HTTP connection bound to\n it.</div>\n </div>\n </li>\n <li class=\"li substep substepexpand\">\n <span class=\"ph cmd\">Create the credentials to access the Nokia Altiplano Controller by selecting <span class=\"ph uicontrol\">Configure</span>.</span>\n <div class=\"itemgroup info\">\n <ol class=\"ol\" type=\"i\" id=\"initial-setup-procedure__ol_nsm_1cy_12c\">\n <li class=\"li\">In the <span class=\"ph uicontrol\">Name</span> field, specify the alias name.</li>\n <li class=\"li\">In the <span class=\"ph uicontrol\">User name</span> field, specify your Nokia Altiplano instance user name.</li>\n <li class=\"li\">In the <span class=\"ph uicontrol\">Password</span> field, specify your Nokia Altiplano instance password.<div class=\"note note note_note\"><span class=\"note__title\">Note:</span> Other authentication fields may be required depending on the authentication methods used in your Nokia\n Altiplano instance. By default, we use <a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/task//csh\" href=\"https://servicenow-be-prod.servicenow.com/csh?topicname=r_BasicAuthCredentialsForm&version=zurich&pubname=zurich-platform-security\" class=\"xref\">Basic authentication credentials</a> (as part of the Guided setup).</div></li>\n <li class=\"li\">Leave the rest of the fields as default, select <span class=\"ph uicontrol\">Submit</span> and then select <span class=\"ph uicontrol\">Mark as Complete</span>.</li>\n </ol>\n </div>\n </li>\n <li class=\"li substep substepexpand\">\n <span class=\"ph cmd\">Create HTTP Connection by selecting <span class=\"ph uicontrol\">Configure</span></span>\n <div class=\"itemgroup info\">\n <ol class=\"ol\" type=\"i\" id=\"initial-setup-procedure__ol_opw_1dy_12c\">\n <li class=\"li\">In the <span class=\"ph uicontrol\">Name</span> field, specify the connection name.</li>\n <li class=\"li\">Choose the <span class=\"ph uicontrol\">Credentials</span> and <span class=\"ph uicontrol\">Connection Alias</span> created earlier.</li>\n <li class=\"li\">Specify the <span class=\"ph uicontrol\">Connection URL</span> for Nokia Altiplano.</li>\n <li class=\"li\">Check <span class=\"ph uicontrol\">Use MID Server</span> and choose either:<ul class=\"ul\" id=\"initial-setup-procedure__ul_tp4_412_wfc\">\n <li class=\"li\">Auto-select</li>\n <li class=\"li\">Specific MID Server</li>\n <li class=\"li\">Specific MID Cluster</li>\n </ul></li>\n <li class=\"li\">Leave the rest of the fields as default, select <span class=\"ph uicontrol\">Submit</span> and then select <span class=\"ph uicontrol\">Mark as Complete</span>.</li>\n </ol>\n </div>\n </li>\n </ol>\n </li><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">Configure Data Collection Schedule either for bulk discovery or filtered discovery by clicking <span class=\"ph uicontrol\">Get Started</span>and then click <span class=\"ph uicontrol\">Configure</span>.</span>\n <div class=\"table-wrap\"><table count-columns=\"2\" border=\"1\" frame=\"hsides\" rules=\"rows\" cellpadding=\"4\" cellspacing=\"0\" summary=\"\" class=\"simpletable choicetable choicetableborder\" id=\"initial-setup-procedure__choicetable_h3d_ndy_yfc\"><colgroup><col style=\"width:50%\"/><col style=\"width:50%\"/></colgroup><thead class=\"thead\"><tr class=\"sthead chhead\"><th scope=\"col\" class=\"stentry choptionhd\" style=\"vertical-align:bottom;text-align:left;\">To</th><th scope=\"col\" class=\"stentry chdeschd\" style=\"vertical-align:bottom;text-align:left;\">Do the following</th></tr></thead><tbody><tr class=\"strow chrow\">\n <td style=\"vertical-align:top;\" headers=\"d7716e346-option\" id=\"d7716e359\" class=\"stentry choption\">Schedule data collection for bulk discovery (Use bulk discovery data source for all devices in connection alias)</td>\n <td style=\"vertical-align:top;\" class=\"stentry chdesc\">\n <ul class=\"ul\" id=\"initial-setup-procedure__ul_npf_gh5_xfc\">\n <li class=\"li\">Provide a <span class=\"ph uicontrol\">Name</span> for the scheduler. </li>\n <li class=\"li\">Ensure the bulk data source SGC-Nokia Altipano Bulk Discovery is selected.</li>\n <li class=\"li\">Set <span class=\"ph uicontrol\">Active</span> the scheduler automatically runs as mentioned in the <span class=\"ph uicontrol\">Run</span> and <span class=\"ph uicontrol\">Time</span> fields. If inactive, you must manually execute.</li>\n <li class=\"li\">Select <span class=\"ph uicontrol\">Use Connection.</span></li>\n <li class=\"li\">In the <span class=\"ph uicontrol\">Connection</span> field, select connection alias. For example, sn_sgc_altiplano.Atiplano_Alias.</li>\n <li class=\"li\">In the <span class=\"ph uicontrol\">Run</span> field, select the frequency. Specify when you want this schedule to run: Daily, Weekly, Monthly, Periodically, After Parent Runs, or Once.</li>\n <li class=\"li\">In the <span class=\"ph uicontrol\">Time</span> field, enter the time in hours, minutes, and seconds.</li>\n </ul>\n </td>\n </tr><tr class=\"strow chrow\">\n <td style=\"vertical-align:top;\" headers=\"d7716e346-option\" id=\"d7716e416\" class=\"stentry choption\">Schedule data collection for filtered discovery (Use Filtering Discovery data source for specific OLT filter criteria for each connection alias)</td>\n <td style=\"vertical-align:top;\" class=\"stentry chdesc\">\n <ol class=\"ol\" type=\"a\" id=\"initial-setup-procedure__ol_oyc_1zs_xfc\">\n <li class=\"li\">Add Filtering Parameters<ol class=\"ol\" type=\"i\" id=\"initial-setup-procedure__ol_fm1_zdy_yfc\">\n <li class=\"li\">In the <span class=\"ph uicontrol\">Connection Alias</span> field, choose a connection alias.</li>\n <li class=\"li\">Optionally, in the <span class=\"ph uicontrol\">Filtered IPs</span> field, add IP filters in various formats defined as following:<ul class=\"ul\" id=\"initial-setup-procedure__ul_qmm_3j2_wfc\">\n <li class=\"li\">Single IP: <code class=\"ph codeph\">10.10.10.10</code></li>\n <li class=\"li\">List: <code class=\"ph codeph\">10.10.10.10, 10.10.10.20</code></li>\n <li class=\"li\">Ranges: <code class=\"ph codeph\">10.10.10.30-10.10.10.40</code></li>\n <li class=\"li\">CIDR: <code class=\"ph codeph\">10.10.10.0/24</code></li>\n <li class=\"li\">Mask: <code class=\"ph codeph\">10.10.10.0:255.255.255.0</code></li>\n </ul></li>\n <li class=\"li\">Optionally, add name filters to search by device name or part of the name. You can specify a single string or a list of names to filter the results.</li>\n </ol></li>\n <li class=\"li\">Schedule filtered Collection<ul class=\"ul\" id=\"initial-setup-procedure__ul_rmm_3j2_wfc\">\n <li class=\"li\">Provide a <span class=\"ph uicontrol\">Name</span> for the scheduler.</li>\n <li class=\"li\">Ensure the data source SGC-Nokia Altipano Filtering Discovery is selected.</li>\n <li class=\"li\">Set <span class=\"ph uicontrol\">Active</span> the scheduler automatically runs as mentioned in the <span class=\"ph uicontrol\">Run</span> and <span class=\"ph uicontrol\">Time</span> fields. If inactive, you must manually\n execute.</li>\n <li class=\"li\">In the <span class=\"ph uicontrol\">Run</span> field, select the frequency. Specify when you want this schedule to run: Daily, Weekly, Monthly, Periodically, After Parent Runs, or Once.</li>\n <li class=\"li\">In the <span class=\"ph uicontrol\">Time</span> field, enter the time in hours, minutes, and seconds.</li>\n <li class=\"li\">Select <span class=\"ph uicontrol\">Use Connection.</span>.</li>\n <li class=\"li\">In the <span class=\"ph uicontrol\">Connection</span> field, select connection alias. For example, sn_sgc_altiplano.Atiplano_Alias.</li>\n </ul></li>\n </ol>\n </td>\n </tr></tbody></table></div>\n </li><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">Select <span class=\"ph uicontrol\">Submit</span> and then select <span class=\"ph uicontrol\">Mark as Complete</span>.</span>\n </li></ol></section>\n <section class=\"section result\" id=\"initial-setup-procedure__result_nrl_tfy_yfc\"><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">Result</p></div>\n <p class=\"p\">The configured connections, aliases, credentials, and import schedules can also be accessed from the navigation Navigate to <span class=\"ph menucascade\"><span class=\"ph uicontrol\">All</span><abbr> > </abbr><span class=\"ph uicontrol\">Service Graph Connectors</span><abbr> > </abbr><span class=\"ph uicontrol\">Nokia Altiplano</span></span>. </p>\n <p class=\"p\">The following snapshot helps you confirm the configuration set up of Nokia Altiplano service graph connector.</p>\n <p class=\"p\"><img src=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/../images/Complete-guided-setup.png?_LANG=enus\" class=\"image\" id=\"initial-setup-procedure__image_s4s_2gy_yfc\" alt=\"Nokia Altiplano guided setup that has completed all the steps.\"/></p>\n </section>\n </div>\n <nav role=\"navigation\"></nav><nav role=\"navigation\" class=\"tasksNavigation\"></nav><nav role=\"navigation\" class=\"related-links\"><div class=\"col-md-4\"><dt>Related tasks</dt><dd><ul><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/task/multi-instance-setup.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/multi-instance-setup.html\" class=\"link\" title=\"Learn how to configure and manage multiple Nokia Altiplano instances within a single ServiceNow environment. This enables administrators and integrators to create independent connection aliases and import schedules customized to specific filtering or frequency needs.\">Set up multiple Nokia Altiplano instances</a></li><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/task/configure-concurrent-import-and-parallel-loading.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/configure-concurrent-import-and-parallel-loading.html\" class=\"link\" title=\"Improve the efficiency of large data imports from Nokia Altiplano by configuring concurrent imports and enabling parallel loading. This configuration allows the platform to run multiple data import and transformation jobs simultaneously.\">Configure concurrent import and parallel loading for Nokia Altiplano</a></li></ul></dd></div><div class=\"col-md-4\"><dt>Related concepts</dt><dd><ul><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept/data-mapping.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/data-mapping.html\" class=\"link\" title=\"Use the Service Graph Connector for Nokia Altiplano to map discovered physical and logical network resources to telecom-aligned Configuration Item (CI) classes in the CMDB. The connector supports consistent service modeling, visibility into chassis-level components, and automation of logical and physical relationships.\">Mapping Nokia Altiplano CIs and Relationships in CMDB</a></li></ul></dd></div><div class=\"col-md-4\"><dt>Related reference</dt><dd><ul><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/reference/properties-installed-with-nokia-altiplano.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/reference/properties-installed-with-nokia-altiplano.html\" class=\"link\" title=\"System properties control how the connector operates, including discovery options and performance settings.\">System components installed with Nokia Altiplano</a></li></ul></dd></div></nav>\n</article></main></body></article>",
"topic_language": "enus",
"views": 0,
"your_rating": null
} | # Install and configure the Nokia Altiplano
Learn how to install and configure the Service Graph Connector for Nokia Altiplano, including optional demo data, connectivity setup, and data collection schedules.
## Before you begin
Role required: admin
## About this task
Confirm you are operating in the Service Graph Connector for the Nokia Altiplano application scope. To switch to the Service Graph Connector for Nokia Altiplano scope:
1. Select the application picker (
) in the header.
2. Search for Nokia Altiplano.
3. Select Service Graph Connector for Nokia Altiplano from the list.
## Procedure
1. Navigate to All > Service Graph Connectors > Nokia Altiplano > Setup.
2. On the Getting started page, select Get Started.
The Guided Setup home page opens in a new tab.
3. (Optional)
Create and configure MID Server or skip based on your environment.
1. Select Configure to complete the process.
2. Follow the on-screen instructions to download and install.
3. Select Mark as Complete when done.
Note: For more information on how to install and configure MID Server, see Configuring MID Server.
4. Configure or skip the validation step.
5. Select Mark as Complete when validated.
Once all MID Server steps are complete, proceed to Configure Connectivity.
4. Create connection aliases, credentials, and HTTP connections to your Nokia Altiplano instance with Configure Connectivity
1. Select Get Started.
2. Create and configure aliases for the connections and credentials:
1. Select Configure.
2. In the Name field, specify the alias name.
3. Leave the rest of the fields as default, select Submit and then Mark as Complete.Note: This enables using the connection by name rather than directly, enabling the collector to extract all active aliases from the CMDB and start performing data collection on the HTTP connection bound to
it.
3. Create the credentials to access the Nokia Altiplano Controller by selecting Configure.
1. In the Name field, specify the alias name.
2. In the User name field, specify your Nokia Altiplano instance user name.
3. In the Password field, specify your Nokia Altiplano instance password.Note: Other authentication fields may be required depending on the authentication methods used in your Nokia
Altiplano instance. By default, we use Basic authentication credentials (as part of the Guided setup).
4. Leave the rest of the fields as default, select Submit and then select Mark as Complete.
4. Create HTTP Connection by selecting Configure
1. In the Name field, specify the connection name.
2. Choose the Credentials and Connection Alias created earlier.
3. Specify the Connection URL for Nokia Altiplano.
4. Check Use MID Server and choose either:
* Auto-select
* Specific MID Server
* Specific MID Cluster
5. Leave the rest of the fields as default, select Submit and then select Mark as Complete.
5. Configure Data Collection Schedule either for bulk discovery or filtered discovery by clicking Get Startedand then click Configure.
| To | Do the following |
| --- | --- |
| Schedule data collection for bulk discovery (Use bulk discovery data source for all devices in connection alias) | * Provide a Name for the scheduler. * Ensure the bulk data source SGC-Nokia Altipano Bulk Discovery is selected. * Set Active the scheduler automatically runs as mentioned in the Run and Time fields. If inactive, you must manually execute. * Select Use Connection. * In the Connection field, select connection alias. For example, sn\_sgc\_altiplano.Atiplano\_Alias. * In the Run field, select the frequency. Specify when you want this schedule to run: Daily, Weekly, Monthly, Periodically, After Parent Runs, or Once. * In the Time field, enter the time in hours, minutes, and seconds. |
| Schedule data collection for filtered discovery (Use Filtering Discovery data source for specific OLT filter criteria for each connection alias) | 1. Add Filtering Parameters 1. In the Connection Alias field, choose a connection alias. 2. Optionally, in the Filtered IPs field, add IP filters in various formats defined as following: * Single IP: `10.10.10.10` * List: `10.10.10.10, 10.10.10.20` * Ranges: `10.10.10.30-10.10.10.40` * CIDR: `10.10.10.0/24` * Mask: `10.10.10.0:255.255.255.0` 3. Optionally, add name filters to search by device name or part of the name. You can specify a single string or a list of names to filter the results. 2. Schedule filtered Collection * Provide a Name for the scheduler. * Ensure the data source SGC-Nokia Altipano Filtering Discovery is selected. * Set Active the scheduler automatically runs as mentioned in the Run and Time fields. If inactive, you must manually execute. * In the Run field, select the frequency. Specify when you want this schedule to run: Daily, Weekly, Monthly, Periodically, After Parent Runs, or Once. * In the Time field, enter the time in hours, minutes, and seconds. * Select Use Connection.. * In the Connection field, select connection alias. For example, sn\_sgc\_altiplano.Atiplano\_Alias. |
6. Select Submit and then select Mark as Complete.
### Result
The configured connections, aliases, credentials, and import schedules can also be accessed from the navigation Navigate to All > Service Graph Connectors > Nokia Altiplano.
The following snapshot helps you confirm the configuration set up of Nokia Altiplano service graph connector.
| ---
title: Install and configure the Nokia Altiplano
description: Learn how to install and configure the Service Graph Connector for Nokia
Altiplano, including optional demo data, connectivity setup, and data collection
schedules.
keywords: []
breadcrumbs:
- Telecommunications Service Operations Management
- Configuring Telecommunications Service Operations Management
- Set up Telecom Visibility
- Configuring Nokia Altiplano service graph connector
---
# Install and configure the Nokia Altiplano
Learn how to install and configure the Service Graph Connector for Nokia Altiplano, including optional demo data, connectivity setup, and data collection schedules.
## Before you begin
Role required: admin
## About this task
Confirm you are operating in the Service Graph Connector for the Nokia Altiplano application scope. To switch to the Service Graph Connector for Nokia Altiplano scope:
1. Select the application picker (
) in the header.
2. Search for Nokia Altiplano.
3. Select Service Graph Connector for Nokia Altiplano from the list.
## Procedure
1. Navigate to All > Service Graph Connectors > Nokia Altiplano > Setup.
2. On the Getting started page, select Get Started.
The Guided Setup home page opens in a new tab.
3. (Optional)
Create and configure MID Server or skip based on your environment.
1. Select Configure to complete the process.
2. Follow the on-screen instructions to download and install.
3. Select Mark as Complete when done.
Note: For more information on how to install and configure MID Server, see Configuring MID Server.
4. Configure or skip the validation step.
5. Select Mark as Complete when validated.
Once all MID Server steps are complete, proceed to Configure Connectivity.
4. Create connection aliases, credentials, and HTTP connections to your Nokia Altiplano instance with Configure Connectivity
1. Select Get Started.
2. Create and configure aliases for the connections and credentials:
1. Select Configure.
2. In the Name field, specify the alias name.
3. Leave the rest of the fields as default, select Submit and then Mark as Complete.Note: This enables using the connection by name rather than directly, enabling the collector to extract all active aliases from the CMDB and start performing data collection on the HTTP connection bound to
it.
3. Create the credentials to access the Nokia Altiplano Controller by selecting Configure.
1. In the Name field, specify the alias name.
2. In the User name field, specify your Nokia Altiplano instance user name.
3. In the Password field, specify your Nokia Altiplano instance password.Note: Other authentication fields may be required depending on the authentication methods used in your Nokia
Altiplano instance. By default, we use Basic authentication credentials (as part of the Guided setup).
4. Leave the rest of the fields as default, select Submit and then select Mark as Complete.
4. Create HTTP Connection by selecting Configure
1. In the Name field, specify the connection name.
2. Choose the Credentials and Connection Alias created earlier.
3. Specify the Connection URL for Nokia Altiplano.
4. Check Use MID Server and choose either:
* Auto-select
* Specific MID Server
* Specific MID Cluster
5. Leave the rest of the fields as default, select Submit and then select Mark as Complete.
5. Configure Data Collection Schedule either for bulk discovery or filtered discovery by clicking Get Startedand then click Configure.
| To | Do the following |
| --- | --- |
| Schedule data collection for bulk discovery (Use bulk discovery data source for all devices in connection alias) | * Provide a Name for the scheduler. * Ensure the bulk data source SGC-Nokia Altipano Bulk Discovery is selected. * Set Active the scheduler automatically runs as mentioned in the Run and Time fields. If inactive, you must manually execute. * Select Use Connection. * In the Connection field, select connection alias. For example, sn\_sgc\_altiplano.Atiplano\_Alias. * In the Run field, select the frequency. Specify when you want this schedule to run: Daily, Weekly, Monthly, Periodically, After Parent Runs, or Once. * In the Time field, enter the time in hours, minutes, and seconds. |
| Schedule data collection for filtered discovery (Use Filtering Discovery data source for specific OLT filter criteria for each connection alias) | 1. Add Filtering Parameters 1. In the Connection Alias field, choose a connection alias. 2. Optionally, in the Filtered IPs field, add IP filters in various formats defined as following: * Single IP: `10.10.10.10` * List: `10.10.10.10, 10.10.10.20` * Ranges: `10.10.10.30-10.10.10.40` * CIDR: `10.10.10.0/24` * Mask: `10.10.10.0:255.255.255.0` 3. Optionally, add name filters to search by device name or part of the name. You can specify a single string or a list of names to filter the results. 2. Schedule filtered Collection * Provide a Name for the scheduler. * Ensure the data source SGC-Nokia Altipano Filtering Discovery is selected. * Set Active the scheduler automatically runs as mentioned in the Run and Time fields. If inactive, you must manually execute. * In the Run field, select the frequency. Specify when you want this schedule to run: Daily, Weekly, Monthly, Periodically, After Parent Runs, or Once. * In the Time field, enter the time in hours, minutes, and seconds. * Select Use Connection.. * In the Connection field, select connection alias. For example, sn\_sgc\_altiplano.Atiplano\_Alias. |
6. Select Submit and then select Mark as Complete.
### Result
The configured connections, aliases, credentials, and import schedules can also be accessed from the navigation Navigate to All > Service Graph Connectors > Nokia Altiplano.
The following snapshot helps you confirm the configuration set up of Nokia Altiplano service graph connector.
|
https://www.servicenow.com/docs/en-US/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/install-horizontal-telecommunication-discoverypatterns.html | https://servicenow-be-prod.servicenow.com/api/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/install-horizontal-telecommunication-discoverypatterns.html | 2025-08-02 | daily | 0.5 | 268.xml | en-US | zurich-telecom-service-ops | product/tmt-telecom-service-operations-mgt/task/install-horizontal-telecommunication-discoverypatterns.html | zurich | Install Horizontal Discovery and set up Discovery Patterns | Install Horizontal Discovery patterns understanding the dependencies and requirements. | [] | [
"Telecommunications Service Operations Management",
"Configuring Telecommunications Service Operations Management",
"Set up Telecom Visibility"
] | <article class="hascomments" data-page="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/install-horizontal-telecommunication-discoverypatterns.html" id="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/install-horizontal-telecommunication-discoverypatterns.html"><body id="install-horizontal-telecommunication-discoverypatterns"><main role="main"><article role="article" class="dita" id="install-horizontal-telecommunication-discoverypatterns" aria-labelledby="title_install-horizontal-telecommunication-discoverypatterns">
<h1 class="title topictitle1" id="title_install-horizontal-telecommunication-discoverypatterns">Install Horizontal Discovery and set up Discovery Patterns</h1>
<div class="body taskbody"><p class="shortdesc">Install Horizontal Discovery patterns understanding the dependencies and requirements.</p>
<section class="section prereq" id="install-horizontal-telecommunication-discoverypatterns__task-prereq"><div class="tasklabel"><p class="sectiontitle tasklabel">Before you begin</p></div>
<p class="p">Role required: admin</p>
<p class="p">Ensure you have a subscription to TSOM.</p>
</section>
<section class="section context" id="install-horizontal-telecommunication-discoverypatterns__context_adx_xm3_vfc"><div class="tasklabel"><p class="sectiontitle tasklabel">About this task</p></div>
<p class="p" id="install-horizontal-telecommunication-discoverypatterns__p_c21_nfg_h1c"><span class="ph" id="install-horizontal-telecommunication-discoverypatterns__inline-send-to-store">Visit the <a class="xref true-external" href="https://store.servicenow.com/sn_appstore_store.do#!/store/home" target="_blank"><span class="ph">ServiceNow Store</span></a> 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 <a class="xref" href="https://docs.servicenow.com/bundle/store-release-notes/page/release-notes/store/sn-store-release-notes.html"><span class="ph">ServiceNow Store</span> version history release notes</a>.</span></p>
<div class="p">Dependencies and Requirements:<ul class="ul" id="install-horizontal-telecommunication-discoverypatterns__ul_ofl_zy5_zdc">
<li class="li">Telecom Core (sn_tsom_core)</li>
<li class="li">Discovery Core plugin (com.snc.discovery.core), which is automatically installed by Discovery.</li>
<li class="li">ITOM Discovery License plugin (com.snc.itom.discovery.license). You must activate this plugin.</li>
<li class="li">ITOM Licensing plugin (com.snc.itom.license). For more information, see <a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/task//csh" href="https://servicenow-be-prod.servicenow.com/csh?topicname=t_ActivateTheDiscoveryPlugin&version=zurich&pubname=zurich-it-operations-management" class="xref">Request Discovery</a>.</li>
</ul></div>
<div class="p">Pattern execution logic: By default, when a TSOM pattern is run, it executes both the TSOM-specific and the corresponding ITOM pattern (e.g., Telco Router runs Router). This ensures shared ITOM libraries are reused when
needed. To override this behavior:<ul class="ul" id="install-horizontal-telecommunication-discoverypatterns__ul_cnc_gzy_5fc">
<li class="li">Use the system property <code class="ph codeph">sn_tsom_patterns.itom_pattern_enabled</code>.</li>
<li class="li">Setting this property to false ensures only the TSOM-specific pattern is executed.</li>
</ul></div>
</section>
<section><div class="tasklabel"><p class="sectiontitle tasklabel">Procedure</p></div><ol class="ol steps"><li class="li step stepexpand">
<span class="ph cmd">Install the Horizontal Discovery application.</span>
<div class="itemgroup info">See <a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/task//csh" href="https://servicenow-be-prod.servicenow.com/csh?topicname=discovery-setup&version=zurich&pubname=zurich-it-operations-management" class="xref">Discovery setup</a>, as it is foundational for running Telecommunications Discovery Patterns.</div>
</li><li class="li step stepexpand">
<span class="ph cmd">Obtain and install Telecommunications Discovery Patterns:</span>
<ol type="a" class="ol substeps" id="install-horizontal-telecommunication-discoverypatterns__substeps_kxk_qqf_b2c">
<li class="li substep">
<span class="ph cmd">Install the Telecommunications Discovery Patterns (sn_tsom_patterns) from the <span class="ph">ServiceNow®</span> Store.</span>
</li>
</ol>
</li><li class="li step stepexpand">
<span class="ph cmd">Set up a MID Server and synchronization Patterns:</span>
<ol type="a" class="ol substeps" id="install-horizontal-telecommunication-discoverypatterns__substeps_hw1_tqf_b2c">
<li class="li substep substepexpand">
<span class="ph cmd">Synchronization the installed patterns with the appropriate MID Servers to confirm they’re ready for use:</span>
<div class="itemgroup info">
<ol class="ol" type="i" id="install-horizontal-telecommunication-discoverypatterns__ol_yq3_5qf_b2c">
<li class="li">Navigate to <span class="ph menucascade"><span class="ph uicontrol">Discovery</span><abbr> > </abbr><span class="ph uicontrol">MID Servers</span></span>.</li>
<li class="li">Select <span class="ph uicontrol">Pattern Sync to Mid</span>.</li>
</ol>
<div class="note note note_note"><span class="note__title">Note:</span> This action synchronizes both TSOM and ITOM patterns.<p class="p">For more information on how to configure a MID Server, see <a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/task//csh" href="https://servicenow-be-prod.servicenow.com/csh?topicname=configure-mid-server&version=zurich&pubname=zurich-servicenow-platform" class="xref">Configuring MID Server</a>.</p></div>
</div>
</li>
</ol>
</li><li class="li step stepexpand">
<span class="ph cmd">Configure TSOM System Properties:</span>
<ol type="a" class="ol substeps" id="install-horizontal-telecommunication-discoverypatterns__substeps_crq_drf_b2c">
<li class="li substep substepexpand">
<span class="ph cmd">Set the system property sn_tsom_patterns.itom_pattern_enabled to define the logic for whether to use only the TSOM Pattern or a combination of ITOM and TSOM patterns.</span>
<div class="itemgroup info">
<ol class="ol" type="i" id="install-horizontal-telecommunication-discoverypatterns__ol_x4j_frf_b2c">
<li class="li">Navigate to <span class="ph menucascade"><span class="ph uicontrol">All</span><abbr> > </abbr><span class="ph uicontrol">System Properties</span><abbr> > </abbr><span class="ph uicontrol">All Properties</span></span>.</li>
<li class="li">Select <span class="ph uicontrol">sn_tsom_patterns.itom_pattern_enabled</span>.</li>
<li class="li">Check that the Value is set to <span class="ph uicontrol">true</span> (default).</li>
</ol>
<p class="p">If you want TSOM to run only TSOM patterns and exclude ITOM patterns, set the Value to <span class="ph uicontrol">false</span>.</p>
<div class="note note note_note"><span class="note__title">Note:</span> The default setting is configured to use both TSOM and ITOM patterns.</div>
</div>
</li>
</ol>
</li><li class="li step stepexpand">
<span class="ph cmd">Enable the replacement of various ITOM patterns with TSOM patters on a specific MID Server:</span>
<div class="itemgroup info">
<p class="p">For example: The Telecom Router pattern replaces the Network Router pattern for a specific MID Server when <span class="ph uicontrol">mid.telecom.discovery.patterns.enabled</span> is set to true for that MID Server.</p>
</div>
<ol type="a" class="ol substeps" id="install-horizontal-telecommunication-discoverypatterns__substeps_dw1_prf_b2c">
<li class="li substep">
<span class="ph cmd">Go to the <span class="ph uicontrol">Filter Navigator</span> and type <span class="ph uicontrol">ecc_agent_config.list</span>.</span>
</li>
<li class="li substep">
<span class="ph cmd">Select <span class="ph uicontrol">mid.telecom.discovery.patterns.enabled</span> (each MID Server has this parameter).</span>
</li>
<li class="li substep">
<span class="ph cmd">Check that the Value is set to <span class="ph uicontrol">true</span>.</span>
</li>
</ol>
<div class="itemgroup info">
<p class="p">Repeat this configuration for each MID Server that you want to use for running TSOM patterns.</p>
</div>
</li></ol></section>
</div>
<nav role="navigation"></nav><nav role="navigation" class="tasksNavigation"></nav><nav role="navigation" class="related-links"><div class="col-md-4"><dt>Related concepts</dt><dd><ul><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/concept/telecom-discovery-using-telecommunication-discovery-pattern.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/telecom-discovery-using-telecommunication-discovery-pattern.html" class="link" title="The Telecommunications Discovery Patterns plugin (also known as TSOM Patterns) extends ServiceNow AI Platform Telecom Discovery to support direct discovery of standalone network elements—such as routers and switches—without relying on traditional network management systems. These patterns enable Communication Service Providers (CSPs) to identify and map multivendor xNFs using protocols like SNMP and CLI, with support for NETCONF.">Direct Discovery using Discovery Patterns</a></li></ul></dd></div></nav>
</article></main></body></article> | {
"attachments": {
"all_attachments": null,
"topic_attachments": []
},
"available_languages": [
"enus"
],
"breadcrumbs": [
{
"title": "Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html"
},
{
"title": "Configuring Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/configuring-tsom.html"
},
{
"title": "Set up Telecom Visibility",
"topic_id": "product/tmt-telecom-service-operations-mgt/task/configuring-tsom-visibility.html"
}
],
"breadcrumbs_html": "<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops\">Zurich Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html\">Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/configuring-tsom.html\">Configuring Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/configuring-tsom-visibility.html\">Set up Telecom Visibility</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<span class=\"active\">Install Horizontal Discovery and set up Discovery Patterns</span>",
"bundle_id": "zurich-telecom-service-ops",
"bundle_key": 2733,
"bundle_landing_page": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html",
"bundle_subtitle": null,
"bundle_title": "Zurich Telecommunications Service Operations Management",
"canonical_link": null,
"dates": {
"Added on": "2025-08-02T00:48:08.794016Z",
"Created on": "2025-01-11T00:00:00Z",
"Initial upload": "2025-07-30T22:24:33.519043Z",
"Updated on": "2025-07-31T00:00:00Z"
},
"dislike_url": "https://servicenow-be-prod.servicenow.com/dislike/55686977",
"dislikes": 0,
"es_archived_content": false,
"is_in_fav": false,
"is_liked": null,
"is_watched": false,
"keywords": [
" zurich zurich"
],
"labels": [
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "zurich",
"navtitle": "Zurich",
"outputclasses": [],
"subjectHeadId": "versions",
"subjectheadNavtitle": "Versions",
"visibility": "show-facet"
},
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "tsom",
"navtitle": "Telecommunications Service Operations Management",
"outputclasses": [],
"subjectHeadId": "products",
"subjectheadNavtitle": "Products",
"visibility": "show-facet"
}
],
"labels_text": "Versions > Zurich; Products > CRM and Industry Products > Telecommunications Media and Technology Assurance > Telecommunications Service Operations Management",
"like_url": "https://servicenow-be-prod.servicenow.com/like/55686977",
"likes": 0,
"metadata": {
"AI Search": null,
"AI Search Assist": null,
"Application Insights": null,
"Capabilities": null,
"Code Signing": null,
"Contextual Search": null,
"DC.contributor": null,
"DC.coverage": null,
"DC.creator": "ServiceNow",
"DC.date.created": "2025-01-11T22:13:34+05:30",
"DC.date.modified": "2025-07-31",
"DC.format": "HTML5",
"DC.identifier": "install-horizontal-telecommunication-discoverypatterns",
"DC.language": null,
"DC.relation": "../concept/telecom-discovery-using-telecommunication-discovery-pattern.html",
"DC.rights.owner": "(C) Copyright 2025",
"DC.subject": null,
"DC.type": "task",
"Data Discovery": null,
"Data Policy": null,
"Data Privacy": null,
"Discovery": null,
"External Content for AI Search": null,
"Field Administration": null,
"Field Normalization": null,
"Key Management Framework": null,
"Localization Framework": null,
"Now Platform": null,
"PlatSec": null,
"Platform": null,
"Platform Administration": null,
"Platform Performance": null,
"Platform Privacy": null,
"Proactive Triggers": null,
"Process Optimization": null,
"RN doc editing record number": null,
"Search Administration": null,
"Secrets Management": null,
"ServiceNow AI Platform": null,
"State Model": null,
"Subscription Management": null,
"Task Communications Management": null,
"Timeline Visualizations": null,
"User Administration": null,
"User Experience Analytics": null,
"Zing": null,
"ai-now-assist": null,
"app-name": null,
"app_route": null,
"azureapimanagemen": null,
"change-completed": null,
"change-item": null,
"change-request-id": null,
"change-request-reference": null,
"com.glide.embedded_help.category": null,
"component": null,
"copyright": "(C) Copyright 2025",
"crossroads": null,
"data": null,
"description": "Install Horizontal Discovery patterns understanding the dependencies and requirements.",
"dominant_bundle": null,
"erp-canvas-video": null,
"fsm-mobile": null,
"fsm-route": null,
"fsm-sched-opt": null,
"fsm-wrk-order": null,
"genai-round-7": null,
"generator": "DITA-OT",
"glossPartOfSpeech": null,
"glossStatus": null,
"guided setup": null,
"guided tours": null,
"keywords": null,
"min-toc": null,
"mini": null,
"mini-to truec": null,
"mini-toc": null,
"mini_toc": null,
"minitoc": null,
"modification": null,
"now-assist-app-gen-video": null,
"order": null,
"page-type": null,
"page-type ": null,
"prodname": null,
"product": null,
"product_name": null,
"release": null,
"resourceID": null,
"roles": null,
"route_page": null,
"route_params_listId": null,
"route_params_table": null,
"route_params_type": null,
"route_type": null,
"setconfigurationproperties": null,
"topic": null,
"translation-type": "source",
"version": null,
"workflow": "Customer and Industry",
"workplace-srvc-delvry-ditamap": null
},
"page_id": "product/tmt-telecom-service-operations-mgt/task/install-horizontal-telecommunication-discoverypatterns.html",
"page_key": 55686977,
"preprocessed_PDF": "https://downloads.docs.servicenow.com/pdf/enus/servicenow-zurich-telecom-service-ops-enus.pdf",
"rating": null,
"read_time_data": {
"char_count": 2930,
"img_count": 0,
"read_time": 2,
"video_links": [
""
],
"word_count": 418
},
"related_links": [
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "The Telecommunications Discovery Patterns plugin (also known as TSOM Patterns) extends ServiceNow AI Platform Telecom Discovery to support direct discovery of standalone network elements—such as routers and switches—without relying on traditional network management systems. These patterns enable Communication Service Providers (CSPs) to identify and map multivendor xNFs using protocols like SNMP and CLI, with support for NETCONF.",
"title": "Direct Discovery using Discovery Patterns",
"topic": "/product/tmt-telecom-service-operations-mgt/concept/telecom-discovery-using-telecommunication-discovery-pattern.html",
"type": "concept",
"url": null
}
],
"search_title": null,
"title": "Install Horizontal Discovery and set up Discovery Patterns",
"topic_cluster": {
"clustered_by": {
"enabled": true,
"primary_key": "versions",
"primary_sort": "top-down",
"type": "subjecthead"
},
"clustered_labels": [
"versions"
],
"clustered_topics": [],
"clustering_title": "Zurich"
},
"topic_html": "<article class=\"hascomments\" data-page=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/install-horizontal-telecommunication-discoverypatterns.html\" id=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/install-horizontal-telecommunication-discoverypatterns.html\"><body id=\"install-horizontal-telecommunication-discoverypatterns\"><main role=\"main\"><article role=\"article\" class=\"dita\" id=\"install-horizontal-telecommunication-discoverypatterns\" aria-labelledby=\"title_install-horizontal-telecommunication-discoverypatterns\">\n <h1 class=\"title topictitle1\" id=\"title_install-horizontal-telecommunication-discoverypatterns\">Install Horizontal Discovery and set up Discovery Patterns</h1>\n \n \n <div class=\"body taskbody\"><p class=\"shortdesc\">Install Horizontal Discovery patterns understanding the dependencies and requirements.</p>\n <section class=\"section prereq\" id=\"install-horizontal-telecommunication-discoverypatterns__task-prereq\"><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">Before you begin</p></div>\n <p class=\"p\">Role required: admin</p>\n <p class=\"p\">Ensure you have a subscription to TSOM.</p>\n </section>\n <section class=\"section context\" id=\"install-horizontal-telecommunication-discoverypatterns__context_adx_xm3_vfc\"><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">About this task</p></div>\n <p class=\"p\" id=\"install-horizontal-telecommunication-discoverypatterns__p_c21_nfg_h1c\"><span class=\"ph\" id=\"install-horizontal-telecommunication-discoverypatterns__inline-send-to-store\">Visit the <a class=\"xref true-external\" href=\"https://store.servicenow.com/sn_appstore_store.do#!/store/home\" target=\"_blank\"><span class=\"ph\">ServiceNow Store</span></a> 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 <a class=\"xref\" href=\"https://docs.servicenow.com/bundle/store-release-notes/page/release-notes/store/sn-store-release-notes.html\"><span class=\"ph\">ServiceNow Store</span> version history release notes</a>.</span></p>\n <div class=\"p\">Dependencies and Requirements:<ul class=\"ul\" id=\"install-horizontal-telecommunication-discoverypatterns__ul_ofl_zy5_zdc\">\n <li class=\"li\">Telecom Core (sn_tsom_core)</li>\n <li class=\"li\">Discovery Core plugin (com.snc.discovery.core), which is automatically installed by Discovery.</li>\n <li class=\"li\">ITOM Discovery License plugin (com.snc.itom.discovery.license). You must activate this plugin.</li>\n <li class=\"li\">ITOM Licensing plugin (com.snc.itom.license). For more information, see <a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/task//csh\" href=\"https://servicenow-be-prod.servicenow.com/csh?topicname=t_ActivateTheDiscoveryPlugin&version=zurich&pubname=zurich-it-operations-management\" class=\"xref\">Request Discovery</a>.</li>\n </ul></div>\n <div class=\"p\">Pattern execution logic: By default, when a TSOM pattern is run, it executes both the TSOM-specific and the corresponding ITOM pattern (e.g., Telco Router runs Router). This ensures shared ITOM libraries are reused when\n needed. To override this behavior:<ul class=\"ul\" id=\"install-horizontal-telecommunication-discoverypatterns__ul_cnc_gzy_5fc\">\n <li class=\"li\">Use the system property <code class=\"ph codeph\">sn_tsom_patterns.itom_pattern_enabled</code>.</li>\n <li class=\"li\">Setting this property to false ensures only the TSOM-specific pattern is executed.</li>\n </ul></div>\n </section>\n <section><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">Procedure</p></div><ol class=\"ol steps\"><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">Install the Horizontal Discovery application.</span>\n <div class=\"itemgroup info\">See <a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/task//csh\" href=\"https://servicenow-be-prod.servicenow.com/csh?topicname=discovery-setup&version=zurich&pubname=zurich-it-operations-management\" class=\"xref\">Discovery setup</a>, as it is foundational for running Telecommunications Discovery Patterns.</div>\n </li><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">Obtain and install Telecommunications Discovery Patterns:</span>\n <ol type=\"a\" class=\"ol substeps\" id=\"install-horizontal-telecommunication-discoverypatterns__substeps_kxk_qqf_b2c\">\n <li class=\"li substep\">\n <span class=\"ph cmd\">Install the Telecommunications Discovery Patterns (sn_tsom_patterns) from the <span class=\"ph\">ServiceNow®</span> Store.</span>\n </li>\n </ol>\n </li><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">Set up a MID Server and synchronization Patterns:</span>\n <ol type=\"a\" class=\"ol substeps\" id=\"install-horizontal-telecommunication-discoverypatterns__substeps_hw1_tqf_b2c\">\n <li class=\"li substep substepexpand\">\n <span class=\"ph cmd\">Synchronization the installed patterns with the appropriate MID Servers to confirm they’re ready for use:</span>\n <div class=\"itemgroup info\">\n <ol class=\"ol\" type=\"i\" id=\"install-horizontal-telecommunication-discoverypatterns__ol_yq3_5qf_b2c\">\n <li class=\"li\">Navigate to <span class=\"ph menucascade\"><span class=\"ph uicontrol\">Discovery</span><abbr> > </abbr><span class=\"ph uicontrol\">MID Servers</span></span>.</li>\n <li class=\"li\">Select <span class=\"ph uicontrol\">Pattern Sync to Mid</span>.</li>\n </ol>\n <div class=\"note note note_note\"><span class=\"note__title\">Note:</span> This action synchronizes both TSOM and ITOM patterns.<p class=\"p\">For more information on how to configure a MID Server, see <a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/task//csh\" href=\"https://servicenow-be-prod.servicenow.com/csh?topicname=configure-mid-server&version=zurich&pubname=zurich-servicenow-platform\" class=\"xref\">Configuring MID Server</a>.</p></div>\n </div>\n </li>\n </ol>\n </li><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">Configure TSOM System Properties:</span>\n <ol type=\"a\" class=\"ol substeps\" id=\"install-horizontal-telecommunication-discoverypatterns__substeps_crq_drf_b2c\">\n <li class=\"li substep substepexpand\">\n <span class=\"ph cmd\">Set the system property sn_tsom_patterns.itom_pattern_enabled to define the logic for whether to use only the TSOM Pattern or a combination of ITOM and TSOM patterns.</span>\n <div class=\"itemgroup info\">\n <ol class=\"ol\" type=\"i\" id=\"install-horizontal-telecommunication-discoverypatterns__ol_x4j_frf_b2c\">\n <li class=\"li\">Navigate to <span class=\"ph menucascade\"><span class=\"ph uicontrol\">All</span><abbr> > </abbr><span class=\"ph uicontrol\">System Properties</span><abbr> > </abbr><span class=\"ph uicontrol\">All Properties</span></span>.</li>\n <li class=\"li\">Select <span class=\"ph uicontrol\">sn_tsom_patterns.itom_pattern_enabled</span>.</li>\n <li class=\"li\">Check that the Value is set to <span class=\"ph uicontrol\">true</span> (default).</li>\n </ol>\n <p class=\"p\">If you want TSOM to run only TSOM patterns and exclude ITOM patterns, set the Value to <span class=\"ph uicontrol\">false</span>.</p>\n <div class=\"note note note_note\"><span class=\"note__title\">Note:</span> The default setting is configured to use both TSOM and ITOM patterns.</div>\n </div>\n </li>\n </ol>\n </li><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">Enable the replacement of various ITOM patterns with TSOM patters on a specific MID Server:</span>\n <div class=\"itemgroup info\">\n <p class=\"p\">For example: The Telecom Router pattern replaces the Network Router pattern for a specific MID Server when <span class=\"ph uicontrol\">mid.telecom.discovery.patterns.enabled</span> is set to true for that MID Server.</p>\n </div>\n <ol type=\"a\" class=\"ol substeps\" id=\"install-horizontal-telecommunication-discoverypatterns__substeps_dw1_prf_b2c\">\n <li class=\"li substep\">\n <span class=\"ph cmd\">Go to the <span class=\"ph uicontrol\">Filter Navigator</span> and type <span class=\"ph uicontrol\">ecc_agent_config.list</span>.</span>\n </li>\n <li class=\"li substep\">\n <span class=\"ph cmd\">Select <span class=\"ph uicontrol\">mid.telecom.discovery.patterns.enabled</span> (each MID Server has this parameter).</span>\n </li>\n <li class=\"li substep\">\n <span class=\"ph cmd\">Check that the Value is set to <span class=\"ph uicontrol\">true</span>.</span>\n </li>\n </ol>\n <div class=\"itemgroup info\">\n <p class=\"p\">Repeat this configuration for each MID Server that you want to use for running TSOM patterns.</p>\n </div>\n </li></ol></section>\n </div>\n <nav role=\"navigation\"></nav><nav role=\"navigation\" class=\"tasksNavigation\"></nav><nav role=\"navigation\" class=\"related-links\"><div class=\"col-md-4\"><dt>Related concepts</dt><dd><ul><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept/telecom-discovery-using-telecommunication-discovery-pattern.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/telecom-discovery-using-telecommunication-discovery-pattern.html\" class=\"link\" title=\"The Telecommunications Discovery Patterns plugin (also known as TSOM Patterns) extends ServiceNow AI Platform Telecom Discovery to support direct discovery of standalone network elements—such as routers and switches—without relying on traditional network management systems. These patterns enable Communication Service Providers (CSPs) to identify and map multivendor xNFs using protocols like SNMP and CLI, with support for NETCONF.\">Direct Discovery using Discovery Patterns</a></li></ul></dd></div></nav>\n</article></main></body></article>",
"topic_language": "enus",
"views": 0,
"your_rating": null
} | # Install Horizontal Discovery and set up Discovery Patterns
Install Horizontal Discovery patterns understanding the dependencies and requirements.
## Before you begin
Role required: admin
Ensure you have a subscription to TSOM.
## About this task
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:
* Telecom Core (sn\_tsom\_core)
* 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.
Pattern execution logic: By default, when a TSOM pattern is run, it executes both the TSOM-specific and the corresponding ITOM pattern (e.g., Telco Router runs Router). This ensures shared ITOM libraries are reused when
needed. To override this behavior:
* Use the system property `sn_tsom_patterns.itom_pattern_enabled`.
* Setting this property to false ensures only the TSOM-specific pattern is executed.
## Procedure
1. Install the Horizontal Discovery application.
See Discovery setup, as it is foundational for running Telecommunications Discovery Patterns.
2. Obtain and install Telecommunications Discovery Patterns:
1. Install the Telecommunications Discovery Patterns (sn\_tsom\_patterns) from the ServiceNow® Store.
3. Set up a MID Server and synchronization Patterns:
1. Synchronization the installed patterns with the appropriate MID Servers to confirm they’re ready for use:
1. Navigate to Discovery > MID Servers.
2. Select Pattern Sync to Mid.Note: This action synchronizes both TSOM and ITOM patterns.
For more information on how to configure a MID Server, see Configuring MID Server.
4. Configure TSOM System Properties:
1. Set the system property sn\_tsom\_patterns.itom\_pattern\_enabled to define the logic for whether to use only the TSOM Pattern or a combination of ITOM and TSOM patterns.
1. Navigate to All > System Properties > All Properties.
2. Select sn\_tsom\_patterns.itom\_pattern\_enabled.
3. Check that the Value is set to true (default).
If you want TSOM to run only TSOM patterns and exclude ITOM patterns, set the Value to false.
Note: The default setting is configured to use both TSOM and ITOM patterns.
5. Enable the replacement of various ITOM patterns with TSOM patters on a specific MID Server:
For example: The Telecom Router pattern replaces the Network Router pattern for a specific MID Server when mid.telecom.discovery.patterns.enabled is set to true for that MID Server.
1. Go to the Filter Navigator and type ecc\_agent\_config.list.
2. Select mid.telecom.discovery.patterns.enabled (each MID Server has this parameter).
3. Check that the Value is set to true.
Repeat this configuration for each MID Server that you want to use for running TSOM patterns.
| ---
title: Install Horizontal Discovery and set up Discovery Patterns
description: Install Horizontal Discovery patterns understanding the dependencies
and requirements.
keywords: []
breadcrumbs:
- Telecommunications Service Operations Management
- Configuring Telecommunications Service Operations Management
- Set up Telecom Visibility
---
# Install Horizontal Discovery and set up Discovery Patterns
Install Horizontal Discovery patterns understanding the dependencies and requirements.
## Before you begin
Role required: admin
Ensure you have a subscription to TSOM.
## About this task
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:
* Telecom Core (sn\_tsom\_core)
* 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.
Pattern execution logic: By default, when a TSOM pattern is run, it executes both the TSOM-specific and the corresponding ITOM pattern (e.g., Telco Router runs Router). This ensures shared ITOM libraries are reused when
needed. To override this behavior:
* Use the system property `sn_tsom_patterns.itom_pattern_enabled`.
* Setting this property to false ensures only the TSOM-specific pattern is executed.
## Procedure
1. Install the Horizontal Discovery application.
See Discovery setup, as it is foundational for running Telecommunications Discovery Patterns.
2. Obtain and install Telecommunications Discovery Patterns:
1. Install the Telecommunications Discovery Patterns (sn\_tsom\_patterns) from the ServiceNow® Store.
3. Set up a MID Server and synchronization Patterns:
1. Synchronization the installed patterns with the appropriate MID Servers to confirm they’re ready for use:
1. Navigate to Discovery > MID Servers.
2. Select Pattern Sync to Mid.Note: This action synchronizes both TSOM and ITOM patterns.
For more information on how to configure a MID Server, see Configuring MID Server.
4. Configure TSOM System Properties:
1. Set the system property sn\_tsom\_patterns.itom\_pattern\_enabled to define the logic for whether to use only the TSOM Pattern or a combination of ITOM and TSOM patterns.
1. Navigate to All > System Properties > All Properties.
2. Select sn\_tsom\_patterns.itom\_pattern\_enabled.
3. Check that the Value is set to true (default).
If you want TSOM to run only TSOM patterns and exclude ITOM patterns, set the Value to false.
Note: The default setting is configured to use both TSOM and ITOM patterns.
5. Enable the replacement of various ITOM patterns with TSOM patters on a specific MID Server:
For example: The Telecom Router pattern replaces the Network Router pattern for a specific MID Server when mid.telecom.discovery.patterns.enabled is set to true for that MID Server.
1. Go to the Filter Navigator and type ecc\_agent\_config.list.
2. Select mid.telecom.discovery.patterns.enabled (each MID Server has this parameter).
3. Check that the Value is set to true.
Repeat this configuration for each MID Server that you want to use for running TSOM patterns.
|
https://www.servicenow.com/docs/en-US/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/multi-instance-setup.html | https://servicenow-be-prod.servicenow.com/api/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/multi-instance-setup.html | 2025-08-02 | daily | 0.5 | 268.xml | en-US | zurich-telecom-service-ops | product/tmt-telecom-service-operations-mgt/task/multi-instance-setup.html | zurich | Set up multiple Nokia Altiplano instances | Learn how to configure and manage multiple Nokia Altiplano instances within a single ServiceNow environment. This enables administrators and integrators to create independent connection aliases and import schedules customized to specific filtering or frequency needs. | [] | [
"Telecommunications Service Operations Management",
"Configuring Telecommunications Service Operations Management",
"Set up Telecom Visibility",
"Configuring Nokia Altiplano service graph connector"
] | <article class="hascomments" data-page="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/multi-instance-setup.html" id="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/multi-instance-setup.html"><body id="multi-instance-setup"><main role="main"><article role="article" class="dita" id="multi-instance-setup" aria-labelledby="title_multi-instance-setup">
<h1 class="title topictitle1" id="title_multi-instance-setup">Set up multiple Nokia Altiplano instances</h1>
<div class="body taskbody"><p class="shortdesc">Learn how to configure and manage multiple Nokia Altiplano instances within a single ServiceNow environment. This enables administrators and integrators to create independent connection aliases and import schedules customized
to specific filtering or frequency needs.</p>
<section class="section prereq" id="multi-instance-setup__task-prereq"><div class="tasklabel"><p class="sectiontitle tasklabel">Before you begin</p></div>
<p class="p">Role required: admin</p>
</section>
<section class="section context" id="multi-instance-setup__context_utx_skt_xfc"><div class="tasklabel"><p class="sectiontitle tasklabel">About this task</p></div>
<p class="p">Confirm you have:</p>
<ul class="ul" id="multi-instance-setup__ul_zvj_dsc_zfc">
<li class="li">You’re operating in the Service Graph Connector for NOKIA Altiplano application scope.</li>
<li class="li">Installed the Service Graph Connector for Nokia Altiplano.</li>
<li class="li">Completed the guided setup for the initial Altiplano instance.</li>
<li class="li">MID Server set up and validated.</li>
</ul>
<p class="p">You can configure additional Nokia Altiplano instances or reuse the same Altiplano instance with different connection aliases and import schedules. To add a new Altiplano instance, rerun the Guided setup to configure a new
connection alias. Go through all connectivity stages in the setup for each new alias.</p>
</section>
<section><div class="tasklabel"><p class="sectiontitle tasklabel">Procedure</p></div><ol class="ol steps"><li class="li step stepexpand">
<span class="ph cmd">Navigate to <span class="ph menucascade"><span class="ph uicontrol">All</span><abbr> > </abbr><span class="ph uicontrol">Service Graph Connectors</span><abbr> > </abbr><span class="ph uicontrol">Nokia Altiplano</span><abbr> > </abbr><span class="ph uicontrol">Setup</span></span>.</span>
</li><li class="li step stepexpand">
<span class="ph cmd">On the Getting Started page, select <span class="ph uicontrol">Get Started</span>.</span>
<div class="itemgroup info">Repeat all the steps under the Configured Connectivity section. It creates configuration entries for the new instance of Nokia Altiplano. For more information, see <a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/task/initial-setup-procedure.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/initial-setup-procedure.html" class="xref" title="Learn how to install and configure the Service Graph Connector for Nokia Altiplano, including optional demo data, connectivity setup, and data collection schedules.">Install and configure the Nokia Altiplano</a>.</div>
</li><li class="li step stepexpand">
<span class="ph cmd">Configure the connectivity by creating a connection alias, credentials, and HTTP connection.</span>
<ol type="a" class="ol substeps" id="multi-instance-setup__substeps_xxy_4sc_zfc">
<li class="li substep">
<span class="ph cmd">In the Configure Connectivity section, select Get Started.</span>
</li>
<li class="li substep">
<span class="ph cmd">Select Configure to create a new connection alias by entering a unique alias name (for example, <code class="ph codeph">Altiplano_Prod_01</code>).</span>
</li>
<li class="li substep">
<span class="ph cmd">Select <span class="ph uicontrol">Submit</span> and mark the step as complete.</span>
</li>
</ol>
</li><li class="li step stepexpand">
<span class="ph cmd">Configure credentials for the new Altiplano instance.</span>
<ol type="a" class="ol substeps" id="multi-instance-setup__substeps_djn_2tc_zfc">
<li class="li substep">
<span class="ph cmd">Specify a user name and password for the Altiplano Controller.</span>
</li>
<li class="li substep">
<span class="ph cmd">Submit and mark the step as complete.</span>
</li>
</ol>
</li><li class="li step stepexpand">
<span class="ph cmd">Configure an HTTP connection.</span>
<ol type="a" class="ol substeps" id="multi-instance-setup__substeps_mzt_gtc_zfc">
<li class="li substep">
<span class="ph cmd">Provide the connection name.</span>
</li>
<li class="li substep">
<span class="ph cmd">Select the newly created credentials and connection alias.</span>
</li>
<li class="li substep">
<span class="ph cmd">Enter the connection URL of the Nokia Altiplano instance.</span>
</li>
<li class="li substep">
<span class="ph cmd">Enable use MID Server and choose the appropriate MID option.</span>
</li>
<li class="li substep">
<span class="ph cmd">Select <span class="ph uicontrol">Submit</span> and mark the step as complete.</span>
</li>
</ol>
</li><li class="li step stepexpand">
<span class="ph cmd">Schedule data imports using either bulk or filtered discovery by configuring the import schedule.</span>
<ol type="a" class="ol substeps" id="multi-instance-setup__substeps_qhs_45c_zfc">
<li class="li substep substepexpand">
<span class="ph cmd">Fill in the fields.</span>
<div class="itemgroup info">For more information, see <a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/task/initial-setup-procedure.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/initial-setup-procedure.html" class="xref" title="Learn how to install and configure the Service Graph Connector for Nokia Altiplano, including optional demo data, connectivity setup, and data collection schedules.">Install and configure the Nokia Altiplano</a>.</div>
</li>
<li class="li substep substepexpand">
<span class="ph cmd">In the <span class="ph uicontrol">Use connection</span> field, choose the new Altiplano instance.</span>
</li>
</ol>
</li><li class="li step stepexpand">
<span class="ph cmd">Select <span class="ph uicontrol">Submit</span>.</span>
</li></ol></section>
<section class="section result" id="multi-instance-setup__result_o5z_55c_zfc"><div class="tasklabel"><p class="sectiontitle tasklabel">Result</p></div>
<div class="p">To confirm that your new instance setup is successful, you can verify the configuration.<ul class="ul" id="multi-instance-setup__ul_t3z_gvc_zfc">
<li class="li">Navigate to All > Service Graph Connectors > Nokia Altiplano > Connection Aliases and confirm that the new alias is listed.</li>
<li class="li">Navigate to All > Service Graph Connectors > Nokia Altiplano > Import Schedule and confirm that the new import schedule is listed and confirm that corresponding jobs exist for each alias.</li>
</ul></div>
<p class="p">You can configure multiple connection aliases hovering the same Nokia Altiplano instance. This flexibility enables you to run imports at different frequencies and apply different filters to each alias.</p>
<p class="p">Example: Altiplano_Weekly_OLT_10.10.10.*: Runs weekly, filters OLTs with IPs in the 10.10.10.* range. Altiplano_Daily_Prod: Runs daily, filters OLTs whose name contains "prod_olt".</p>
</section>
</div>
<nav role="navigation"></nav><nav role="navigation" class="tasksNavigation"></nav><nav role="navigation" class="related-links"><div class="col-md-4"><dt>Related tasks</dt><dd><ul><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/task/configure-concurrent-import-and-parallel-loading.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/configure-concurrent-import-and-parallel-loading.html" class="link" title="Improve the efficiency of large data imports from Nokia Altiplano by configuring concurrent imports and enabling parallel loading. This configuration allows the platform to run multiple data import and transformation jobs simultaneously.">Configure concurrent import and parallel loading for Nokia Altiplano</a></li></ul></dd></div><div class="col-md-4"><dt>Related concepts</dt><dd><ul><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/concept/data-mapping.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/data-mapping.html" class="link" title="Use the Service Graph Connector for Nokia Altiplano to map discovered physical and logical network resources to telecom-aligned Configuration Item (CI) classes in the CMDB. The connector supports consistent service modeling, visibility into chassis-level components, and automation of logical and physical relationships.">Mapping Nokia Altiplano CIs and Relationships in CMDB</a></li></ul></dd></div><div class="col-md-4"><dt>Related reference</dt><dd><ul><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/reference/properties-installed-with-nokia-altiplano.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/reference/properties-installed-with-nokia-altiplano.html" class="link" title="System properties control how the connector operates, including discovery options and performance settings.">System components installed with Nokia Altiplano</a></li></ul></dd></div></nav>
</article></main></body></article> | {
"attachments": {
"all_attachments": null,
"topic_attachments": []
},
"available_languages": [
"enus"
],
"breadcrumbs": [
{
"title": "Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html"
},
{
"title": "Configuring Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/configuring-tsom.html"
},
{
"title": "Set up Telecom Visibility",
"topic_id": "product/tmt-telecom-service-operations-mgt/task/configuring-tsom-visibility.html"
},
{
"title": "Configuring Nokia Altiplano service graph connector",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/configuring-service-graph-connector-nokia-altiplano.html"
}
],
"breadcrumbs_html": "<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops\">Zurich Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html\">Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/configuring-tsom.html\">Configuring Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/configuring-tsom-visibility.html\">Set up Telecom Visibility</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/configuring-service-graph-connector-nokia-altiplano.html\">Configuring Nokia Altiplano service graph connector</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<span class=\"active\">Set up multiple Nokia Altiplano instances</span>",
"bundle_id": "zurich-telecom-service-ops",
"bundle_key": 2733,
"bundle_landing_page": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html",
"bundle_subtitle": null,
"bundle_title": "Zurich Telecommunications Service Operations Management",
"canonical_link": null,
"dates": {
"Added on": "2025-08-02T00:48:08.794016Z",
"Created on": "2025-01-15T00:00:00Z",
"Initial upload": "2025-07-30T22:24:33.519043Z",
"Updated on": "2025-07-31T00:00:00Z"
},
"dislike_url": "https://servicenow-be-prod.servicenow.com/dislike/55686978",
"dislikes": 0,
"es_archived_content": false,
"is_in_fav": false,
"is_liked": null,
"is_watched": false,
"keywords": [
" zurich zurich"
],
"labels": [
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "zurich",
"navtitle": "Zurich",
"outputclasses": [],
"subjectHeadId": "versions",
"subjectheadNavtitle": "Versions",
"visibility": "show-facet"
},
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "tsom",
"navtitle": "Telecommunications Service Operations Management",
"outputclasses": [],
"subjectHeadId": "products",
"subjectheadNavtitle": "Products",
"visibility": "show-facet"
}
],
"labels_text": "Versions > Zurich; Products > CRM and Industry Products > Telecommunications Media and Technology Assurance > Telecommunications Service Operations Management",
"like_url": "https://servicenow-be-prod.servicenow.com/like/55686978",
"likes": 0,
"metadata": {
"AI Search": null,
"AI Search Assist": null,
"Application Insights": null,
"Capabilities": null,
"Code Signing": null,
"Contextual Search": null,
"DC.contributor": null,
"DC.coverage": null,
"DC.creator": "ServiceNow",
"DC.date.created": "2025-01-15T22:51:54+05:30",
"DC.date.modified": "2025-07-31",
"DC.format": "HTML5",
"DC.identifier": "multi-instance-setup",
"DC.language": null,
"DC.relation": "configure-concurrent-import-and-parallel-loading.html",
"DC.rights.owner": "(C) Copyright 2025",
"DC.subject": null,
"DC.type": "task",
"Data Discovery": null,
"Data Policy": null,
"Data Privacy": null,
"Discovery": null,
"External Content for AI Search": null,
"Field Administration": null,
"Field Normalization": null,
"Key Management Framework": null,
"Localization Framework": null,
"Now Platform": null,
"PlatSec": null,
"Platform": null,
"Platform Administration": null,
"Platform Performance": null,
"Platform Privacy": null,
"Proactive Triggers": null,
"Process Optimization": null,
"RN doc editing record number": null,
"Search Administration": null,
"Secrets Management": null,
"ServiceNow AI Platform": null,
"State Model": null,
"Subscription Management": null,
"Task Communications Management": null,
"Timeline Visualizations": null,
"User Administration": null,
"User Experience Analytics": null,
"Zing": null,
"ai-now-assist": null,
"app-name": null,
"app_route": null,
"azureapimanagemen": null,
"change-completed": null,
"change-item": null,
"change-request-id": null,
"change-request-reference": null,
"com.glide.embedded_help.category": null,
"component": null,
"copyright": "(C) Copyright 2025",
"crossroads": null,
"data": null,
"description": "Learn how to configure and manage multiple Nokia Altiplano instances within a single ServiceNow environment. This enables administrators and integrators to create independent connection aliases and import schedules customized to specific filtering or frequency needs.",
"dominant_bundle": null,
"erp-canvas-video": null,
"fsm-mobile": null,
"fsm-route": null,
"fsm-sched-opt": null,
"fsm-wrk-order": null,
"genai-round-7": null,
"generator": "DITA-OT",
"glossPartOfSpeech": null,
"glossStatus": null,
"guided setup": null,
"guided tours": null,
"keywords": null,
"min-toc": null,
"mini": null,
"mini-to truec": null,
"mini-toc": null,
"mini_toc": null,
"minitoc": null,
"modification": null,
"now-assist-app-gen-video": null,
"order": null,
"page-type": null,
"page-type ": null,
"prodname": null,
"product": null,
"product_name": null,
"release": null,
"resourceID": null,
"roles": null,
"route_page": null,
"route_params_listId": null,
"route_params_table": null,
"route_params_type": null,
"route_type": null,
"setconfigurationproperties": null,
"topic": null,
"translation-type": "source",
"version": null,
"workflow": "Customer and Industry",
"workplace-srvc-delvry-ditamap": null
},
"page_id": "product/tmt-telecom-service-operations-mgt/task/multi-instance-setup.html",
"page_key": 55686978,
"preprocessed_PDF": "https://downloads.docs.servicenow.com/pdf/enus/servicenow-zurich-telecom-service-ops-enus.pdf",
"rating": null,
"read_time_data": {
"char_count": 3063,
"img_count": 0,
"read_time": 2,
"video_links": [
""
],
"word_count": 456
},
"related_links": [
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "Improve the efficiency of large data imports from Nokia Altiplano by configuring concurrent imports and enabling parallel loading. This configuration allows the platform to run multiple data import and transformation jobs simultaneously.",
"title": "Configure concurrent import and parallel loading for Nokia Altiplano",
"topic": "/product/tmt-telecom-service-operations-mgt/task/configure-concurrent-import-and-parallel-loading.html",
"type": "task",
"url": null
},
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "Use the Service Graph Connector for Nokia Altiplano to map discovered physical and logical network resources to telecom-aligned Configuration Item (CI) classes in the CMDB. The connector supports consistent service modeling, visibility into chassis-level components, and automation of logical and physical relationships.",
"title": "Mapping Nokia Altiplano CIs and Relationships in CMDB",
"topic": "/product/tmt-telecom-service-operations-mgt/concept/data-mapping.html",
"type": "concept",
"url": null
},
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "System properties control how the connector operates, including discovery options and performance settings.",
"title": "System components installed with Nokia Altiplano",
"topic": "/product/tmt-telecom-service-operations-mgt/reference/properties-installed-with-nokia-altiplano.html",
"type": "reference",
"url": null
}
],
"search_title": null,
"title": "Set up multiple Nokia Altiplano instances",
"topic_cluster": {
"clustered_by": {
"enabled": true,
"primary_key": "versions",
"primary_sort": "top-down",
"type": "subjecthead"
},
"clustered_labels": [
"versions"
],
"clustered_topics": [],
"clustering_title": "Zurich"
},
"topic_html": "<article class=\"hascomments\" data-page=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/multi-instance-setup.html\" id=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/multi-instance-setup.html\"><body id=\"multi-instance-setup\"><main role=\"main\"><article role=\"article\" class=\"dita\" id=\"multi-instance-setup\" aria-labelledby=\"title_multi-instance-setup\">\n <h1 class=\"title topictitle1\" id=\"title_multi-instance-setup\">Set up multiple Nokia Altiplano instances</h1>\n \n \n <div class=\"body taskbody\"><p class=\"shortdesc\">Learn how to configure and manage multiple Nokia Altiplano instances within a single ServiceNow environment. This enables administrators and integrators to create independent connection aliases and import schedules customized\n to specific filtering or frequency needs.</p>\n <section class=\"section prereq\" id=\"multi-instance-setup__task-prereq\"><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">Before you begin</p></div>\n <p class=\"p\">Role required: admin</p>\n </section>\n <section class=\"section context\" id=\"multi-instance-setup__context_utx_skt_xfc\"><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">About this task</p></div>\n <p class=\"p\">Confirm you have:</p>\n <ul class=\"ul\" id=\"multi-instance-setup__ul_zvj_dsc_zfc\">\n <li class=\"li\">You’re operating in the Service Graph Connector for NOKIA Altiplano application scope.</li>\n <li class=\"li\">Installed the Service Graph Connector for Nokia Altiplano.</li>\n <li class=\"li\">Completed the guided setup for the initial Altiplano instance.</li>\n <li class=\"li\">MID Server set up and validated.</li>\n </ul>\n <p class=\"p\">You can configure additional Nokia Altiplano instances or reuse the same Altiplano instance with different connection aliases and import schedules. To add a new Altiplano instance, rerun the Guided setup to configure a new\n connection alias. Go through all connectivity stages in the setup for each new alias.</p>\n </section>\n <section><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">Procedure</p></div><ol class=\"ol steps\"><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">Navigate to <span class=\"ph menucascade\"><span class=\"ph uicontrol\">All</span><abbr> > </abbr><span class=\"ph uicontrol\">Service Graph Connectors</span><abbr> > </abbr><span class=\"ph uicontrol\">Nokia Altiplano</span><abbr> > </abbr><span class=\"ph uicontrol\">Setup</span></span>.</span>\n </li><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">On the Getting Started page, select <span class=\"ph uicontrol\">Get Started</span>.</span>\n <div class=\"itemgroup info\">Repeat all the steps under the Configured Connectivity section. It creates configuration entries for the new instance of Nokia Altiplano. For more information, see <a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/task/initial-setup-procedure.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/initial-setup-procedure.html\" class=\"xref\" title=\"Learn how to install and configure the Service Graph Connector for Nokia Altiplano, including optional demo data, connectivity setup, and data collection schedules.\">Install and configure the Nokia Altiplano</a>.</div>\n </li><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">Configure the connectivity by creating a connection alias, credentials, and HTTP connection.</span>\n <ol type=\"a\" class=\"ol substeps\" id=\"multi-instance-setup__substeps_xxy_4sc_zfc\">\n <li class=\"li substep\">\n <span class=\"ph cmd\">In the Configure Connectivity section, select Get Started.</span>\n </li>\n <li class=\"li substep\">\n <span class=\"ph cmd\">Select Configure to create a new connection alias by entering a unique alias name (for example, <code class=\"ph codeph\">Altiplano_Prod_01</code>).</span>\n </li>\n <li class=\"li substep\">\n <span class=\"ph cmd\">Select <span class=\"ph uicontrol\">Submit</span> and mark the step as complete.</span>\n </li>\n </ol>\n </li><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">Configure credentials for the new Altiplano instance.</span>\n <ol type=\"a\" class=\"ol substeps\" id=\"multi-instance-setup__substeps_djn_2tc_zfc\">\n <li class=\"li substep\">\n <span class=\"ph cmd\">Specify a user name and password for the Altiplano Controller.</span>\n </li>\n <li class=\"li substep\">\n <span class=\"ph cmd\">Submit and mark the step as complete.</span>\n </li>\n </ol>\n </li><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">Configure an HTTP connection.</span>\n <ol type=\"a\" class=\"ol substeps\" id=\"multi-instance-setup__substeps_mzt_gtc_zfc\">\n <li class=\"li substep\">\n <span class=\"ph cmd\">Provide the connection name.</span>\n </li>\n <li class=\"li substep\">\n <span class=\"ph cmd\">Select the newly created credentials and connection alias.</span>\n </li>\n <li class=\"li substep\">\n <span class=\"ph cmd\">Enter the connection URL of the Nokia Altiplano instance.</span>\n </li>\n <li class=\"li substep\">\n <span class=\"ph cmd\">Enable use MID Server and choose the appropriate MID option.</span>\n </li>\n <li class=\"li substep\">\n <span class=\"ph cmd\">Select <span class=\"ph uicontrol\">Submit</span> and mark the step as complete.</span>\n </li>\n </ol>\n </li><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">Schedule data imports using either bulk or filtered discovery by configuring the import schedule.</span>\n <ol type=\"a\" class=\"ol substeps\" id=\"multi-instance-setup__substeps_qhs_45c_zfc\">\n <li class=\"li substep substepexpand\">\n <span class=\"ph cmd\">Fill in the fields.</span>\n <div class=\"itemgroup info\">For more information, see <a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/task/initial-setup-procedure.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/initial-setup-procedure.html\" class=\"xref\" title=\"Learn how to install and configure the Service Graph Connector for Nokia Altiplano, including optional demo data, connectivity setup, and data collection schedules.\">Install and configure the Nokia Altiplano</a>.</div>\n </li>\n <li class=\"li substep substepexpand\">\n <span class=\"ph cmd\">In the <span class=\"ph uicontrol\">Use connection</span> field, choose the new Altiplano instance.</span>\n </li>\n </ol>\n </li><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">Select <span class=\"ph uicontrol\">Submit</span>.</span>\n </li></ol></section>\n <section class=\"section result\" id=\"multi-instance-setup__result_o5z_55c_zfc\"><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">Result</p></div>\n <div class=\"p\">To confirm that your new instance setup is successful, you can verify the configuration.<ul class=\"ul\" id=\"multi-instance-setup__ul_t3z_gvc_zfc\">\n <li class=\"li\">Navigate to All > Service Graph Connectors > Nokia Altiplano > Connection Aliases and confirm that the new alias is listed.</li>\n <li class=\"li\">Navigate to All > Service Graph Connectors > Nokia Altiplano > Import Schedule and confirm that the new import schedule is listed and confirm that corresponding jobs exist for each alias.</li>\n </ul></div>\n <p class=\"p\">You can configure multiple connection aliases hovering the same Nokia Altiplano instance. This flexibility enables you to run imports at different frequencies and apply different filters to each alias.</p>\n <p class=\"p\">Example: Altiplano_Weekly_OLT_10.10.10.*: Runs weekly, filters OLTs with IPs in the 10.10.10.* range. Altiplano_Daily_Prod: Runs daily, filters OLTs whose name contains "prod_olt".</p>\n </section>\n </div>\n <nav role=\"navigation\"></nav><nav role=\"navigation\" class=\"tasksNavigation\"></nav><nav role=\"navigation\" class=\"related-links\"><div class=\"col-md-4\"><dt>Related tasks</dt><dd><ul><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/task/configure-concurrent-import-and-parallel-loading.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/configure-concurrent-import-and-parallel-loading.html\" class=\"link\" title=\"Improve the efficiency of large data imports from Nokia Altiplano by configuring concurrent imports and enabling parallel loading. This configuration allows the platform to run multiple data import and transformation jobs simultaneously.\">Configure concurrent import and parallel loading for Nokia Altiplano</a></li></ul></dd></div><div class=\"col-md-4\"><dt>Related concepts</dt><dd><ul><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept/data-mapping.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/data-mapping.html\" class=\"link\" title=\"Use the Service Graph Connector for Nokia Altiplano to map discovered physical and logical network resources to telecom-aligned Configuration Item (CI) classes in the CMDB. The connector supports consistent service modeling, visibility into chassis-level components, and automation of logical and physical relationships.\">Mapping Nokia Altiplano CIs and Relationships in CMDB</a></li></ul></dd></div><div class=\"col-md-4\"><dt>Related reference</dt><dd><ul><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/reference/properties-installed-with-nokia-altiplano.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/reference/properties-installed-with-nokia-altiplano.html\" class=\"link\" title=\"System properties control how the connector operates, including discovery options and performance settings.\">System components installed with Nokia Altiplano</a></li></ul></dd></div></nav>\n</article></main></body></article>",
"topic_language": "enus",
"views": 0,
"your_rating": null
} | # Set up multiple Nokia Altiplano instances
Learn how to configure and manage multiple Nokia Altiplano instances within a single ServiceNow environment. This enables administrators and integrators to create independent connection aliases and import schedules customized
to specific filtering or frequency needs.
## Before you begin
Role required: admin
## About this task
Confirm you have:
* You’re operating in the Service Graph Connector for NOKIA Altiplano application scope.
* Installed the Service Graph Connector for Nokia Altiplano.
* Completed the guided setup for the initial Altiplano instance.
* MID Server set up and validated.
You can configure additional Nokia Altiplano instances or reuse the same Altiplano instance with different connection aliases and import schedules. To add a new Altiplano instance, rerun the Guided setup to configure a new
connection alias. Go through all connectivity stages in the setup for each new alias.
## Procedure
1. Navigate to All > Service Graph Connectors > Nokia Altiplano > Setup.
2. On the Getting Started page, select Get Started.
Repeat all the steps under the Configured Connectivity section. It creates configuration entries for the new instance of Nokia Altiplano. For more information, see Install and configure the Nokia Altiplano.
3. Configure the connectivity by creating a connection alias, credentials, and HTTP connection.
1. In the Configure Connectivity section, select Get Started.
2. Select Configure to create a new connection alias by entering a unique alias name (for example, `Altiplano_Prod_01`).
3. Select Submit and mark the step as complete.
4. Configure credentials for the new Altiplano instance.
1. Specify a user name and password for the Altiplano Controller.
2. Submit and mark the step as complete.
5. Configure an HTTP connection.
1. Provide the connection name.
2. Select the newly created credentials and connection alias.
3. Enter the connection URL of the Nokia Altiplano instance.
4. Enable use MID Server and choose the appropriate MID option.
5. Select Submit and mark the step as complete.
6. Schedule data imports using either bulk or filtered discovery by configuring the import schedule.
1. Fill in the fields.
For more information, see Install and configure the Nokia Altiplano.
2. In the Use connection field, choose the new Altiplano instance.
7. Select Submit.
### Result
To confirm that your new instance setup is successful, you can verify the configuration.
* Navigate to All > Service Graph Connectors > Nokia Altiplano > Connection Aliases and confirm that the new alias is listed.
* Navigate to All > Service Graph Connectors > Nokia Altiplano > Import Schedule and confirm that the new import schedule is listed and confirm that corresponding jobs exist for each alias.
You can configure multiple connection aliases hovering the same Nokia Altiplano instance. This flexibility enables you to run imports at different frequencies and apply different filters to each alias.
Example: Altiplano\_Weekly\_OLT\_10.10.10.*: Runs weekly, filters OLTs with IPs in the 10.10.10.* range. Altiplano\_Daily\_Prod: Runs daily, filters OLTs whose name contains "prod\_olt".
| ---
title: Set up multiple Nokia Altiplano instances
description: Learn how to configure and manage multiple Nokia Altiplano instances
within a single ServiceNow environment. This enables administrators and integrators
to create independent connection aliases and import schedules customized to specific
filtering or frequency needs.
keywords: []
breadcrumbs:
- Telecommunications Service Operations Management
- Configuring Telecommunications Service Operations Management
- Set up Telecom Visibility
- Configuring Nokia Altiplano service graph connector
---
# Set up multiple Nokia Altiplano instances
Learn how to configure and manage multiple Nokia Altiplano instances within a single ServiceNow environment. This enables administrators and integrators to create independent connection aliases and import schedules customized
to specific filtering or frequency needs.
## Before you begin
Role required: admin
## About this task
Confirm you have:
* You’re operating in the Service Graph Connector for NOKIA Altiplano application scope.
* Installed the Service Graph Connector for Nokia Altiplano.
* Completed the guided setup for the initial Altiplano instance.
* MID Server set up and validated.
You can configure additional Nokia Altiplano instances or reuse the same Altiplano instance with different connection aliases and import schedules. To add a new Altiplano instance, rerun the Guided setup to configure a new
connection alias. Go through all connectivity stages in the setup for each new alias.
## Procedure
1. Navigate to All > Service Graph Connectors > Nokia Altiplano > Setup.
2. On the Getting Started page, select Get Started.
Repeat all the steps under the Configured Connectivity section. It creates configuration entries for the new instance of Nokia Altiplano. For more information, see Install and configure the Nokia Altiplano.
3. Configure the connectivity by creating a connection alias, credentials, and HTTP connection.
1. In the Configure Connectivity section, select Get Started.
2. Select Configure to create a new connection alias by entering a unique alias name (for example, `Altiplano_Prod_01`).
3. Select Submit and mark the step as complete.
4. Configure credentials for the new Altiplano instance.
1. Specify a user name and password for the Altiplano Controller.
2. Submit and mark the step as complete.
5. Configure an HTTP connection.
1. Provide the connection name.
2. Select the newly created credentials and connection alias.
3. Enter the connection URL of the Nokia Altiplano instance.
4. Enable use MID Server and choose the appropriate MID option.
5. Select Submit and mark the step as complete.
6. Schedule data imports using either bulk or filtered discovery by configuring the import schedule.
1. Fill in the fields.
For more information, see Install and configure the Nokia Altiplano.
2. In the Use connection field, choose the new Altiplano instance.
7. Select Submit.
### Result
To confirm that your new instance setup is successful, you can verify the configuration.
* Navigate to All > Service Graph Connectors > Nokia Altiplano > Connection Aliases and confirm that the new alias is listed.
* Navigate to All > Service Graph Connectors > Nokia Altiplano > Import Schedule and confirm that the new import schedule is listed and confirm that corresponding jobs exist for each alias.
You can configure multiple connection aliases hovering the same Nokia Altiplano instance. This flexibility enables you to run imports at different frequencies and apply different filters to each alias.
Example: Altiplano\_Weekly\_OLT\_10.10.10.*: Runs weekly, filters OLTs with IPs in the 10.10.10.* range. Altiplano\_Daily\_Prod: Runs daily, filters OLTs whose name contains "prod\_olt".
|
https://www.servicenow.com/docs/en-US/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/run-and-verify-import-for-nokia-altiplano-service-graph-connector.html | https://servicenow-be-prod.servicenow.com/api/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/run-and-verify-import-for-nokia-altiplano-service-graph-connector.html | 2025-08-02 | daily | 0.5 | 268.xml | en-US | zurich-telecom-service-ops | product/tmt-telecom-service-operations-mgt/task/run-and-verify-import-for-nokia-altiplano-service-graph-connector.html | zurich | Run and verify import for Nokia Altiplano Service Graph Connector | Manually execute a configured import schedule for the Nokia Altiplano Service Graph Connector. You can also execute the import to validate the connector setup, run ad-hoc imports, or test newly configured connection aliases. This task helps ensure that data from | [] | [
"Telecommunications Service Operations Management",
"Using Telecommunications Service Operations Management"
] | <article class="hascomments" data-page="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/run-and-verify-import-for-nokia-altiplano-service-graph-connector.html" id="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/run-and-verify-import-for-nokia-altiplano-service-graph-connector.html"><body id="run-and-verify-import-for-nokia-altiplano-service-graph-connector"><main role="main"><article role="article" class="dita" id="run-and-verify-import-for-nokia-altiplano-service-graph-connector" aria-labelledby="title_run-and-verify-import-for-nokia-altiplano-service-graph-connector">
<h1 class="title topictitle1" id="title_run-and-verify-import-for-nokia-altiplano-service-graph-connector">Run and verify import for Nokia Altiplano Service Graph Connector</h1>
<div class="body taskbody"><p class="shortdesc">Manually execute a configured import schedule for the Nokia Altiplano Service Graph Connector. You can also execute the import to validate the connector setup, run ad-hoc imports, or test newly configured connection aliases.
This task helps ensure that data from Altiplano is successfully imported or updated in the CMDB.</p>
<section class="section prereq" id="run-and-verify-import-for-nokia-altiplano-service-graph-connector__task-prereq"><div class="tasklabel"><p class="sectiontitle tasklabel">Before you begin</p></div>
<p class="p">Role required: admin</p>
</section>
<section class="section context"><div class="tasklabel"><p class="sectiontitle tasklabel">About this task</p></div>After configuring the Nokia Altiplano Service Graph Connector and setting up one or more import schedules, you can execute an import job. This task helps you verify that the integration is working as expected and that CIs
are successfully imported or updated in the CMDB.<p class="p">You can either enable the import schedules to run automatically based on their defined frequency, or trigger them manually for immediate execution and validation.</p><div class="note note note_note"><span class="note__title">Note:</span> If
you have configured multiple Altiplano connection aliases (for different environments or filters), confirm that the import schedule is set up correctly for each alias.</div><p class="p">The following screenshot helps you understand
the scheduled data import process and displays the executions in the form of import sets.</p><img src="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/../images/scheduled-data-import.png?_LANG=enus" class="image" id="run-and-verify-import-for-nokia-altiplano-service-graph-connector__image_c4h_rh2_zfc" alt="Scheduled data import screen of Nokia Altiplano bulk discovery and the list of executions."/></section>
<section><div class="tasklabel"><p class="sectiontitle tasklabel">Procedure</p></div><ol class="ol steps"><li class="li step stepexpand">
<span class="ph cmd">Navigate to <span class="ph menucascade"><span class="ph uicontrol">All</span><abbr> > </abbr><span class="ph uicontrol">Nokia Altiplano</span><abbr> > </abbr><span class="ph uicontrol">Import Schedules</span></span>.</span>
</li><li class="li step stepexpand">
<span class="ph cmd">Select the import schedule that you want to run.</span>
<div class="itemgroup info">The list of scheduled data imports appear.</div>
</li><li class="li step stepexpand">
<span class="ph cmd">Select the scheduled data import.</span>
</li><li class="li step stepexpand">
<span class="ph cmd">Do one of the following:</span>
<ul class="ul choices" id="run-and-verify-import-for-nokia-altiplano-service-graph-connector__choices_kyp_kdd_zfc">
<li class="li choice">If the schedule is <span class="ph uicontrol">Active</span>, the job runs automatically at the defined interval. So wait until it’s executed. </li>
<li class="li choice">Select <span class="ph uicontrol">Execute Now</span> to run the import immediately.</li>
</ul>
</li><li class="li step stepexpand">
<span class="ph cmd">To monitor the execution and verify results:</span>
<ol type="a" class="ol substeps" id="run-and-verify-import-for-nokia-altiplano-service-graph-connector__substeps_q5w_ndd_zfc">
<li class="li substep">
<span class="ph cmd">Scroll down to the <span class="ph uicontrol">Executions</span> list or the table linked to the import schedule.</span>
</li>
<li class="li substep">
<span class="ph cmd">Open the most recent <span class="ph uicontrol">Import Set</span> record created by the execution.</span>
</li>
</ol>
</li><li class="li step stepexpand">
<span class="ph cmd">Review the import set log to verify the numbers of rows read, number of rows inserted or updated in the CMDB, or transformation success status.</span>
</li><li class="li step stepexpand">(Optional)
<span class="ph cmd">Navigate to <span class="ph menucascade"><span class="ph uicontrol">All</span><abbr> > </abbr><span class="ph uicontrol">CMDB</span><abbr> > </abbr><span class="ph uicontrol">CI Classes</span></span> or your custom telecom tables (such as TNI base item) to confirm the CIs were created or updated as expected.</span>
</li></ol></section>
<section class="section result" id="run-and-verify-import-for-nokia-altiplano-service-graph-connector__result_ztf_wdd_zfc"><div class="tasklabel"><p class="sectiontitle tasklabel">Result</p></div>
<p class="p">The import schedule runs immediately, and you can verify the import set execution and the corresponding CI updates in the CMDB. If configured correctly, the connector brings in the network inventory data from Nokia Altiplano
into your ServiceNow instance.</p>
<p class="p">Example: After executing the import schedule:</p>
<ul class="ul" id="run-and-verify-import-for-nokia-altiplano-service-graph-connector__ul_nss_w2d_zfc">
<li class="li">The log shows: “12 rows read, 0 inserted/updated.” This indicates that CIs exist.</li>
<li class="li">If you delete existing CIs and rerun the import, the log might show multiple inserts and updates, validating end-to-end functionality.</li>
</ul>
<div class="note note note_note"><span class="note__title">Note:</span>
<ul class="ul" id="run-and-verify-import-for-nokia-altiplano-service-graph-connector__ul_kwh_1fd_zfc">
<li class="li">If <span class="ph uicontrol">Concurrent Import</span> option is enabled in the import schedule, you’ll see records in the <span class="ph uicontrol">Concurrent Import Set</span> table instead of the standard Import Set table.</li>
<li class="li">Each concurrent job creates its own import set and log entry. The structure of the execution records remains the same.</li>
</ul>
</div>
</section>
</div>
<nav role="navigation"></nav><nav role="navigation" class="tasksNavigation"></nav><nav role="navigation" class="related-links"><div class="col-md-4"><dt>Related concepts</dt><dd><ul><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/concept/configuring-service-graph-connector-nokia-altiplano.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/configuring-service-graph-connector-nokia-altiplano.html" class="link" title="Configure the Nokia Altiplano service graph connector to import physical and logical inventory data from the Nokia Altiplano Access Network SDN Controller into your ServiceNow Configuration Management Database (CMDB).">Configuring Nokia Altiplano service graph connector</a></li><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/concept/service-graph-connector-for-nokia-altiplano.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/service-graph-connector-for-nokia-altiplano.html" class="link" title="The Service Graph Connector for Nokia Altiplano offers a telecom-aware integration that brings real-time network inventory from the Nokia Altiplano Access Network SDN Controller into your ServiceNow CMDB.">Telecom Discovery via Nokia Altiplano</a></li></ul></dd></div></nav>
</article></main></body></article> | {
"attachments": {
"all_attachments": null,
"topic_attachments": []
},
"available_languages": [
"enus"
],
"breadcrumbs": [
{
"title": "Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html"
},
{
"title": "Using Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/using-tsom.html"
}
],
"breadcrumbs_html": "<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops\">Zurich Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html\">Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/using-tsom.html\">Using Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<span class=\"active\">Run and verify import for Nokia Altiplano Service Graph Connector</span>",
"bundle_id": "zurich-telecom-service-ops",
"bundle_key": 2733,
"bundle_landing_page": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html",
"bundle_subtitle": null,
"bundle_title": "Zurich Telecommunications Service Operations Management",
"canonical_link": null,
"dates": {
"Added on": "2025-08-02T00:48:08.794016Z",
"Created on": "2025-07-14T00:00:00Z",
"Initial upload": "2025-07-30T22:24:33.519043Z",
"Updated on": "2025-07-31T00:00:00Z"
},
"dislike_url": "https://servicenow-be-prod.servicenow.com/dislike/55686979",
"dislikes": 0,
"es_archived_content": false,
"is_in_fav": false,
"is_liked": null,
"is_watched": false,
"keywords": [
" zurich zurich"
],
"labels": [
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "zurich",
"navtitle": "Zurich",
"outputclasses": [],
"subjectHeadId": "versions",
"subjectheadNavtitle": "Versions",
"visibility": "show-facet"
},
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "tsom",
"navtitle": "Telecommunications Service Operations Management",
"outputclasses": [],
"subjectHeadId": "products",
"subjectheadNavtitle": "Products",
"visibility": "show-facet"
}
],
"labels_text": "Versions > Zurich; Products > CRM and Industry Products > Telecommunications Media and Technology Assurance > Telecommunications Service Operations Management",
"like_url": "https://servicenow-be-prod.servicenow.com/like/55686979",
"likes": 0,
"metadata": {
"AI Search": null,
"AI Search Assist": null,
"Application Insights": null,
"Capabilities": null,
"Code Signing": null,
"Contextual Search": null,
"DC.contributor": null,
"DC.coverage": null,
"DC.creator": "ServiceNow",
"DC.date.created": "2025-07-14T09:05:07+05:30",
"DC.date.modified": "2025-07-31",
"DC.format": "HTML5",
"DC.identifier": "run-and-verify-import-for-nokia-altiplano-service-graph-connector",
"DC.language": null,
"DC.relation": "../../../product/tmt-telecom-service-operations-mgt/concept/using-tsom.html",
"DC.rights.owner": "(C) Copyright 2025",
"DC.subject": null,
"DC.type": "task",
"Data Discovery": null,
"Data Policy": null,
"Data Privacy": null,
"Discovery": null,
"External Content for AI Search": null,
"Field Administration": null,
"Field Normalization": null,
"Key Management Framework": null,
"Localization Framework": null,
"Now Platform": null,
"PlatSec": null,
"Platform": null,
"Platform Administration": null,
"Platform Performance": null,
"Platform Privacy": null,
"Proactive Triggers": null,
"Process Optimization": null,
"RN doc editing record number": null,
"Search Administration": null,
"Secrets Management": null,
"ServiceNow AI Platform": null,
"State Model": null,
"Subscription Management": null,
"Task Communications Management": null,
"Timeline Visualizations": null,
"User Administration": null,
"User Experience Analytics": null,
"Zing": null,
"ai-now-assist": null,
"app-name": null,
"app_route": null,
"azureapimanagemen": null,
"change-completed": null,
"change-item": null,
"change-request-id": null,
"change-request-reference": null,
"com.glide.embedded_help.category": null,
"component": null,
"copyright": "(C) Copyright 2025",
"crossroads": null,
"data": null,
"description": "Manually execute a configured import schedule for the Nokia Altiplano Service Graph Connector. You can also execute the import to validate the connector setup, run ad-hoc imports, or test newly configured connection aliases. This task helps ensure that data from",
"dominant_bundle": null,
"erp-canvas-video": null,
"fsm-mobile": null,
"fsm-route": null,
"fsm-sched-opt": null,
"fsm-wrk-order": null,
"genai-round-7": null,
"generator": "DITA-OT",
"glossPartOfSpeech": null,
"glossStatus": null,
"guided setup": null,
"guided tours": null,
"keywords": null,
"min-toc": null,
"mini": null,
"mini-to truec": null,
"mini-toc": null,
"mini_toc": null,
"minitoc": null,
"modification": null,
"now-assist-app-gen-video": null,
"order": null,
"page-type": null,
"page-type ": null,
"prodname": null,
"product": null,
"product_name": null,
"release": null,
"resourceID": null,
"roles": null,
"route_page": null,
"route_params_listId": null,
"route_params_table": null,
"route_params_type": null,
"route_type": null,
"setconfigurationproperties": null,
"topic": null,
"translation-type": "source",
"version": null,
"workflow": "Customer and Industry",
"workplace-srvc-delvry-ditamap": null
},
"page_id": "product/tmt-telecom-service-operations-mgt/task/run-and-verify-import-for-nokia-altiplano-service-graph-connector.html",
"page_key": 55686979,
"preprocessed_PDF": "https://downloads.docs.servicenow.com/pdf/enus/servicenow-zurich-telecom-service-ops-enus.pdf",
"rating": null,
"read_time_data": {
"char_count": 2866,
"img_count": 1,
"read_time": 2,
"video_links": [
""
],
"word_count": 450
},
"related_links": [
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "Configure the Nokia Altiplano service graph connector to import physical and logical inventory data from the Nokia Altiplano Access Network SDN Controller into your ServiceNow Configuration Management Database (CMDB).",
"title": "Configuring Nokia Altiplano service graph connector",
"topic": "/product/tmt-telecom-service-operations-mgt/concept/configuring-service-graph-connector-nokia-altiplano.html",
"type": "concept",
"url": null
},
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "The Service Graph Connector for Nokia Altiplano offers a telecom-aware integration that brings real-time network inventory from the Nokia Altiplano Access Network SDN Controller into your ServiceNow CMDB.",
"title": "Telecom Discovery via Nokia Altiplano",
"topic": "/product/tmt-telecom-service-operations-mgt/concept/service-graph-connector-for-nokia-altiplano.html",
"type": "concept",
"url": null
}
],
"search_title": null,
"title": "Run and verify import for Nokia Altiplano Service Graph Connector",
"topic_cluster": {
"clustered_by": {
"enabled": true,
"primary_key": "versions",
"primary_sort": "top-down",
"type": "subjecthead"
},
"clustered_labels": [
"versions"
],
"clustered_topics": [],
"clustering_title": "Zurich"
},
"topic_html": "<article class=\"hascomments\" data-page=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/run-and-verify-import-for-nokia-altiplano-service-graph-connector.html\" id=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/run-and-verify-import-for-nokia-altiplano-service-graph-connector.html\"><body id=\"run-and-verify-import-for-nokia-altiplano-service-graph-connector\"><main role=\"main\"><article role=\"article\" class=\"dita\" id=\"run-and-verify-import-for-nokia-altiplano-service-graph-connector\" aria-labelledby=\"title_run-and-verify-import-for-nokia-altiplano-service-graph-connector\">\n <h1 class=\"title topictitle1\" id=\"title_run-and-verify-import-for-nokia-altiplano-service-graph-connector\">Run and verify import for Nokia Altiplano Service Graph Connector</h1>\n \n \n <div class=\"body taskbody\"><p class=\"shortdesc\">Manually execute a configured import schedule for the Nokia Altiplano Service Graph Connector. You can also execute the import to validate the connector setup, run ad-hoc imports, or test newly configured connection aliases.\n This task helps ensure that data from Altiplano is successfully imported or updated in the CMDB.</p>\n <section class=\"section prereq\" id=\"run-and-verify-import-for-nokia-altiplano-service-graph-connector__task-prereq\"><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">Before you begin</p></div>\n <p class=\"p\">Role required: admin</p>\n </section>\n <section class=\"section context\"><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">About this task</p></div>After configuring the Nokia Altiplano Service Graph Connector and setting up one or more import schedules, you can execute an import job. This task helps you verify that the integration is working as expected and that CIs\n are successfully imported or updated in the CMDB.<p class=\"p\">You can either enable the import schedules to run automatically based on their defined frequency, or trigger them manually for immediate execution and validation.</p><div class=\"note note note_note\"><span class=\"note__title\">Note:</span> If\n you have configured multiple Altiplano connection aliases (for different environments or filters), confirm that the import schedule is set up correctly for each alias.</div><p class=\"p\">The following screenshot helps you understand\n the scheduled data import process and displays the executions in the form of import sets.</p><img src=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/../images/scheduled-data-import.png?_LANG=enus\" class=\"image\" id=\"run-and-verify-import-for-nokia-altiplano-service-graph-connector__image_c4h_rh2_zfc\" alt=\"Scheduled data import screen of Nokia Altiplano bulk discovery and the list of executions.\"/></section>\n <section><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">Procedure</p></div><ol class=\"ol steps\"><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">Navigate to <span class=\"ph menucascade\"><span class=\"ph uicontrol\">All</span><abbr> > </abbr><span class=\"ph uicontrol\">Nokia Altiplano</span><abbr> > </abbr><span class=\"ph uicontrol\">Import Schedules</span></span>.</span>\n </li><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">Select the import schedule that you want to run.</span>\n <div class=\"itemgroup info\">The list of scheduled data imports appear.</div>\n </li><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">Select the scheduled data import.</span>\n </li><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">Do one of the following:</span>\n <ul class=\"ul choices\" id=\"run-and-verify-import-for-nokia-altiplano-service-graph-connector__choices_kyp_kdd_zfc\">\n <li class=\"li choice\">If the schedule is <span class=\"ph uicontrol\">Active</span>, the job runs automatically at the defined interval. So wait until it’s executed. </li>\n <li class=\"li choice\">Select <span class=\"ph uicontrol\">Execute Now</span> to run the import immediately.</li>\n </ul>\n </li><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">To monitor the execution and verify results:</span>\n <ol type=\"a\" class=\"ol substeps\" id=\"run-and-verify-import-for-nokia-altiplano-service-graph-connector__substeps_q5w_ndd_zfc\">\n <li class=\"li substep\">\n <span class=\"ph cmd\">Scroll down to the <span class=\"ph uicontrol\">Executions</span> list or the table linked to the import schedule.</span>\n </li>\n <li class=\"li substep\">\n <span class=\"ph cmd\">Open the most recent <span class=\"ph uicontrol\">Import Set</span> record created by the execution.</span>\n </li>\n </ol>\n </li><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">Review the import set log to verify the numbers of rows read, number of rows inserted or updated in the CMDB, or transformation success status.</span>\n </li><li class=\"li step stepexpand\">(Optional) \n <span class=\"ph cmd\">Navigate to <span class=\"ph menucascade\"><span class=\"ph uicontrol\">All</span><abbr> > </abbr><span class=\"ph uicontrol\">CMDB</span><abbr> > </abbr><span class=\"ph uicontrol\">CI Classes</span></span> or your custom telecom tables (such as TNI base item) to confirm the CIs were created or updated as expected.</span>\n </li></ol></section>\n <section class=\"section result\" id=\"run-and-verify-import-for-nokia-altiplano-service-graph-connector__result_ztf_wdd_zfc\"><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">Result</p></div>\n <p class=\"p\">The import schedule runs immediately, and you can verify the import set execution and the corresponding CI updates in the CMDB. If configured correctly, the connector brings in the network inventory data from Nokia Altiplano\n into your ServiceNow instance.</p>\n <p class=\"p\">Example: After executing the import schedule:</p>\n <ul class=\"ul\" id=\"run-and-verify-import-for-nokia-altiplano-service-graph-connector__ul_nss_w2d_zfc\">\n <li class=\"li\">The log shows: “12 rows read, 0 inserted/updated.” This indicates that CIs exist.</li>\n <li class=\"li\">If you delete existing CIs and rerun the import, the log might show multiple inserts and updates, validating end-to-end functionality.</li>\n </ul>\n <div class=\"note note note_note\"><span class=\"note__title\">Note:</span> \n <ul class=\"ul\" id=\"run-and-verify-import-for-nokia-altiplano-service-graph-connector__ul_kwh_1fd_zfc\">\n <li class=\"li\">If <span class=\"ph uicontrol\">Concurrent Import</span> option is enabled in the import schedule, you’ll see records in the <span class=\"ph uicontrol\">Concurrent Import Set</span> table instead of the standard Import Set table.</li>\n <li class=\"li\">Each concurrent job creates its own import set and log entry. The structure of the execution records remains the same.</li>\n </ul>\n </div>\n </section>\n </div>\n <nav role=\"navigation\"></nav><nav role=\"navigation\" class=\"tasksNavigation\"></nav><nav role=\"navigation\" class=\"related-links\"><div class=\"col-md-4\"><dt>Related concepts</dt><dd><ul><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept/configuring-service-graph-connector-nokia-altiplano.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/configuring-service-graph-connector-nokia-altiplano.html\" class=\"link\" title=\"Configure the Nokia Altiplano service graph connector to import physical and logical inventory data from the Nokia Altiplano Access Network SDN Controller into your ServiceNow Configuration Management Database (CMDB).\">Configuring Nokia Altiplano service graph connector</a></li><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept/service-graph-connector-for-nokia-altiplano.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/service-graph-connector-for-nokia-altiplano.html\" class=\"link\" title=\"The Service Graph Connector for Nokia Altiplano offers a telecom-aware integration that brings real-time network inventory from the Nokia Altiplano Access Network SDN Controller into your ServiceNow CMDB.\">Telecom Discovery via Nokia Altiplano</a></li></ul></dd></div></nav>\n</article></main></body></article>",
"topic_language": "enus",
"views": 0,
"your_rating": null
} | # Run and verify import for Nokia Altiplano Service Graph Connector
Manually execute a configured import schedule for the Nokia Altiplano Service Graph Connector. You can also execute the import to validate the connector setup, run ad-hoc imports, or test newly configured connection aliases.
This task helps ensure that data from Altiplano is successfully imported or updated in the CMDB.
## Before you begin
Role required: admin
## About this task
After configuring the Nokia Altiplano Service Graph Connector and setting up one or more import schedules, you can execute an import job. This task helps you verify that the integration is working as expected and that CIs
are successfully imported or updated in the CMDB.
You can either enable the import schedules to run automatically based on their defined frequency, or trigger them manually for immediate execution and validation.
Note: If
you have configured multiple Altiplano connection aliases (for different environments or filters), confirm that the import schedule is set up correctly for each alias.
The following screenshot helps you understand
the scheduled data import process and displays the executions in the form of import sets.
## Procedure
1. Navigate to All > Nokia Altiplano > Import Schedules.
2. Select the import schedule that you want to run.
The list of scheduled data imports appear.
3. Select the scheduled data import.
4. Do one of the following:
* If the schedule is Active, the job runs automatically at the defined interval. So wait until it’s executed.
* Select Execute Now to run the import immediately.
5. To monitor the execution and verify results:
1. Scroll down to the Executions list or the table linked to the import schedule.
2. Open the most recent Import Set record created by the execution.
6. Review the import set log to verify the numbers of rows read, number of rows inserted or updated in the CMDB, or transformation success status.
7. (Optional)
Navigate to All > CMDB > CI Classes or your custom telecom tables (such as TNI base item) to confirm the CIs were created or updated as expected.
### Result
The import schedule runs immediately, and you can verify the import set execution and the corresponding CI updates in the CMDB. If configured correctly, the connector brings in the network inventory data from Nokia Altiplano
into your ServiceNow instance.
Example: After executing the import schedule:
* The log shows: “12 rows read, 0 inserted/updated.” This indicates that CIs exist.
* If you delete existing CIs and rerun the import, the log might show multiple inserts and updates, validating end-to-end functionality.
Note:
* If Concurrent Import option is enabled in the import schedule, you’ll see records in the Concurrent Import Set table instead of the standard Import Set table.
* Each concurrent job creates its own import set and log entry. The structure of the execution records remains the same.
| ---
title: Run and verify import for Nokia Altiplano Service Graph Connector
description: Manually execute a configured import schedule for the Nokia Altiplano
Service Graph Connector. You can also execute the import to validate the connector
setup, run ad-hoc imports, or test newly configured connection aliases. This task
helps ensure that data from
keywords: []
breadcrumbs:
- Telecommunications Service Operations Management
- Using Telecommunications Service Operations Management
---
# Run and verify import for Nokia Altiplano Service Graph Connector
Manually execute a configured import schedule for the Nokia Altiplano Service Graph Connector. You can also execute the import to validate the connector setup, run ad-hoc imports, or test newly configured connection aliases.
This task helps ensure that data from Altiplano is successfully imported or updated in the CMDB.
## Before you begin
Role required: admin
## About this task
After configuring the Nokia Altiplano Service Graph Connector and setting up one or more import schedules, you can execute an import job. This task helps you verify that the integration is working as expected and that CIs
are successfully imported or updated in the CMDB.
You can either enable the import schedules to run automatically based on their defined frequency, or trigger them manually for immediate execution and validation.
Note: If
you have configured multiple Altiplano connection aliases (for different environments or filters), confirm that the import schedule is set up correctly for each alias.
The following screenshot helps you understand
the scheduled data import process and displays the executions in the form of import sets.
## Procedure
1. Navigate to All > Nokia Altiplano > Import Schedules.
2. Select the import schedule that you want to run.
The list of scheduled data imports appear.
3. Select the scheduled data import.
4. Do one of the following:
* If the schedule is Active, the job runs automatically at the defined interval. So wait until it’s executed.
* Select Execute Now to run the import immediately.
5. To monitor the execution and verify results:
1. Scroll down to the Executions list or the table linked to the import schedule.
2. Open the most recent Import Set record created by the execution.
6. Review the import set log to verify the numbers of rows read, number of rows inserted or updated in the CMDB, or transformation success status.
7. (Optional)
Navigate to All > CMDB > CI Classes or your custom telecom tables (such as TNI base item) to confirm the CIs were created or updated as expected.
### Result
The import schedule runs immediately, and you can verify the import set execution and the corresponding CI updates in the CMDB. If configured correctly, the connector brings in the network inventory data from Nokia Altiplano
into your ServiceNow instance.
Example: After executing the import schedule:
* The log shows: “12 rows read, 0 inserted/updated.” This indicates that CIs exist.
* If you delete existing CIs and rerun the import, the log might show multiple inserts and updates, validating end-to-end functionality.
Note:
* If Concurrent Import option is enabled in the import schedule, you’ll see records in the Concurrent Import Set table instead of the standard Import Set table.
* Each concurrent job creates its own import set and log entry. The structure of the execution records remains the same.
|
https://www.servicenow.com/docs/en-US/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/run-audits.html | https://servicenow-be-prod.servicenow.com/api/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/run-audits.html | 2025-08-02 | daily | 0.5 | 268.xml | en-US | zurich-telecom-service-ops | product/tmt-telecom-service-operations-mgt/task/run-audits.html | zurich | 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. | [] | [
"Telecommunications Service Operations Management",
"Using Telecommunications Service Operations Management"
] | <article class="hascomments" data-page="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/run-audits.html" id="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/run-audits.html"><body><main role="main"><article role="article" class="dita" aria-labelledby="title_run-audits"><article class="nested0" aria-labelledby="title_run-audits" id="run-audits">
<h1 class="title topictitle1" id="title_run-audits">Run Telecom Discrepancy audit</h1>
<div class="body taskbody"><p class="shortdesc">The Telecom Discrepancy Audit validates the integrity of configuration items (CIs) and relationships across your telecom inventory using the CMDB Compliance framework. </p>
<section class="section prereq" id="run-audits__task-prereq"><div class="tasklabel"><p class="sectiontitle tasklabel">Before you begin</p></div>
<p class="p">Role required: admin</p>
</section>
<section class="section context" id="run-audits__context_ypb_vbc_yfc"><div class="tasklabel"><p class="sectiontitle tasklabel">About this task</p></div>
<p class="p">The Telecom Discrepancy Audit is part of the CMDB Compliance framework and supports phased auditing to detect and address discrepancies in CI relationships and attributes discovered through ServiceNow Discovery or Service
Graph Connectors (for example, Nokia Altiplano).</p>
<p class="p">You can run the audit manually or set it to run at regular intervals. During manual execution, you can select from existing filters to limit the audit scope to specific CIs—helpful for testing or targeted reconciliation.</p>
<div class="p">The Telecom Discrepancy Audit works in two phases:<ol class="ol" id="run-audits__ol_cfk_yyn_xfc">
<li class="li">Initial compliance run: Validates CI relationships and selected CI tables using the following default criteria:<ul class="ul" id="run-audits__ul_ydk_qyn_xfc">
<li class="li">Supported CI classes: Slot, Subslot, Card, Interface, Network Gear (includes all extension tables).</li>
<li class="li">Source: CI was discovered via Discovery (For example <code class="ph codeph">discovery_source = SG-TSOM-Altiplano</code>).</li>
<li class="li">Relationship type: <code class="ph codeph">Contains::Contained By</code> (customizable via <code class="ph codeph">sn_tsom_core.audit.relationship_types</code> property).</li>
</ul></li>
<li class="li">Subsequent compliance runs: In addition to initial checks, evaluates whether the Updated timestamp of the relationship or related CIs is more recent than the Last run date in the audit record.<div class="note note note_note"><span class="note__title">Note:</span> Each failed audit
creates a Follow-On Task for manual or automated remediation, confirming telecom CMDB data stays aligned with the network state.</div></li>
</ol></div>
<p class="p">The following screenshot helps you understand the Telecom Discrepancy Audit.<img src="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/../images/telecom-discrepancy-audit.png?_LANG=enus" class="image" id="run-audits__image_w5j_lrd_zfc" alt="The user interface of the telecom discrepancy audit."/></p>
</section>
<section id="run-audits__steps_vzt_tbc_yfc"><div class="tasklabel"><p class="sectiontitle tasklabel">Procedure</p></div><ol class="ol steps" id="run-audits__steps_vzt_tbc_yfc"><li class="li step stepexpand">
<span class="ph cmd">Navigate to <span class="ph menucascade"><span class="ph uicontrol">All</span><abbr> > </abbr><span class="ph uicontrol">Compliance</span><abbr> > </abbr><span class="ph uicontrol">Audits</span></span></span>
</li><li class="li step stepexpand">
<span class="ph cmd">Open the Telecom Discrepancy Audit (cert_audit table) record.</span>
</li><li class="li step stepexpand">(Optional)
<span class="ph cmd">Select a filter.</span>
<div class="itemgroup info">
<ul class="ul" id="run-audits__ul_olp_mcn_zfc">
<li class="li">If multiple audit filters have been defined during configuration, you can choose one before running the audit.</li>
<li class="li">Filters enable you to restrict the audit scope based on criteria such as discovery source, CI class, or specific CI attributes.</li>
<li class="li">This step is especially useful when troubleshooting a subset of records or validating specific discovery results.</li>
</ul>
</div>
</li><li class="li step stepexpand">
<span class="ph cmd">Do either of the following to run the audit.</span>
<ul class="ul choices" id="run-audits__choices_tsn_vcn_zfc">
<li class="li choice">Click <span class="ph uicontrol">Run Audit</span> to trigger a manual execution.</li>
<li class="li choice">Configure the audit to run on a scheduled basis by setting up a recurring job.</li>
</ul>
<div class="itemgroup stepresult">The audit uses CMDB Compliance to validate relationship and CI integrity across telecom inventory.</div>
</li></ol></section>
<section class="section result" id="run-audits__result_rz5_cdn_zfc"><div class="tasklabel"><p class="sectiontitle tasklabel">Result</p></div>
<div class="p">Review audit results<ul class="ul" id="run-audits__ul_l5z_zcn_zfc">
<li class="li">The audit identifies compliance failures such as missing relationships or misaligned attributes.</li>
<li class="li">For each failed audit record, a Follow-On Task is automatically generated.</li>
<li class="li">Tasks include recommended or automated remediation actions such as updating or decommissioning CIs.</li>
</ul></div>
<p class="p">Example use case: The configured filters can be used for different discovery sources. For example, the Nokia Altiplano. When running the audit manually, you can select the appropriate filter to validate only those CIs
discovered by that specific source—confirming targeted and efficient auditing.</p>
</section>
</div>
<nav role="navigation"></nav><nav role="navigation" class="tasksNavigation"></nav><nav role="navigation" class="related-links"><div class="col-md-4"><dt>Related tasks</dt><dd><ul><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/task/configure-certification-filter-for-audit.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/configure-certification-filter-for-audit.html" class="link" title="Define filtering conditions to control the scope of Telecom Discrepancy audits. These filters ensure that audits run only on the desired set of CIs, improving performance and targeting accuracy.">Configure filter for audit</a></li><li><a class="link" href="#example-for-telecom-discrepancy-and-reconciliation" title="The following example illustrates how the audit works in a scenario.">Example for Telecom Discrepancy Audit and Remediation</a></li></ul></dd></div></nav>
<article class="topic task nested1" aria-labelledby="title_example-for-telecom-discrepancy-and-reconciliation" id="example-for-telecom-discrepancy-and-reconciliation">
<h2 class="title topictitle2" id="title_example-for-telecom-discrepancy-and-reconciliation">Example for Telecom Discrepancy Audit and Remediation</h2>
<div class="body taskbody"><p class="shortdesc">The following example illustrates how the audit works in a scenario.</p>
<section class="section prereq" id="example-for-telecom-discrepancy-and-reconciliation__task-prereq"><div class="tasklabel"><p class="sectiontitle tasklabel">Before you begin</p></div>
<p class="p">Role required: admin</p>
</section>
<section class="section context" id="example-for-telecom-discrepancy-and-reconciliation__context_qbq_2zd_wfc"><div class="tasklabel"><p class="sectiontitle tasklabel">About this task</p></div><p class="p">A card (Card04) was initially discovered in Slot04. Later, Card04 was replaced by Card05 in the physical network, but the CMDB still shows Card04 in Slot04. When a new discovery run executes, Card05
is discovered and added to the same slot, creating a data conflict in CMDB.</p><p class="p">Audit Behavior:</p><ul class="ul" id="example-for-telecom-discrepancy-and-reconciliation__ul_zls_d3c_yfc">
<li class="li">The Telecom Discrepancy Audit detects this inconsistency and creates a failed audit record (e.g., <code class="ph codeph">AUDR0001283</code>).</li>
<li class="li">A Follow-On Task is created automatically (e.g., <code class="ph codeph">TASK0020215</code>) with a detailed description of the discrepancy.</li>
</ul><p class="p">Task Description Example (Incorrect Number of Relationships):</p><div class="p">Card04 was last discovered more than 2.5 days ago.<div class="table-wrap"><table count-columns="2" class="table frame-all" id="example-for-telecom-discrepancy-and-reconciliation__table_z5y_m3c_yfc"><caption><span class="table--title-label">Table 1. </span><span class="title">Relationships between the following CIs</span></caption><colgroup><col style="width:50%"/><col style="width:50%"/></colgroup><thead class="thead">
<tr class="row">
<th class="entry colsep-1 rowsep-1" id="example-for-telecom-discrepancy-and-reconciliation__table_z5y_m3c_yfc__entry__1">CI</th>
<th class="entry colsep-1 rowsep-1" id="example-for-telecom-discrepancy-and-reconciliation__table_z5y_m3c_yfc__entry__2">Model</th>
</tr>
</thead><tbody class="tbody">
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="example-for-telecom-discrepancy-and-reconciliation__table_z5y_m3c_yfc__entry__1">Slot04</td>
<td class="entry colsep-1 rowsep-1" headers="example-for-telecom-discrepancy-and-reconciliation__table_z5y_m3c_yfc__entry__2">DEMO 20532Tree</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="example-for-telecom-discrepancy-and-reconciliation__table_z5y_m3c_yfc__entry__1">Card04</td>
<td class="entry colsep-1 rowsep-1" headers="example-for-telecom-discrepancy-and-reconciliation__table_z5y_m3c_yfc__entry__2">Nokia 7360 FANT-F CARD MODULE</td>
</tr>
<tr class="row">
<td class="entry colsep-1 rowsep-1" headers="example-for-telecom-discrepancy-and-reconciliation__table_z5y_m3c_yfc__entry__1">Card05</td>
<td class="entry colsep-1 rowsep-1" headers="example-for-telecom-discrepancy-and-reconciliation__table_z5y_m3c_yfc__entry__2"><model not identified></td>
</tr>
</tbody></table></div></div><p class="p">The following snapshots will help you understand the discrepancy and remediation process.</p><p class="p"><img src="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/../images/telecom-run-audits.png?_LANG=enus" class="image" id="example-for-telecom-discrepancy-and-reconciliation__image_g4b_znj_b2c" alt="run audit."/></p><img src="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/../images/telecom-ui-actions.png?_LANG=enus" class="image" id="example-for-telecom-discrepancy-and-reconciliation__image_z4b_k4j_b2c" alt="UI actions."/><p class="p"><img src="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/../images/telecom-subflow.png?_LANG=enus" class="image" id="example-for-telecom-discrepancy-and-reconciliation__image_mcn_fcd_yfc" alt="example subflow."/></p></section>
<section><div class="tasklabel"><p class="sectiontitle tasklabel">Procedure</p></div><ol class="ol steps"><li class="li step stepexpand">
<span class="ph cmd">Navigate <span class="ph menucascade"><span class="ph uicontrol">All</span><abbr> > </abbr><span class="ph uicontrol">Compliance</span><abbr> > </abbr><span class="ph uicontrol">Audits</span><abbr> > </abbr><span class="ph uicontrol">Telecom Discrepancy Audit</span><abbr> > </abbr><span class="ph uicontrol">Run Audits</span></span>.</span>
<div class="itemgroup stepresult">A Follow-on Task is automatically created for each failed audit record (for example, TASK0020215).</div>
</li><li class="li step stepexpand">
<span class="ph cmd">Select <span class="ph uicontrol">TASK0020215</span> and review the discrepancy description.</span>
<div class="itemgroup info">
<div class="note note note_note"><span class="note__title">Note:</span> This is an example of the TASK0020215 description created for the "Incorrect number of relationships" scenario. Other scenarios and environments might have different descriptions.</div>
</div>
<div class="itemgroup stepresult">The Follow-On Task contains a detailed description of the discrepancy. As you can see in the description, the Card04 CI is in discrepancy.</div>
</li><li class="li step stepexpand">
<span class="ph cmd">To remediate, perform the following steps:</span>
<ol type="a" class="ol substeps">
<li class="li substep substepexpand">
<span class="ph cmd">Navigate <span class="ph menucascade"><span class="ph uicontrol">All</span><abbr> > </abbr><span class="ph uicontrol">System Definition</span><abbr> > </abbr><span class="ph uicontrol">UI Actions</span></span>.</span>
</li>
<li class="li substep substepexpand">
<span class="ph cmd">Select <span class="ph uicontrol">Remediate</span>.</span>
<div class="itemgroup stepresult">The Remediate button is a UI action that triggers the <code class="ph codeph">TSOM CI Decommission</code> subflow. This subflow:<ul class="ul" id="example-for-telecom-discrepancy-and-reconciliation__ul_hpd_3bd_yfc">
<li class="li">Retires the outdated Card04 CI.</li>
<li class="li">Removes the incorrect Slot04 → Card04 relationship.</li>
<li class="li">Synchronizes CMDB records with the network state.</li>
</ul></div>
</li>
</ol>
</li></ol></section>
<section class="section result" id="example-for-telecom-discrepancy-and-reconciliation__result_zvt_mbd_yfc"><div class="tasklabel"><p class="sectiontitle tasklabel">Result</p></div>
<p class="p">After remediation:</p>
<ul class="ul" id="example-for-telecom-discrepancy-and-reconciliation__ul_gwy_mbd_yfc">
<li class="li">The Follow-On Task (<code class="ph codeph">TASK0020215</code>) updates with work notes summarizing the resolution steps.</li>
<li class="li">The Card04 CI is marked as retired, and incorrect relationships are removed.</li>
<li class="li">CMDB is now aligned with the latest discovered state from the network.</li>
</ul>
<div class="note note note_note"><span class="note__title">Note:</span> Customize Remediation - The Telecom Discrepancy Audit ships with example remediation subflows. You can create and attach custom subflows using Flow Designer to suit your operational requirements.</div>
</section>
</div>
<nav role="navigation"></nav><nav role="navigation" class="tasksNavigation"></nav><nav role="navigation" class="related-links"><div class="col-md-4"><dt>Related tasks</dt><dd><ul><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/task/configure-telecom-reconciliation.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/configure-telecom-reconciliation.html" class="link" title="Activate the Telecom Discrepancy Identification and Reconciliation feature (part of the Telecom Visibility plugin) to ensure consistency between telecom network resources discovered in the live network and the data represented in the CMDB or Telecom Network Inventory (TNI). This feature helps detect and remediate mismatches automatically, supporting service accuracy and data integrity across your telecom environment.">Activate Telecom Discrepancy Identification and Reconciliation</a></li></ul></dd></div><div class="col-md-4"><dt>Related concepts</dt><dd><ul><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/concept/exploring-telecom-reconciliation.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/exploring-telecom-reconciliation.html" class="link" title="Use the Telecom Discrepancy Identification and Reconciliation capability to keep your CMDB or Telecommunications Network Inventory (TNI) in sync with your live telecom network. By continuously auditing and comparing discovered data with inventory records, this solution helps you detect, classify, and automatically remediate inconsistencies before they impact service quality, assurance, or fulfillment processes.">Telecom Discrepancy Identification and Reconciliation</a></li><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/concept/discrepancy-identification-types-of-discrepancies.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/discrepancy-identification-types-of-discrepancies.html" class="link" title="The Telecom Discrepancy Identification and Reconciliation capability identifies and classifies mismatches between the network state (as discovered through TSOM Discovery or Service Graph Connectors) and the inventory data stored in the CMDB or TNI.">Discrepancy identification – types of discrepancies</a></li><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/concept/system-properties-affecting-telecom-discrepancy-identification-reconciliation.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/system-properties-affecting-telecom-discrepancy-identification-reconciliation.html" class="link" title="The system properties are part of the TSOM Visibility plugin (sn_tsom_core) and control the Telecom Discrepancy Identification & Reconciliation log (TSOM CMDB Audit). The TSOM Visibility plugin serves as an enabler for the TSOM Visibility applications, containing logic that is shared across the Telecom Discovery and Telecom Discrepancy Identification & Reconciliation solution.">System components installed with Telecom Discrepancy Identification & Reconciliation</a></li></ul></dd></div><div class="col-md-4"><dt>Related topics</dt><dd><ul><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/task//csh" href="https://servicenow-be-prod.servicenow.com/csh?topicname=c_UIActions&version=zurich&pubname=zurich-platform-administration" class="link">Defining UI actions</a></li></ul></dd></div></nav>
</article></article></article></main></body></article> | {
"attachments": {
"all_attachments": null,
"topic_attachments": []
},
"available_languages": [
"enus"
],
"breadcrumbs": [
{
"title": "Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html"
},
{
"title": "Using Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/using-tsom.html"
}
],
"breadcrumbs_html": "<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops\">Zurich Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html\">Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/using-tsom.html\">Using Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<span class=\"active\">Run Telecom Discrepancy audit</span>",
"bundle_id": "zurich-telecom-service-ops",
"bundle_key": 2733,
"bundle_landing_page": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html",
"bundle_subtitle": null,
"bundle_title": "Zurich Telecommunications Service Operations Management",
"canonical_link": null,
"dates": {
"Added on": "2025-08-02T00:48:08.794016Z",
"Created on": "2025-07-10T00:00:00Z",
"Initial upload": "2025-07-30T22:24:33.519043Z",
"Updated on": "2025-07-31T00:00:00Z"
},
"dislike_url": "https://servicenow-be-prod.servicenow.com/dislike/55686980",
"dislikes": 0,
"es_archived_content": false,
"is_in_fav": false,
"is_liked": null,
"is_watched": false,
"keywords": [
" zurich zurich"
],
"labels": [
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "zurich",
"navtitle": "Zurich",
"outputclasses": [],
"subjectHeadId": "versions",
"subjectheadNavtitle": "Versions",
"visibility": "show-facet"
},
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "tsom",
"navtitle": "Telecommunications Service Operations Management",
"outputclasses": [],
"subjectHeadId": "products",
"subjectheadNavtitle": "Products",
"visibility": "show-facet"
}
],
"labels_text": "Versions > Zurich; Products > CRM and Industry Products > Telecommunications Media and Technology Assurance > Telecommunications Service Operations Management",
"like_url": "https://servicenow-be-prod.servicenow.com/like/55686980",
"likes": 0,
"metadata": {
"AI Search": null,
"AI Search Assist": null,
"Application Insights": null,
"Capabilities": null,
"Code Signing": null,
"Contextual Search": null,
"DC.contributor": null,
"DC.coverage": null,
"DC.creator": "ServiceNow",
"DC.date.created": "2025-07-10T16:03:44+05:30",
"DC.date.modified": "2025-07-31",
"DC.format": "HTML5",
"DC.identifier": "run-audits",
"DC.language": null,
"DC.relation": "../../../product/tmt-telecom-service-operations-mgt/concept/using-tsom.html",
"DC.rights.owner": "(C) Copyright 2025",
"DC.subject": null,
"DC.type": "dita",
"Data Discovery": null,
"Data Policy": null,
"Data Privacy": null,
"Discovery": null,
"External Content for AI Search": null,
"Field Administration": null,
"Field Normalization": null,
"Key Management Framework": null,
"Localization Framework": null,
"Now Platform": null,
"PlatSec": null,
"Platform": null,
"Platform Administration": null,
"Platform Performance": null,
"Platform Privacy": null,
"Proactive Triggers": null,
"Process Optimization": null,
"RN doc editing record number": null,
"Search Administration": null,
"Secrets Management": null,
"ServiceNow AI Platform": null,
"State Model": null,
"Subscription Management": null,
"Task Communications Management": null,
"Timeline Visualizations": null,
"User Administration": null,
"User Experience Analytics": null,
"Zing": null,
"ai-now-assist": null,
"app-name": null,
"app_route": null,
"azureapimanagemen": null,
"change-completed": null,
"change-item": null,
"change-request-id": null,
"change-request-reference": null,
"com.glide.embedded_help.category": null,
"component": null,
"copyright": "(C) Copyright 2025",
"crossroads": null,
"data": null,
"description": "The Telecom Discrepancy Audit validates the integrity of configuration items (CIs) and relationships across your telecom inventory using the CMDB Compliance framework.",
"dominant_bundle": null,
"erp-canvas-video": null,
"fsm-mobile": null,
"fsm-route": null,
"fsm-sched-opt": null,
"fsm-wrk-order": null,
"genai-round-7": null,
"generator": "DITA-OT",
"glossPartOfSpeech": null,
"glossStatus": null,
"guided setup": null,
"guided tours": null,
"keywords": null,
"min-toc": null,
"mini": null,
"mini-to truec": null,
"mini-toc": "yes",
"mini_toc": null,
"minitoc": null,
"modification": null,
"now-assist-app-gen-video": null,
"order": null,
"page-type": null,
"page-type ": null,
"prodname": null,
"product": null,
"product_name": null,
"release": null,
"resourceID": null,
"roles": null,
"route_page": null,
"route_params_listId": null,
"route_params_table": null,
"route_params_type": null,
"route_type": null,
"setconfigurationproperties": null,
"topic": null,
"translation-type": "source",
"version": null,
"workflow": "Customer and Industry",
"workplace-srvc-delvry-ditamap": null
},
"page_id": "product/tmt-telecom-service-operations-mgt/task/run-audits.html",
"page_key": 55686980,
"preprocessed_PDF": "https://downloads.docs.servicenow.com/pdf/enus/servicenow-zurich-telecom-service-ops-enus.pdf",
"rating": null,
"read_time_data": {
"char_count": 5441,
"img_count": 4,
"read_time": 4,
"video_links": [
""
],
"word_count": 787
},
"related_links": [
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "Define filtering conditions to control the scope of Telecom Discrepancy audits. These filters ensure that audits run only on the desired set of CIs, improving performance and targeting accuracy.",
"title": "Configure filter for audit",
"topic": "/product/tmt-telecom-service-operations-mgt/task/configure-certification-filter-for-audit.html",
"type": "task",
"url": null
},
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "The following example illustrates how the audit works in a scenario.",
"title": "Example for Telecom Discrepancy Audit and Remediation",
"topic": "/product/tmt-telecom-service-operations-mgt/task/run-audits.html",
"type": "task",
"url": null
},
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "Use the Telecom Discrepancy Identification and Reconciliation capability to keep your CMDB or Telecommunications Network Inventory (TNI) in sync with your live telecom network. By continuously auditing and comparing discovered data with inventory records, this solution helps you detect, classify, and automatically remediate inconsistencies before they impact service quality, assurance, or fulfillment processes.",
"title": "Telecom Discrepancy Identification and Reconciliation",
"topic": "/product/tmt-telecom-service-operations-mgt/concept/exploring-telecom-reconciliation.html",
"type": "concept",
"url": null
},
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "The Telecom Discrepancy Identification and Reconciliation capability identifies and classifies mismatches between the network state (as discovered through TSOM Discovery or Service Graph Connectors) and the inventory data stored in the CMDB or TNI.",
"title": "Discrepancy identification – types of discrepancies",
"topic": "/product/tmt-telecom-service-operations-mgt/concept/discrepancy-identification-types-of-discrepancies.html",
"type": "concept",
"url": null
},
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "The system properties are part of the TSOM Visibility plugin (sn_tsom_core) and control the Telecom Discrepancy Identification & Reconciliation log (TSOM CMDB Audit). The TSOM Visibility plugin serves as an enabler for the TSOM Visibility applications, containing logic that is shared across the Telecom Discovery and Telecom Discrepancy Identification & Reconciliation solution.",
"title": "System components installed with Telecom Discrepancy Identification & Reconciliation",
"topic": "/product/tmt-telecom-service-operations-mgt/concept/system-properties-affecting-telecom-discrepancy-identification-reconciliation.html",
"type": "concept",
"url": null
},
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "Activate the Telecom Discrepancy Identification and Reconciliation feature (part of the Telecom Visibility plugin) to ensure consistency between telecom network resources discovered in the live network and the data represented in the CMDB or Telecom Network Inventory (TNI). This feature helps detect and remediate mismatches automatically, supporting service accuracy and data integrity across your telecom environment.",
"title": "Activate Telecom Discrepancy Identification and Reconciliation",
"topic": "/product/tmt-telecom-service-operations-mgt/task/configure-telecom-reconciliation.html",
"type": "task",
"url": null
},
{
"bundle": null,
"role": null,
"scope": "external",
"shortDes": null,
"title": "Defining UI actions",
"topic": null,
"type": null,
"url": "https://docs.servicenow.com/csh?topicname=c_UIActions&version=zurich&pubname=zurich-platform-administration"
}
],
"search_title": null,
"title": "Run Telecom Discrepancy audit",
"topic_cluster": {
"clustered_by": {
"enabled": true,
"primary_key": "versions",
"primary_sort": "top-down",
"type": "subjecthead"
},
"clustered_labels": [
"versions"
],
"clustered_topics": [],
"clustering_title": "Zurich"
},
"topic_html": "<article class=\"hascomments\" data-page=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/run-audits.html\" id=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/run-audits.html\"><body><main role=\"main\"><article role=\"article\" class=\"dita\" aria-labelledby=\"title_run-audits\"><article class=\"nested0\" aria-labelledby=\"title_run-audits\" id=\"run-audits\">\n <h1 class=\"title topictitle1\" id=\"title_run-audits\">Run Telecom Discrepancy audit</h1>\n \n \n <div class=\"body taskbody\"><p class=\"shortdesc\">The Telecom Discrepancy Audit validates the integrity of configuration items (CIs) and relationships across your telecom inventory using the CMDB Compliance framework. </p>\n <section class=\"section prereq\" id=\"run-audits__task-prereq\"><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">Before you begin</p></div>\n <p class=\"p\">Role required: admin</p>\n </section>\n <section class=\"section context\" id=\"run-audits__context_ypb_vbc_yfc\"><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">About this task</p></div>\n <p class=\"p\">The Telecom Discrepancy Audit is part of the CMDB Compliance framework and supports phased auditing to detect and address discrepancies in CI relationships and attributes discovered through ServiceNow Discovery or Service\n Graph Connectors (for example, Nokia Altiplano).</p>\n <p class=\"p\">You can run the audit manually or set it to run at regular intervals. During manual execution, you can select from existing filters to limit the audit scope to specific CIs—helpful for testing or targeted reconciliation.</p>\n <div class=\"p\">The Telecom Discrepancy Audit works in two phases:<ol class=\"ol\" id=\"run-audits__ol_cfk_yyn_xfc\">\n <li class=\"li\">Initial compliance run: Validates CI relationships and selected CI tables using the following default criteria:<ul class=\"ul\" id=\"run-audits__ul_ydk_qyn_xfc\">\n <li class=\"li\">Supported CI classes: Slot, Subslot, Card, Interface, Network Gear (includes all extension tables).</li>\n <li class=\"li\">Source: CI was discovered via Discovery (For example <code class=\"ph codeph\">discovery_source = SG-TSOM-Altiplano</code>).</li>\n <li class=\"li\">Relationship type: <code class=\"ph codeph\">Contains::Contained By</code> (customizable via <code class=\"ph codeph\">sn_tsom_core.audit.relationship_types</code> property).</li>\n </ul></li>\n <li class=\"li\">Subsequent compliance runs: In addition to initial checks, evaluates whether the Updated timestamp of the relationship or related CIs is more recent than the Last run date in the audit record.<div class=\"note note note_note\"><span class=\"note__title\">Note:</span> Each failed audit\n creates a Follow-On Task for manual or automated remediation, confirming telecom CMDB data stays aligned with the network state.</div></li>\n </ol></div>\n <p class=\"p\">The following screenshot helps you understand the Telecom Discrepancy Audit.<img src=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/../images/telecom-discrepancy-audit.png?_LANG=enus\" class=\"image\" id=\"run-audits__image_w5j_lrd_zfc\" alt=\"The user interface of the telecom discrepancy audit.\"/></p>\n </section>\n <section id=\"run-audits__steps_vzt_tbc_yfc\"><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">Procedure</p></div><ol class=\"ol steps\" id=\"run-audits__steps_vzt_tbc_yfc\"><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">Navigate to <span class=\"ph menucascade\"><span class=\"ph uicontrol\">All</span><abbr> > </abbr><span class=\"ph uicontrol\">Compliance</span><abbr> > </abbr><span class=\"ph uicontrol\">Audits</span></span></span>\n </li><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">Open the Telecom Discrepancy Audit (cert_audit table) record.</span>\n </li><li class=\"li step stepexpand\">(Optional) \n <span class=\"ph cmd\">Select a filter.</span>\n <div class=\"itemgroup info\">\n <ul class=\"ul\" id=\"run-audits__ul_olp_mcn_zfc\">\n <li class=\"li\">If multiple audit filters have been defined during configuration, you can choose one before running the audit.</li>\n <li class=\"li\">Filters enable you to restrict the audit scope based on criteria such as discovery source, CI class, or specific CI attributes.</li>\n <li class=\"li\">This step is especially useful when troubleshooting a subset of records or validating specific discovery results.</li>\n </ul>\n </div>\n </li><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">Do either of the following to run the audit.</span>\n <ul class=\"ul choices\" id=\"run-audits__choices_tsn_vcn_zfc\">\n <li class=\"li choice\">Click <span class=\"ph uicontrol\">Run Audit</span> to trigger a manual execution.</li>\n <li class=\"li choice\">Configure the audit to run on a scheduled basis by setting up a recurring job.</li>\n </ul>\n <div class=\"itemgroup stepresult\">The audit uses CMDB Compliance to validate relationship and CI integrity across telecom inventory.</div>\n </li></ol></section>\n <section class=\"section result\" id=\"run-audits__result_rz5_cdn_zfc\"><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">Result</p></div>\n <div class=\"p\">Review audit results<ul class=\"ul\" id=\"run-audits__ul_l5z_zcn_zfc\">\n <li class=\"li\">The audit identifies compliance failures such as missing relationships or misaligned attributes.</li>\n <li class=\"li\">For each failed audit record, a Follow-On Task is automatically generated.</li>\n <li class=\"li\">Tasks include recommended or automated remediation actions such as updating or decommissioning CIs.</li>\n </ul></div>\n <p class=\"p\">Example use case: The configured filters can be used for different discovery sources. For example, the Nokia Altiplano. When running the audit manually, you can select the appropriate filter to validate only those CIs\n discovered by that specific source—confirming targeted and efficient auditing.</p>\n </section>\n </div>\n <nav role=\"navigation\"></nav><nav role=\"navigation\" class=\"tasksNavigation\"></nav><nav role=\"navigation\" class=\"related-links\"><div class=\"col-md-4\"><dt>Related tasks</dt><dd><ul><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/task/configure-certification-filter-for-audit.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/configure-certification-filter-for-audit.html\" class=\"link\" title=\"Define filtering conditions to control the scope of Telecom Discrepancy audits. These filters ensure that audits run only on the desired set of CIs, improving performance and targeting accuracy.\">Configure filter for audit</a></li><li><a class=\"link\" href=\"#example-for-telecom-discrepancy-and-reconciliation\" title=\"The following example illustrates how the audit works in a scenario.\">Example for Telecom Discrepancy Audit and Remediation</a></li></ul></dd></div></nav>\n<article class=\"topic task nested1\" aria-labelledby=\"title_example-for-telecom-discrepancy-and-reconciliation\" id=\"example-for-telecom-discrepancy-and-reconciliation\">\n <h2 class=\"title topictitle2\" id=\"title_example-for-telecom-discrepancy-and-reconciliation\">Example for Telecom Discrepancy Audit and Remediation</h2>\n \n \n <div class=\"body taskbody\"><p class=\"shortdesc\">The following example illustrates how the audit works in a scenario.</p>\n <section class=\"section prereq\" id=\"example-for-telecom-discrepancy-and-reconciliation__task-prereq\"><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">Before you begin</p></div>\n <p class=\"p\">Role required: admin</p>\n </section>\n <section class=\"section context\" id=\"example-for-telecom-discrepancy-and-reconciliation__context_qbq_2zd_wfc\"><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">About this task</p></div><p class=\"p\">A card (Card04) was initially discovered in Slot04. Later, Card04 was replaced by Card05 in the physical network, but the CMDB still shows Card04 in Slot04. When a new discovery run executes, Card05\n is discovered and added to the same slot, creating a data conflict in CMDB.</p><p class=\"p\">Audit Behavior:</p><ul class=\"ul\" id=\"example-for-telecom-discrepancy-and-reconciliation__ul_zls_d3c_yfc\">\n <li class=\"li\">The Telecom Discrepancy Audit detects this inconsistency and creates a failed audit record (e.g., <code class=\"ph codeph\">AUDR0001283</code>).</li>\n <li class=\"li\">A Follow-On Task is created automatically (e.g., <code class=\"ph codeph\">TASK0020215</code>) with a detailed description of the discrepancy.</li>\n </ul><p class=\"p\">Task Description Example (Incorrect Number of Relationships):</p><div class=\"p\">Card04 was last discovered more than 2.5 days ago.<div class=\"table-wrap\"><table count-columns=\"2\" class=\"table frame-all\" id=\"example-for-telecom-discrepancy-and-reconciliation__table_z5y_m3c_yfc\"><caption><span class=\"table--title-label\">Table 1. </span><span class=\"title\">Relationships between the following CIs</span></caption><colgroup><col style=\"width:50%\"/><col style=\"width:50%\"/></colgroup><thead class=\"thead\">\n <tr class=\"row\">\n <th class=\"entry colsep-1 rowsep-1\" id=\"example-for-telecom-discrepancy-and-reconciliation__table_z5y_m3c_yfc__entry__1\">CI</th>\n <th class=\"entry colsep-1 rowsep-1\" id=\"example-for-telecom-discrepancy-and-reconciliation__table_z5y_m3c_yfc__entry__2\">Model</th>\n </tr>\n </thead><tbody class=\"tbody\">\n <tr class=\"row\">\n <td class=\"entry colsep-1 rowsep-1\" headers=\"example-for-telecom-discrepancy-and-reconciliation__table_z5y_m3c_yfc__entry__1\">Slot04</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"example-for-telecom-discrepancy-and-reconciliation__table_z5y_m3c_yfc__entry__2\">DEMO 20532Tree</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry colsep-1 rowsep-1\" headers=\"example-for-telecom-discrepancy-and-reconciliation__table_z5y_m3c_yfc__entry__1\">Card04</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"example-for-telecom-discrepancy-and-reconciliation__table_z5y_m3c_yfc__entry__2\">Nokia 7360 FANT-F CARD MODULE</td>\n </tr>\n <tr class=\"row\">\n <td class=\"entry colsep-1 rowsep-1\" headers=\"example-for-telecom-discrepancy-and-reconciliation__table_z5y_m3c_yfc__entry__1\">Card05</td>\n <td class=\"entry colsep-1 rowsep-1\" headers=\"example-for-telecom-discrepancy-and-reconciliation__table_z5y_m3c_yfc__entry__2\"><model not identified></td>\n </tr>\n </tbody></table></div></div><p class=\"p\">The following snapshots will help you understand the discrepancy and remediation process.</p><p class=\"p\"><img src=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/../images/telecom-run-audits.png?_LANG=enus\" class=\"image\" id=\"example-for-telecom-discrepancy-and-reconciliation__image_g4b_znj_b2c\" alt=\"run audit.\"/></p><img src=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/../images/telecom-ui-actions.png?_LANG=enus\" class=\"image\" id=\"example-for-telecom-discrepancy-and-reconciliation__image_z4b_k4j_b2c\" alt=\"UI actions.\"/><p class=\"p\"><img src=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/../images/telecom-subflow.png?_LANG=enus\" class=\"image\" id=\"example-for-telecom-discrepancy-and-reconciliation__image_mcn_fcd_yfc\" alt=\"example subflow.\"/></p></section>\n <section><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">Procedure</p></div><ol class=\"ol steps\"><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">Navigate <span class=\"ph menucascade\"><span class=\"ph uicontrol\">All</span><abbr> > </abbr><span class=\"ph uicontrol\">Compliance</span><abbr> > </abbr><span class=\"ph uicontrol\">Audits</span><abbr> > </abbr><span class=\"ph uicontrol\">Telecom Discrepancy Audit</span><abbr> > </abbr><span class=\"ph uicontrol\">Run Audits</span></span>.</span>\n <div class=\"itemgroup stepresult\">A Follow-on Task is automatically created for each failed audit record (for example, TASK0020215).</div>\n </li><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">Select <span class=\"ph uicontrol\">TASK0020215</span> and review the discrepancy description.</span>\n <div class=\"itemgroup info\">\n <div class=\"note note note_note\"><span class=\"note__title\">Note:</span> This is an example of the TASK0020215 description created for the "Incorrect number of relationships" scenario. Other scenarios and environments might have different descriptions.</div>\n </div>\n <div class=\"itemgroup stepresult\">The Follow-On Task contains a detailed description of the discrepancy. As you can see in the description, the Card04 CI is in discrepancy.</div>\n </li><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">To remediate, perform the following steps:</span>\n <ol type=\"a\" class=\"ol substeps\">\n <li class=\"li substep substepexpand\">\n <span class=\"ph cmd\">Navigate <span class=\"ph menucascade\"><span class=\"ph uicontrol\">All</span><abbr> > </abbr><span class=\"ph uicontrol\">System Definition</span><abbr> > </abbr><span class=\"ph uicontrol\">UI Actions</span></span>.</span>\n </li>\n <li class=\"li substep substepexpand\">\n <span class=\"ph cmd\">Select <span class=\"ph uicontrol\">Remediate</span>.</span>\n <div class=\"itemgroup stepresult\">The Remediate button is a UI action that triggers the <code class=\"ph codeph\">TSOM CI Decommission</code> subflow. This subflow:<ul class=\"ul\" id=\"example-for-telecom-discrepancy-and-reconciliation__ul_hpd_3bd_yfc\">\n <li class=\"li\">Retires the outdated Card04 CI.</li>\n <li class=\"li\">Removes the incorrect Slot04 → Card04 relationship.</li>\n <li class=\"li\">Synchronizes CMDB records with the network state.</li>\n </ul></div>\n </li>\n </ol>\n </li></ol></section>\n <section class=\"section result\" id=\"example-for-telecom-discrepancy-and-reconciliation__result_zvt_mbd_yfc\"><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">Result</p></div>\n <p class=\"p\">After remediation:</p>\n <ul class=\"ul\" id=\"example-for-telecom-discrepancy-and-reconciliation__ul_gwy_mbd_yfc\">\n <li class=\"li\">The Follow-On Task (<code class=\"ph codeph\">TASK0020215</code>) updates with work notes summarizing the resolution steps.</li>\n <li class=\"li\">The Card04 CI is marked as retired, and incorrect relationships are removed.</li>\n <li class=\"li\">CMDB is now aligned with the latest discovered state from the network.</li>\n </ul>\n <div class=\"note note note_note\"><span class=\"note__title\">Note:</span> Customize Remediation - The Telecom Discrepancy Audit ships with example remediation subflows. You can create and attach custom subflows using Flow Designer to suit your operational requirements.</div>\n </section>\n </div>\n <nav role=\"navigation\"></nav><nav role=\"navigation\" class=\"tasksNavigation\"></nav><nav role=\"navigation\" class=\"related-links\"><div class=\"col-md-4\"><dt>Related tasks</dt><dd><ul><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/task/configure-telecom-reconciliation.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/configure-telecom-reconciliation.html\" class=\"link\" title=\"Activate the Telecom Discrepancy Identification and Reconciliation feature (part of the Telecom Visibility plugin) to ensure consistency between telecom network resources discovered in the live network and the data represented in the CMDB or Telecom Network Inventory (TNI). This feature helps detect and remediate mismatches automatically, supporting service accuracy and data integrity across your telecom environment.\">Activate Telecom Discrepancy Identification and Reconciliation</a></li></ul></dd></div><div class=\"col-md-4\"><dt>Related concepts</dt><dd><ul><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept/exploring-telecom-reconciliation.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/exploring-telecom-reconciliation.html\" class=\"link\" title=\"Use the Telecom Discrepancy Identification and Reconciliation capability to keep your CMDB or Telecommunications Network Inventory (TNI) in sync with your live telecom network. By continuously auditing and comparing discovered data with inventory records, this solution helps you detect, classify, and automatically remediate inconsistencies before they impact service quality, assurance, or fulfillment processes.\">Telecom Discrepancy Identification and Reconciliation</a></li><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept/discrepancy-identification-types-of-discrepancies.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/discrepancy-identification-types-of-discrepancies.html\" class=\"link\" title=\"The Telecom Discrepancy Identification and Reconciliation capability identifies and classifies mismatches between the network state (as discovered through TSOM Discovery or Service Graph Connectors) and the inventory data stored in the CMDB or TNI.\">Discrepancy identification – types of discrepancies</a></li><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/concept/system-properties-affecting-telecom-discrepancy-identification-reconciliation.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/system-properties-affecting-telecom-discrepancy-identification-reconciliation.html\" class=\"link\" title=\"The system properties are part of the TSOM Visibility plugin (sn_tsom_core) and control the Telecom Discrepancy Identification & Reconciliation log (TSOM CMDB Audit). The TSOM Visibility plugin serves as an enabler for the TSOM Visibility applications, containing logic that is shared across the Telecom Discovery and Telecom Discrepancy Identification & Reconciliation solution.\">System components installed with Telecom Discrepancy Identification & Reconciliation</a></li></ul></dd></div><div class=\"col-md-4\"><dt>Related topics</dt><dd><ul><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/task//csh\" href=\"https://servicenow-be-prod.servicenow.com/csh?topicname=c_UIActions&version=zurich&pubname=zurich-platform-administration\" class=\"link\">Defining UI actions</a></li></ul></dd></div></nav>\n</article></article></article></main></body></article>",
"topic_language": "enus",
"views": 0,
"your_rating": null
} | # 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.
## Before you begin
Role required: admin
## About this task
The Telecom Discrepancy Audit is part of the CMDB Compliance framework and supports phased auditing to detect and address discrepancies in CI relationships and attributes discovered through ServiceNow Discovery or Service
Graph Connectors (for example, Nokia Altiplano).
You can run the audit manually or set it to run at regular intervals. During manual execution, you can select from existing filters to limit the audit scope to specific CIs—helpful for testing or targeted reconciliation.
The Telecom Discrepancy Audit works in two phases:
1. Initial compliance run: Validates CI relationships and selected CI tables using the following default criteria:
* Supported CI classes: Slot, Subslot, Card, Interface, Network Gear (includes all extension tables).
* Source: CI was discovered via Discovery (For example `discovery_source = SG-TSOM-Altiplano`).
* Relationship type: `Contains::Contained By` (customizable via `sn_tsom_core.audit.relationship_types` property).
2. Subsequent compliance runs: In addition to initial checks, evaluates whether the Updated timestamp of the relationship or related CIs is more recent than the Last run date in the audit record.Note: Each failed audit
creates a Follow-On Task for manual or automated remediation, confirming telecom CMDB data stays aligned with the network state.
The following screenshot helps you understand the Telecom Discrepancy Audit.
## Procedure
1. Navigate to All > Compliance > Audits
2. Open the Telecom Discrepancy Audit (cert\_audit table) record.
3. (Optional)
Select a filter.
* If multiple audit filters have been defined during configuration, you can choose one before running the audit.
* Filters enable you to restrict the audit scope based on criteria such as discovery source, CI class, or specific CI attributes.
* This step is especially useful when troubleshooting a subset of records or validating specific discovery results.
4. Do either of the following to run the audit.
* Click Run Audit to trigger a manual execution.
* Configure the audit to run on a scheduled basis by setting up a recurring job.The audit uses CMDB Compliance to validate relationship and CI integrity across telecom inventory.
### Result
Review audit results
* The audit identifies compliance failures such as missing relationships or misaligned attributes.
* For each failed audit record, a Follow-On Task is automatically generated.
* Tasks include recommended or automated remediation actions such as updating or decommissioning CIs.
Example use case: The configured filters can be used for different discovery sources. For example, the Nokia Altiplano. When running the audit manually, you can select the appropriate filter to validate only those CIs
discovered by that specific source—confirming targeted and efficient auditing.
## Example for Telecom Discrepancy Audit and Remediation
The following example illustrates how the audit works in a scenario.
## Before you begin
Role required: admin
## About this task
A card (Card04) was initially discovered in Slot04. Later, Card04 was replaced by Card05 in the physical network, but the CMDB still shows Card04 in Slot04. When a new discovery run executes, Card05
is discovered and added to the same slot, creating a data conflict in CMDB.
Audit Behavior:
* The Telecom Discrepancy Audit detects this inconsistency and creates a failed audit record (e.g., `AUDR0001283`).
* A Follow-On Task is created automatically (e.g., `TASK0020215`) with a detailed description of the discrepancy.
Task Description Example (Incorrect Number of Relationships):
Card04 was last discovered more than 2.5 days ago.
Table 1. Relationships between the following CIs
| CI | Model |
| --- | --- |
| Slot04 | DEMO 20532Tree |
| Card04 | Nokia 7360 FANT-F CARD MODULE |
| Card05 | <model not identified> |
The following snapshots will help you understand the discrepancy and remediation process.
## Procedure
1. Navigate All > Compliance > Audits > Telecom Discrepancy Audit > Run Audits.
A Follow-on Task is automatically created for each failed audit record (for example, TASK0020215).
2. Select TASK0020215 and review the discrepancy description.
Note: This is an example of the TASK0020215 description created for the "Incorrect number of relationships" scenario. Other scenarios and environments might have different descriptions.
The Follow-On Task contains a detailed description of the discrepancy. As you can see in the description, the Card04 CI is in discrepancy.
3. To remediate, perform the following steps:
1. Navigate All > System Definition > UI Actions.
2. Select Remediate.
The Remediate button is a UI action that triggers the `TSOM CI Decommission` subflow. This subflow:
* Retires the outdated Card04 CI.
* Removes the incorrect Slot04 → Card04 relationship.
* Synchronizes CMDB records with the network state.
### Result
After remediation:
* The Follow-On Task (`TASK0020215`) updates with work notes summarizing the resolution steps.
* The Card04 CI is marked as retired, and incorrect relationships are removed.
* CMDB is now aligned with the latest discovered state from the network.
Note: Customize Remediation - The Telecom Discrepancy Audit ships with example remediation subflows. You can create and attach custom subflows using Flow Designer to suit your operational requirements.
| ---
title: Run Telecom Discrepancy audit
description: The Telecom Discrepancy Audit validates the integrity of configuration
items (CIs) and relationships across your telecom inventory using the CMDB Compliance
framework.
keywords: []
breadcrumbs:
- Telecommunications Service Operations Management
- Using Telecommunications Service Operations Management
---
# 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.
## Before you begin
Role required: admin
## About this task
The Telecom Discrepancy Audit is part of the CMDB Compliance framework and supports phased auditing to detect and address discrepancies in CI relationships and attributes discovered through ServiceNow Discovery or Service
Graph Connectors (for example, Nokia Altiplano).
You can run the audit manually or set it to run at regular intervals. During manual execution, you can select from existing filters to limit the audit scope to specific CIs—helpful for testing or targeted reconciliation.
The Telecom Discrepancy Audit works in two phases:
1. Initial compliance run: Validates CI relationships and selected CI tables using the following default criteria:
* Supported CI classes: Slot, Subslot, Card, Interface, Network Gear (includes all extension tables).
* Source: CI was discovered via Discovery (For example `discovery_source = SG-TSOM-Altiplano`).
* Relationship type: `Contains::Contained By` (customizable via `sn_tsom_core.audit.relationship_types` property).
2. Subsequent compliance runs: In addition to initial checks, evaluates whether the Updated timestamp of the relationship or related CIs is more recent than the Last run date in the audit record.Note: Each failed audit
creates a Follow-On Task for manual or automated remediation, confirming telecom CMDB data stays aligned with the network state.
The following screenshot helps you understand the Telecom Discrepancy Audit.
## Procedure
1. Navigate to All > Compliance > Audits
2. Open the Telecom Discrepancy Audit (cert\_audit table) record.
3. (Optional)
Select a filter.
* If multiple audit filters have been defined during configuration, you can choose one before running the audit.
* Filters enable you to restrict the audit scope based on criteria such as discovery source, CI class, or specific CI attributes.
* This step is especially useful when troubleshooting a subset of records or validating specific discovery results.
4. Do either of the following to run the audit.
* Click Run Audit to trigger a manual execution.
* Configure the audit to run on a scheduled basis by setting up a recurring job.The audit uses CMDB Compliance to validate relationship and CI integrity across telecom inventory.
### Result
Review audit results
* The audit identifies compliance failures such as missing relationships or misaligned attributes.
* For each failed audit record, a Follow-On Task is automatically generated.
* Tasks include recommended or automated remediation actions such as updating or decommissioning CIs.
Example use case: The configured filters can be used for different discovery sources. For example, the Nokia Altiplano. When running the audit manually, you can select the appropriate filter to validate only those CIs
discovered by that specific source—confirming targeted and efficient auditing.
## Example for Telecom Discrepancy Audit and Remediation
The following example illustrates how the audit works in a scenario.
## Before you begin
Role required: admin
## About this task
A card (Card04) was initially discovered in Slot04. Later, Card04 was replaced by Card05 in the physical network, but the CMDB still shows Card04 in Slot04. When a new discovery run executes, Card05
is discovered and added to the same slot, creating a data conflict in CMDB.
Audit Behavior:
* The Telecom Discrepancy Audit detects this inconsistency and creates a failed audit record (e.g., `AUDR0001283`).
* A Follow-On Task is created automatically (e.g., `TASK0020215`) with a detailed description of the discrepancy.
Task Description Example (Incorrect Number of Relationships):
Card04 was last discovered more than 2.5 days ago.
Table 1. Relationships between the following CIs
| CI | Model |
| --- | --- |
| Slot04 | DEMO 20532Tree |
| Card04 | Nokia 7360 FANT-F CARD MODULE |
| Card05 | <model not identified> |
The following snapshots will help you understand the discrepancy and remediation process.
## Procedure
1. Navigate All > Compliance > Audits > Telecom Discrepancy Audit > Run Audits.
A Follow-on Task is automatically created for each failed audit record (for example, TASK0020215).
2. Select TASK0020215 and review the discrepancy description.
Note: This is an example of the TASK0020215 description created for the "Incorrect number of relationships" scenario. Other scenarios and environments might have different descriptions.
The Follow-On Task contains a detailed description of the discrepancy. As you can see in the description, the Card04 CI is in discrepancy.
3. To remediate, perform the following steps:
1. Navigate All > System Definition > UI Actions.
2. Select Remediate.
The Remediate button is a UI action that triggers the `TSOM CI Decommission` subflow. This subflow:
* Retires the outdated Card04 CI.
* Removes the incorrect Slot04 → Card04 relationship.
* Synchronizes CMDB records with the network state.
### Result
After remediation:
* The Follow-On Task (`TASK0020215`) updates with work notes summarizing the resolution steps.
* The Card04 CI is marked as retired, and incorrect relationships are removed.
* CMDB is now aligned with the latest discovered state from the network.
Note: Customize Remediation - The Telecom Discrepancy Audit ships with example remediation subflows. You can create and attach custom subflows using Flow Designer to suit your operational requirements.
|
https://www.servicenow.com/docs/en-US/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/update-data-source-of-the-connector.html | https://servicenow-be-prod.servicenow.com/api/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/update-data-source-of-the-connector.html | 2025-08-02 | daily | 0.5 | 268.xml | en-US | zurich-telecom-service-ops | product/tmt-telecom-service-operations-mgt/task/update-data-source-of-the-connector.html | zurich | Update the data source of the connector | Link the duplicated ETL to a valid data source for your specific connector. | [] | [
"Telecommunications Service Operations Management",
"Configuring Telecommunications Service Operations Management",
"Set up Telecom Visibility",
"Configuring the Telecom Discovery Builder framework ETL in a connector"
] | <article class="hascomments" data-page="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/update-data-source-of-the-connector.html" id="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/update-data-source-of-the-connector.html"><body id="update-data-source-of-the-connector"><main role="main"><article role="article" class="dita" id="update-data-source-of-the-connector" aria-labelledby="title_update-data-source-of-the-connector">
<h1 class="title topictitle1" id="title_update-data-source-of-the-connector">Update the data source of the connector</h1>
<div class="body taskbody"><p class="shortdesc">Link the duplicated ETL to a valid data source for your specific connector.</p>
<section class="section prereq" id="update-data-source-of-the-connector__task-prereq"><div class="tasklabel"><p class="sectiontitle tasklabel">Before you begin</p></div>
<p class="p">Role required: admin</p>
</section>
<section class="section context" id="update-data-source-of-the-connector__context_gfj_jhw_vfc"><div class="tasklabel"><p class="sectiontitle tasklabel">About this task</p></div>
<p class="p">The following screenshot can help you to replace the default source with your connector's data source.<img src="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/../images/replace-datasource.png?_LANG=enus" class="image" id="update-data-source-of-the-connector__image_fmp_lhw_vfc" alt="Specify basic details user interface displaying the selection of data source to replace the default data source"/></p>
</section>
<section><div class="tasklabel"><p class="sectiontitle tasklabel">Procedure</p></div><ol class="ol steps"><li class="li step stepexpand">
<span class="ph cmd">Navigate to <span class="ph menucascade"><span class="ph uicontrol">All</span><abbr> > </abbr><span class="ph uicontrol">IntegrationHub ETL</span></span>.</span>
</li><li class="li step stepexpand">
<span class="ph cmd">In <span class="ph uicontrol">Specify Basic Details</span>, replace the default data source with your connector’s data source.</span>
</li><li class="li step stepexpand">
<span class="ph cmd">Select <span class="ph uicontrol">Save</span>.</span>
</li><li class="li step stepexpand">
<span class="ph cmd">Open <span class="ph uicontrol">Import Schedules</span> and run your data source.</span>
<div class="itemgroup stepresult">The system creates a new transform map based on the selected settings and create CIs generated from your payload.</div>
</li></ol></section>
</div>
<nav role="navigation"></nav><nav role="navigation" class="tasksNavigation"></nav><nav role="navigation" class="related-links"><div class="col-md-4"><dt>Related tasks</dt><dd><ul><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/task/deploy-a-new-service-graph-connector-with-duplicated-etl.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/deploy-a-new-service-graph-connector-with-duplicated-etl.html" class="link" title="Associate a new Service Graph Connector (SGC) with an existing ETL.">Deploy a new service graph connector with existing ETL</a></li></ul></dd></div></nav>
</article></main></body></article> | {
"attachments": {
"all_attachments": null,
"topic_attachments": []
},
"available_languages": [
"enus"
],
"breadcrumbs": [
{
"title": "Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html"
},
{
"title": "Configuring Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/configuring-tsom.html"
},
{
"title": "Set up Telecom Visibility",
"topic_id": "product/tmt-telecom-service-operations-mgt/task/configuring-tsom-visibility.html"
},
{
"title": "Configuring the Telecom Discovery Builder framework ETL in a connector",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/configuring-the-telco-generic-schema-etl.html"
}
],
"breadcrumbs_html": "<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops\">Zurich Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html\">Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/configuring-tsom.html\">Configuring Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/configuring-tsom-visibility.html\">Set up Telecom Visibility</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/configuring-the-telco-generic-schema-etl.html\">Configuring the Telecom Discovery Builder framework ETL in a connector</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<span class=\"active\">Update the data source of the connector</span>",
"bundle_id": "zurich-telecom-service-ops",
"bundle_key": 2733,
"bundle_landing_page": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html",
"bundle_subtitle": null,
"bundle_title": "Zurich Telecommunications Service Operations Management",
"canonical_link": null,
"dates": {
"Added on": "2025-08-02T00:48:08.794016Z",
"Created on": "2025-04-14T00:00:00Z",
"Initial upload": "2025-07-30T22:24:33.519043Z",
"Updated on": "2025-07-31T00:00:00Z"
},
"dislike_url": "https://servicenow-be-prod.servicenow.com/dislike/55686981",
"dislikes": 0,
"es_archived_content": false,
"is_in_fav": false,
"is_liked": null,
"is_watched": false,
"keywords": [
" zurich zurich"
],
"labels": [
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "zurich",
"navtitle": "Zurich",
"outputclasses": [],
"subjectHeadId": "versions",
"subjectheadNavtitle": "Versions",
"visibility": "show-facet"
},
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "tsom",
"navtitle": "Telecommunications Service Operations Management",
"outputclasses": [],
"subjectHeadId": "products",
"subjectheadNavtitle": "Products",
"visibility": "show-facet"
}
],
"labels_text": "Versions > Zurich; Products > CRM and Industry Products > Telecommunications Media and Technology Assurance > Telecommunications Service Operations Management",
"like_url": "https://servicenow-be-prod.servicenow.com/like/55686981",
"likes": 0,
"metadata": {
"AI Search": null,
"AI Search Assist": null,
"Application Insights": null,
"Capabilities": null,
"Code Signing": null,
"Contextual Search": null,
"DC.contributor": null,
"DC.coverage": null,
"DC.creator": "ServiceNow",
"DC.date.created": "2025-04-14T15:25:04+05:30",
"DC.date.modified": "2025-07-31",
"DC.format": "HTML5",
"DC.identifier": "update-data-source-of-the-connector",
"DC.language": null,
"DC.relation": "deploy-a-new-service-graph-connector-with-duplicated-etl.html",
"DC.rights.owner": "(C) Copyright 2025",
"DC.subject": null,
"DC.type": "task",
"Data Discovery": null,
"Data Policy": null,
"Data Privacy": null,
"Discovery": null,
"External Content for AI Search": null,
"Field Administration": null,
"Field Normalization": null,
"Key Management Framework": null,
"Localization Framework": null,
"Now Platform": null,
"PlatSec": null,
"Platform": null,
"Platform Administration": null,
"Platform Performance": null,
"Platform Privacy": null,
"Proactive Triggers": null,
"Process Optimization": null,
"RN doc editing record number": null,
"Search Administration": null,
"Secrets Management": null,
"ServiceNow AI Platform": null,
"State Model": null,
"Subscription Management": null,
"Task Communications Management": null,
"Timeline Visualizations": null,
"User Administration": null,
"User Experience Analytics": null,
"Zing": null,
"ai-now-assist": null,
"app-name": null,
"app_route": null,
"azureapimanagemen": null,
"change-completed": null,
"change-item": null,
"change-request-id": null,
"change-request-reference": null,
"com.glide.embedded_help.category": null,
"component": null,
"copyright": "(C) Copyright 2025",
"crossroads": null,
"data": null,
"description": "Link the duplicated ETL to a valid data source for your specific connector.",
"dominant_bundle": null,
"erp-canvas-video": null,
"fsm-mobile": null,
"fsm-route": null,
"fsm-sched-opt": null,
"fsm-wrk-order": null,
"genai-round-7": null,
"generator": "DITA-OT",
"glossPartOfSpeech": null,
"glossStatus": null,
"guided setup": null,
"guided tours": null,
"keywords": null,
"min-toc": null,
"mini": null,
"mini-to truec": null,
"mini-toc": null,
"mini_toc": null,
"minitoc": null,
"modification": null,
"now-assist-app-gen-video": null,
"order": null,
"page-type": null,
"page-type ": null,
"prodname": null,
"product": null,
"product_name": null,
"release": null,
"resourceID": null,
"roles": null,
"route_page": null,
"route_params_listId": null,
"route_params_table": null,
"route_params_type": null,
"route_type": null,
"setconfigurationproperties": null,
"topic": null,
"translation-type": "source",
"version": null,
"workflow": "Customer and Industry",
"workplace-srvc-delvry-ditamap": null
},
"page_id": "product/tmt-telecom-service-operations-mgt/task/update-data-source-of-the-connector.html",
"page_key": 55686981,
"preprocessed_PDF": "https://downloads.docs.servicenow.com/pdf/enus/servicenow-zurich-telecom-service-ops-enus.pdf",
"rating": null,
"read_time_data": {
"char_count": 551,
"img_count": 1,
"read_time": 1,
"video_links": [
""
],
"word_count": 91
},
"related_links": [
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "Associate a new Service Graph Connector (SGC) with an existing ETL.",
"title": "Deploy a new service graph connector with existing ETL",
"topic": "/product/tmt-telecom-service-operations-mgt/task/deploy-a-new-service-graph-connector-with-duplicated-etl.html",
"type": "task",
"url": null
}
],
"search_title": null,
"title": "Update the data source of the connector",
"topic_cluster": {
"clustered_by": {
"enabled": true,
"primary_key": "versions",
"primary_sort": "top-down",
"type": "subjecthead"
},
"clustered_labels": [
"versions"
],
"clustered_topics": [],
"clustering_title": "Zurich"
},
"topic_html": "<article class=\"hascomments\" data-page=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/update-data-source-of-the-connector.html\" id=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/update-data-source-of-the-connector.html\"><body id=\"update-data-source-of-the-connector\"><main role=\"main\"><article role=\"article\" class=\"dita\" id=\"update-data-source-of-the-connector\" aria-labelledby=\"title_update-data-source-of-the-connector\">\n <h1 class=\"title topictitle1\" id=\"title_update-data-source-of-the-connector\">Update the data source of the connector</h1>\n \n \n <div class=\"body taskbody\"><p class=\"shortdesc\">Link the duplicated ETL to a valid data source for your specific connector.</p>\n <section class=\"section prereq\" id=\"update-data-source-of-the-connector__task-prereq\"><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">Before you begin</p></div>\n <p class=\"p\">Role required: admin</p>\n </section>\n <section class=\"section context\" id=\"update-data-source-of-the-connector__context_gfj_jhw_vfc\"><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">About this task</p></div>\n <p class=\"p\">The following screenshot can help you to replace the default source with your connector's data source.<img src=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/../images/replace-datasource.png?_LANG=enus\" class=\"image\" id=\"update-data-source-of-the-connector__image_fmp_lhw_vfc\" alt=\"Specify basic details user interface displaying the selection of data source to replace the default data source\"/></p>\n </section>\n <section><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">Procedure</p></div><ol class=\"ol steps\"><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">Navigate to <span class=\"ph menucascade\"><span class=\"ph uicontrol\">All</span><abbr> > </abbr><span class=\"ph uicontrol\">IntegrationHub ETL</span></span>.</span>\n </li><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">In <span class=\"ph uicontrol\">Specify Basic Details</span>, replace the default data source with your connector’s data source.</span>\n </li><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">Select <span class=\"ph uicontrol\">Save</span>.</span>\n </li><li class=\"li step stepexpand\">\n <span class=\"ph cmd\">Open <span class=\"ph uicontrol\">Import Schedules</span> and run your data source.</span>\n <div class=\"itemgroup stepresult\">The system creates a new transform map based on the selected settings and create CIs generated from your payload.</div>\n </li></ol></section>\n </div>\n <nav role=\"navigation\"></nav><nav role=\"navigation\" class=\"tasksNavigation\"></nav><nav role=\"navigation\" class=\"related-links\"><div class=\"col-md-4\"><dt>Related tasks</dt><dd><ul><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/task/deploy-a-new-service-graph-connector-with-duplicated-etl.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/deploy-a-new-service-graph-connector-with-duplicated-etl.html\" class=\"link\" title=\"Associate a new Service Graph Connector (SGC) with an existing ETL.\">Deploy a new service graph connector with existing ETL</a></li></ul></dd></div></nav>\n</article></main></body></article>",
"topic_language": "enus",
"views": 0,
"your_rating": null
} | # Update the data source of the connector
Link the duplicated ETL to a valid data source for your specific connector.
## Before you begin
Role required: admin
## About this task
The following screenshot can help you to replace the default source with your connector's data source.
## Procedure
1. Navigate to All > IntegrationHub ETL.
2. In Specify Basic Details, replace the default data source with your connector’s data source.
3. Select Save.
4. Open Import Schedules and run your data source.
The system creates a new transform map based on the selected settings and create CIs generated from your payload.
| ---
title: Update the data source of the connector
description: Link the duplicated ETL to a valid data source for your specific connector.
keywords: []
breadcrumbs:
- Telecommunications Service Operations Management
- Configuring Telecommunications Service Operations Management
- Set up Telecom Visibility
- Configuring the Telecom Discovery Builder framework ETL in a connector
---
# Update the data source of the connector
Link the duplicated ETL to a valid data source for your specific connector.
## Before you begin
Role required: admin
## About this task
The following screenshot can help you to replace the default source with your connector's data source.
## Procedure
1. Navigate to All > IntegrationHub ETL.
2. In Specify Basic Details, replace the default data source with your connector’s data source.
3. Select Save.
4. Open Import Schedules and run your data source.
The system creates a new transform map based on the selected settings and create CIs generated from your payload.
|
https://www.servicenow.com/docs/en-US/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/use-attribute-value-discrepancy-in-cmdb-360.html | https://servicenow-be-prod.servicenow.com/api/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/use-attribute-value-discrepancy-in-cmdb-360.html | 2025-08-02 | daily | 0.5 | 268.xml | en-US | zurich-telecom-service-ops | product/tmt-telecom-service-operations-mgt/task/use-attribute-value-discrepancy-in-cmdb-360.html | zurich | 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. | [] | [
"Telecommunications Service Operations Management",
"Using Telecommunications Service Operations Management"
] | <article class="hascomments" data-page="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/use-attribute-value-discrepancy-in-cmdb-360.html" id="bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/use-attribute-value-discrepancy-in-cmdb-360.html"><body id="use-attribute-value-discrepancy-in-cmdb-360"><main role="main"><article role="article" class="dita" id="use-attribute-value-discrepancy-in-cmdb-360" aria-labelledby="title_use-attribute-value-discrepancy-in-cmdb-360">
<h1 class="title topictitle1" id="title_use-attribute-value-discrepancy-in-cmdb-360">Generate reports for attribute value discrepancies</h1>
<div class="body taskbody"><p class="shortdesc">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.</p>
<section class="section prereq" id="use-attribute-value-discrepancy-in-cmdb-360__task-prereq"><div class="tasklabel"><p class="sectiontitle tasklabel">Before you begin</p></div>
<p class="p">Role required: admin</p>
</section>
<section class="section context" id="use-attribute-value-discrepancy-in-cmdb-360__context_wfv_dqn_zfc"><div class="tasklabel"><p class="sectiontitle tasklabel">About this task</p></div>
<p class="p">Attribute value discrepancy reports help identify conflicting data from multiple sources updating the same configuration item (CI). This enables better data quality and integrity across your CMDB.</p>
</section>
<section><div class="tasklabel"><p class="sectiontitle tasklabel">Procedure</p></div><ol class="ol steps"><li class="li step">
<span class="ph cmd">Navigate to <span class="ph menucascade"><span class="ph uicontrol">All</span><abbr> > </abbr><span class="ph uicontrol">CMDB Workspace</span><abbr> > </abbr><span class="ph uicontrol">CMDB 360</span></span>.</span>
</li><li class="li step">
<span class="ph cmd">Select <span class="ph uicontrol">Create Query</span>.</span>
</li><li class="li step">
<span class="ph cmd">In the query type window, select <span class="ph uicontrol">Compare attribute values</span>.</span>
</li><li class="li step">
<span class="ph cmd">Define the query parameters:</span>
<ol type="a" class="ol substeps" id="use-attribute-value-discrepancy-in-cmdb-360__substeps_ky3_dpn_zfc">
<li class="li substep">
<span class="ph cmd">Select <span class="ph uicontrol">CI Class</span> you want to analyze (for example, cmdb_ci_computer).</span>
</li>
<li class="li substep">
<span class="ph cmd">Apply filters to narrow the scope (for example, Discovery source contains "TSOM").</span>
</li>
<li class="li substep">
<span class="ph cmd">Select attributes to compare values across different discovery sources.</span>
</li>
<li class="li substep">
<span class="ph cmd">Choose the sources to compare (for example, Discovery, SCCM).</span>
</li>
<li class="li substep">(Optional)
<span class="ph cmd">Select <span class="ph uicontrol">Compare to CMDB</span> to compare discovery source data to the current CMDB baseline.</span>
</li>
<li class="li substep">
<span class="ph cmd">Click <span class="ph uicontrol">Save</span>, provide a name for the query, and then click <span class="ph uicontrol">Run</span> to generate the results.</span>
</li>
</ol>
</li><li class="li step">(Optional)
<span class="ph cmd">Click <span class="ph uicontrol">Schedule</span> to set up the query to run at defined intervals.</span>
</li></ol></section>
<section class="section result" id="use-attribute-value-discrepancy-in-cmdb-360__result_fb4_3bt_zfc"><div class="tasklabel"><p class="sectiontitle tasklabel">Result</p></div>
<p class="p">The report displays a comparison of attribute values across sources:</p>
<ul class="ul" id="use-attribute-value-discrepancy-in-cmdb-360__ul_g2x_bwb_1gc">
<li class="li">Source 1: Current CMDB record.</li>
<li class="li">Source 1 Value: Value updated by the most recent discovery source.</li>
<li class="li">Source 2: Previous discovery source.</li>
<li class="li">Source 2 Value: Value provided by the earlier discovery source.</li>
</ul>
<p class="p">Each discrepancy is listed as a separate record when a CI has been updated by multiple sources.</p>
</section>
</div>
<nav role="navigation"></nav><nav role="navigation" class="tasksNavigation"></nav><nav role="navigation" class="related-links"><div class="col-md-4"><dt>Related tasks</dt><dd><ul><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/task/configure-attribute-value-discrepancy-in-cmdb-360.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/configure-attribute-value-discrepancy-in-cmdb-360.html" class="link" title="Configure attribute comparison settings in CMDB 360 to detect data inconsistencies across multiple discovery sources.">Configure attribute value discrepancy in CMDB 360</a></li><li><a data-bundleid="zurich-telecom-service-ops" data-navpath="product/tmt-telecom-service-operations-mgt/task/control-ci-attribute-updates-using-reconciliation-rules.html" href="https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/control-ci-attribute-updates-using-reconciliation-rules.html" class="link" title="To prevent specific attributes of a Configuration Item (CI) from being overwritten by Discovery or other data sources, use Reconciliation Rules. These rules define which data source is trusted to update a particular attribute when multiple sources provide values.">Control CI attribute updates using Reconciliation rules</a></li></ul></dd></div></nav>
</article></main></body></article> | {
"attachments": {
"all_attachments": null,
"topic_attachments": []
},
"available_languages": [
"enus"
],
"breadcrumbs": [
{
"title": "Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html"
},
{
"title": "Using Telecommunications Service Operations Management",
"topic_id": "product/tmt-telecom-service-operations-mgt/concept/using-tsom.html"
}
],
"breadcrumbs_html": "<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops\">Zurich Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html\">Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<a href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/concept/using-tsom.html\">Using Telecommunications Service Operations Management</a>\n<span><i class=\"fa fa-angle-right\"></i>\n</span>\n<span class=\"active\">Generate reports for attribute value discrepancies</span>",
"bundle_id": "zurich-telecom-service-ops",
"bundle_key": 2733,
"bundle_landing_page": "product/tmt-telecom-service-operations-mgt/concept/telecommunications-service-operations-management.html",
"bundle_subtitle": null,
"bundle_title": "Zurich Telecommunications Service Operations Management",
"canonical_link": null,
"dates": {
"Added on": "2025-08-02T00:48:08.794016Z",
"Created on": "2025-07-15T00:00:00Z",
"Initial upload": "2025-07-30T22:24:33.519043Z",
"Updated on": "2025-07-31T00:00:00Z"
},
"dislike_url": "https://servicenow-be-prod.servicenow.com/dislike/55686982",
"dislikes": 0,
"es_archived_content": false,
"is_in_fav": false,
"is_liked": null,
"is_watched": false,
"keywords": [
" zurich zurich"
],
"labels": [
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "zurich",
"navtitle": "Zurich",
"outputclasses": [],
"subjectHeadId": "versions",
"subjectheadNavtitle": "Versions",
"visibility": "show-facet"
},
{
"aliases": [],
"hidden": false,
"isSubjectHead": false,
"key": "tsom",
"navtitle": "Telecommunications Service Operations Management",
"outputclasses": [],
"subjectHeadId": "products",
"subjectheadNavtitle": "Products",
"visibility": "show-facet"
}
],
"labels_text": "Versions > Zurich; Products > CRM and Industry Products > Telecommunications Media and Technology Assurance > Telecommunications Service Operations Management",
"like_url": "https://servicenow-be-prod.servicenow.com/like/55686982",
"likes": 0,
"metadata": {
"AI Search": null,
"AI Search Assist": null,
"Application Insights": null,
"Capabilities": null,
"Code Signing": null,
"Contextual Search": null,
"DC.contributor": null,
"DC.coverage": null,
"DC.creator": "ServiceNow",
"DC.date.created": "2025-07-15T19:25:52+05:30",
"DC.date.modified": "2025-07-31",
"DC.format": "HTML5",
"DC.identifier": "use-attribute-value-discrepancy-in-cmdb-360",
"DC.language": null,
"DC.relation": "../../../product/tmt-telecom-service-operations-mgt/concept/using-tsom.html",
"DC.rights.owner": "(C) Copyright 2025",
"DC.subject": null,
"DC.type": "task",
"Data Discovery": null,
"Data Policy": null,
"Data Privacy": null,
"Discovery": null,
"External Content for AI Search": null,
"Field Administration": null,
"Field Normalization": null,
"Key Management Framework": null,
"Localization Framework": null,
"Now Platform": null,
"PlatSec": null,
"Platform": null,
"Platform Administration": null,
"Platform Performance": null,
"Platform Privacy": null,
"Proactive Triggers": null,
"Process Optimization": null,
"RN doc editing record number": null,
"Search Administration": null,
"Secrets Management": null,
"ServiceNow AI Platform": null,
"State Model": null,
"Subscription Management": null,
"Task Communications Management": null,
"Timeline Visualizations": null,
"User Administration": null,
"User Experience Analytics": null,
"Zing": null,
"ai-now-assist": null,
"app-name": null,
"app_route": null,
"azureapimanagemen": null,
"change-completed": null,
"change-item": null,
"change-request-id": null,
"change-request-reference": null,
"com.glide.embedded_help.category": null,
"component": null,
"copyright": "(C) Copyright 2025",
"crossroads": null,
"data": null,
"description": "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.",
"dominant_bundle": null,
"erp-canvas-video": null,
"fsm-mobile": null,
"fsm-route": null,
"fsm-sched-opt": null,
"fsm-wrk-order": null,
"genai-round-7": null,
"generator": "DITA-OT",
"glossPartOfSpeech": null,
"glossStatus": null,
"guided setup": null,
"guided tours": null,
"keywords": null,
"min-toc": null,
"mini": null,
"mini-to truec": null,
"mini-toc": null,
"mini_toc": null,
"minitoc": null,
"modification": null,
"now-assist-app-gen-video": null,
"order": null,
"page-type": null,
"page-type ": null,
"prodname": null,
"product": null,
"product_name": null,
"release": null,
"resourceID": null,
"roles": null,
"route_page": null,
"route_params_listId": null,
"route_params_table": null,
"route_params_type": null,
"route_type": null,
"setconfigurationproperties": null,
"topic": null,
"translation-type": "source",
"version": null,
"workflow": "Customer and Industry",
"workplace-srvc-delvry-ditamap": null
},
"page_id": "product/tmt-telecom-service-operations-mgt/task/use-attribute-value-discrepancy-in-cmdb-360.html",
"page_key": 55686982,
"preprocessed_PDF": "https://downloads.docs.servicenow.com/pdf/enus/servicenow-zurich-telecom-service-ops-enus.pdf",
"rating": null,
"read_time_data": {
"char_count": 1504,
"img_count": 0,
"read_time": 1,
"video_links": [
""
],
"word_count": 234
},
"related_links": [
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "Configure attribute comparison settings in CMDB 360 to detect data inconsistencies across multiple discovery sources.",
"title": "Configure attribute value discrepancy in CMDB 360",
"topic": "/product/tmt-telecom-service-operations-mgt/task/configure-attribute-value-discrepancy-in-cmdb-360.html",
"type": "task",
"url": null
},
{
"bundle": "zurich-telecom-service-ops",
"role": null,
"scope": "internal",
"shortDes": "To prevent specific attributes of a Configuration Item (CI) from being overwritten by Discovery or other data sources, use Reconciliation Rules. These rules define which data source is trusted to update a particular attribute when multiple sources provide values.",
"title": "Control CI attribute updates using Reconciliation rules",
"topic": "/product/tmt-telecom-service-operations-mgt/task/control-ci-attribute-updates-using-reconciliation-rules.html",
"type": "task",
"url": null
}
],
"search_title": null,
"title": "Generate reports for attribute value discrepancies",
"topic_cluster": {
"clustered_by": {
"enabled": true,
"primary_key": "versions",
"primary_sort": "top-down",
"type": "subjecthead"
},
"clustered_labels": [
"versions"
],
"clustered_topics": [],
"clustering_title": "Zurich"
},
"topic_html": "<article class=\"hascomments\" data-page=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/use-attribute-value-discrepancy-in-cmdb-360.html\" id=\"bundle:zurich-telecom-service-ops/enus/product/tmt-telecom-service-operations-mgt/task/use-attribute-value-discrepancy-in-cmdb-360.html\"><body id=\"use-attribute-value-discrepancy-in-cmdb-360\"><main role=\"main\"><article role=\"article\" class=\"dita\" id=\"use-attribute-value-discrepancy-in-cmdb-360\" aria-labelledby=\"title_use-attribute-value-discrepancy-in-cmdb-360\">\n <h1 class=\"title topictitle1\" id=\"title_use-attribute-value-discrepancy-in-cmdb-360\">Generate reports for attribute value discrepancies</h1>\n \n \n <div class=\"body taskbody\"><p class=\"shortdesc\">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.</p>\n <section class=\"section prereq\" id=\"use-attribute-value-discrepancy-in-cmdb-360__task-prereq\"><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">Before you begin</p></div>\n <p class=\"p\">Role required: admin</p>\n </section>\n <section class=\"section context\" id=\"use-attribute-value-discrepancy-in-cmdb-360__context_wfv_dqn_zfc\"><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">About this task</p></div>\n <p class=\"p\">Attribute value discrepancy reports help identify conflicting data from multiple sources updating the same configuration item (CI). This enables better data quality and integrity across your CMDB.</p>\n </section>\n <section><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">Procedure</p></div><ol class=\"ol steps\"><li class=\"li step\">\n <span class=\"ph cmd\">Navigate to <span class=\"ph menucascade\"><span class=\"ph uicontrol\">All</span><abbr> > </abbr><span class=\"ph uicontrol\">CMDB Workspace</span><abbr> > </abbr><span class=\"ph uicontrol\">CMDB 360</span></span>.</span>\n </li><li class=\"li step\">\n <span class=\"ph cmd\">Select <span class=\"ph uicontrol\">Create Query</span>.</span>\n </li><li class=\"li step\">\n <span class=\"ph cmd\">In the query type window, select <span class=\"ph uicontrol\">Compare attribute values</span>.</span>\n </li><li class=\"li step\">\n <span class=\"ph cmd\">Define the query parameters:</span>\n <ol type=\"a\" class=\"ol substeps\" id=\"use-attribute-value-discrepancy-in-cmdb-360__substeps_ky3_dpn_zfc\">\n <li class=\"li substep\">\n <span class=\"ph cmd\">Select <span class=\"ph uicontrol\">CI Class</span> you want to analyze (for example, cmdb_ci_computer).</span>\n </li>\n <li class=\"li substep\">\n <span class=\"ph cmd\">Apply filters to narrow the scope (for example, Discovery source contains "TSOM").</span>\n </li>\n <li class=\"li substep\">\n <span class=\"ph cmd\">Select attributes to compare values across different discovery sources.</span>\n </li>\n <li class=\"li substep\">\n <span class=\"ph cmd\">Choose the sources to compare (for example, Discovery, SCCM).</span>\n </li>\n <li class=\"li substep\">(Optional) \n <span class=\"ph cmd\">Select <span class=\"ph uicontrol\">Compare to CMDB</span> to compare discovery source data to the current CMDB baseline.</span>\n </li>\n <li class=\"li substep\">\n <span class=\"ph cmd\">Click <span class=\"ph uicontrol\">Save</span>, provide a name for the query, and then click <span class=\"ph uicontrol\">Run</span> to generate the results.</span>\n </li>\n </ol>\n </li><li class=\"li step\">(Optional) \n <span class=\"ph cmd\">Click <span class=\"ph uicontrol\">Schedule</span> to set up the query to run at defined intervals.</span>\n </li></ol></section>\n <section class=\"section result\" id=\"use-attribute-value-discrepancy-in-cmdb-360__result_fb4_3bt_zfc\"><div class=\"tasklabel\"><p class=\"sectiontitle tasklabel\">Result</p></div>\n <p class=\"p\">The report displays a comparison of attribute values across sources:</p>\n <ul class=\"ul\" id=\"use-attribute-value-discrepancy-in-cmdb-360__ul_g2x_bwb_1gc\">\n <li class=\"li\">Source 1: Current CMDB record.</li>\n <li class=\"li\">Source 1 Value: Value updated by the most recent discovery source.</li>\n <li class=\"li\">Source 2: Previous discovery source.</li>\n <li class=\"li\">Source 2 Value: Value provided by the earlier discovery source.</li>\n </ul>\n <p class=\"p\">Each discrepancy is listed as a separate record when a CI has been updated by multiple sources.</p>\n </section>\n </div>\n <nav role=\"navigation\"></nav><nav role=\"navigation\" class=\"tasksNavigation\"></nav><nav role=\"navigation\" class=\"related-links\"><div class=\"col-md-4\"><dt>Related tasks</dt><dd><ul><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/task/configure-attribute-value-discrepancy-in-cmdb-360.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/configure-attribute-value-discrepancy-in-cmdb-360.html\" class=\"link\" title=\"Configure attribute comparison settings in CMDB 360 to detect data inconsistencies across multiple discovery sources.\">Configure attribute value discrepancy in CMDB 360</a></li><li><a data-bundleid=\"zurich-telecom-service-ops\" data-navpath=\"product/tmt-telecom-service-operations-mgt/task/control-ci-attribute-updates-using-reconciliation-rules.html\" href=\"https://servicenow-be-prod.servicenow.com/bundle/zurich-telecom-service-ops/page/product/tmt-telecom-service-operations-mgt/task/control-ci-attribute-updates-using-reconciliation-rules.html\" class=\"link\" title=\"To prevent specific attributes of a Configuration Item (CI) from being overwritten by Discovery or other data sources, use Reconciliation Rules. These rules define which data source is trusted to update a particular attribute when multiple sources provide values.\">Control CI attribute updates using Reconciliation rules</a></li></ul></dd></div></nav>\n</article></main></body></article>",
"topic_language": "enus",
"views": 0,
"your_rating": null
} | # 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.
## Before you begin
Role required: admin
## About this task
Attribute value discrepancy reports help identify conflicting data from multiple sources updating the same configuration item (CI). This enables better data quality and integrity across your CMDB.
## Procedure
1. Navigate to All > CMDB Workspace > CMDB 360.
2. Select Create Query.
3. In the query type window, select Compare attribute values.
4. Define the query parameters:
1. Select CI Class you want to analyze (for example, cmdb\_ci\_computer).
2. Apply filters to narrow the scope (for example, Discovery source contains "TSOM").
3. Select attributes to compare values across different discovery sources.
4. Choose the sources to compare (for example, Discovery, SCCM).
5. (Optional)
Select Compare to CMDB to compare discovery source data to the current CMDB baseline.
6. Click Save, provide a name for the query, and then click Run to generate the results.
5. (Optional)
Click Schedule to set up the query to run at defined intervals.
### Result
The report displays a comparison of attribute values across sources:
* Source 1: Current CMDB record.
* Source 1 Value: Value updated by the most recent discovery source.
* Source 2: Previous discovery source.
* Source 2 Value: Value provided by the earlier discovery source.
Each discrepancy is listed as a separate record when a CI has been updated by multiple sources.
| ---
title: Generate reports for attribute value discrepancies
description: 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.
keywords: []
breadcrumbs:
- Telecommunications Service Operations Management
- Using Telecommunications Service Operations Management
---
# 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.
## Before you begin
Role required: admin
## About this task
Attribute value discrepancy reports help identify conflicting data from multiple sources updating the same configuration item (CI). This enables better data quality and integrity across your CMDB.
## Procedure
1. Navigate to All > CMDB Workspace > CMDB 360.
2. Select Create Query.
3. In the query type window, select Compare attribute values.
4. Define the query parameters:
1. Select CI Class you want to analyze (for example, cmdb\_ci\_computer).
2. Apply filters to narrow the scope (for example, Discovery source contains "TSOM").
3. Select attributes to compare values across different discovery sources.
4. Choose the sources to compare (for example, Discovery, SCCM).
5. (Optional)
Select Compare to CMDB to compare discovery source data to the current CMDB baseline.
6. Click Save, provide a name for the query, and then click Run to generate the results.
5. (Optional)
Click Schedule to set up the query to run at defined intervals.
### Result
The report displays a comparison of attribute values across sources:
* Source 1: Current CMDB record.
* Source 1 Value: Value updated by the most recent discovery source.
* Source 2: Previous discovery source.
* Source 2 Value: Value provided by the earlier discovery source.
Each discrepancy is listed as a separate record when a CI has been updated by multiple sources.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.