--- sourceDocument: Australia Telecommunications Network Inventory sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/telecom-network-inventory Release : - australia ft:locale : - en-US ft:publication_title : - Australia Telecommunications Network Inventory ft:clusterId : - telninv bundleId : - telninv workflow : - Customer and Industry --- # Revision, operationalization, and decommission # Revision, operationalization, and decommission of a Configuration Item {#ariaid-title1} Release version: Australia Updated March 12, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Revision, operationalization, and decommission of a Configuration Item This process in ServiceNow's Telecommunications Network Inventory application allows you to safely and efficiently update network attributes, connection elements, and relations of Configuration Items (CIs). It specifically applies to logical and physical connection CIs, enabling controlled revision, operationalization, and decommissioning of these items without disrupting network operations. Show full answer Show less ## Key Features * **CI Revision:** Enables modification of network-configured attributes and connection elements by cloning the selected CI along with its related data (attributes, connections, relations). * **Customizable Cloning:** Allows specification of which related tables to include during cloning, providing flexibility in the revision process. * **Operationalization:** Merges and finalizes changes from the cloned CI back into the original CI, ensuring updates are applied efficiently and accurately. * **Decommissioning:** Automatically decommissions the cloned CI post-operationalization to maintain inventory integrity and workflow efficiency. ## Practical Application For example, to safely expand a logical connection's LAG capacity by adding another ENET, you use the revise CI process to clone the LAG and its connections, make the addition in the cloned CI, and then operationalize the changes back into the original CI without network disruption. Similarly, updating critical information like a router's IP address follows the same revision and operationalization steps to ensure safe, disruption-free updates in complex network environments. ## Benefits for ServiceNow Customers * Enables safe, controlled updates to network configuration items without impacting live network operations. * Ensures data integrity by cloning and revising CIs before finalizing changes. * Streamlines update workflows with automatic decommissioning of interim cloned CIs. * Supports complex network changes with minimal risk through clear, repeatable processes. Revision of Configuration Item (CI) enables you to update the network attributes of a Configuration Item, such as attributes, connection elements, and relations using the Telecommunications Network Inventory application. You can make a safe and efficient update to your network infrastructure by using the CI revision. ## CI revision overview {#revision-of-a-confiuguration-item__section_lxz_3vy_bzb} CI revisions enable you to modify network-configured attributes and connection elements of an operational Configuration Item. The CI revision is applicable only to logical connection and physical connection CIs. So, you can update all configuration items of a connection, as required with the help of revise CI and its subflows. CI revisions enable you to modify network-configured attributes and connection elements of an operational Configuration Item. The CI revision is applicable only to logical connection and physical connection CIs. So, after a logical connection or a physical connection configuration Item is created, you can update it as required with the help of revise CI and its subflows. ## Operationalization and decommission flow {#revision-of-a-confiuguration-item__section_jhv_vgz_lzb} The following process guides you through the flow for a Configuration Item (CI) record after a request is created. 1. Initiate Revision Request: Once you create a revision request, the selected CI is automatically cloned. This cloned CI includes all its related tables such as, attributes, connection elements, and relations. 2. Customize Cloning Process: You can customize the cloning process and specify which related tables are included. To learn more, see ../task/clone-and-revise-a-ci.html. 3. Modify cloned CI: After successful cloning, you can perform changes on the cloned Configuration Item record, as required. 4. Finalize and apply changes: Using operationalization process merge and finalize the changes. This process integrates the revisions into the original CI record. To learn more, see [Revise a configuration item using design and assign](https://servicenow-prod.fluidtopics.net/XCiEjcg32JclHrxWSGKK7g "Revise a CI (Configuration Item) of the connection to update a CI in the Telecommunications Network Inventory application."). 5. Decommission: After operationalization, the cloned CI record is automatically decommissioned, ensuring an efficient workflow. To learn more, see [Decommission an inventory record](https://servicenow-prod.fluidtopics.net/NdjIDC0FzZ7B1aZwgemWvg "Decommission an inventory record that you want to remove from Telecommunications Network Inventory."). {#revision-of-a-confiuguration-item__ol_okg_4k1_ybc}. ## Use case {#revision-of-a-confiuguration-item__section_ukc_xzc_2zb} Let's say, for a logical connection having two ENETs, you want to add another ENET to increase the LAG capacity. So, in this scenario, for a safe LAG update, use the CI revision. With the help of revise CI, the LAG and all of its connections are cloned. Then, in the cloned LAG Configuration Item, add the desired ENET member and merge it back into the original CI with the help of operationalize CI. After successful operationalization, all three ENETs are added to the original CI without disrupting the network. To learn more, see [Revise a configuration item using design and assign](https://servicenow-prod.fluidtopics.net/XCiEjcg32JclHrxWSGKK7g "Revise a CI (Configuration Item) of the connection to update a CI in the Telecommunications Network Inventory application."), [Operationalize a configuration item](https://servicenow-prod.fluidtopics.net/icCEqr2EF8tNbojINwto0g "Operationalize a Configuration Item so that you can finalize the changes and apply them on the original CI."). Here, the cloned CI is decommissioned automatically. To learn more, see [Decommission an inventory record](https://servicenow-prod.fluidtopics.net/NdjIDC0FzZ7B1aZwgemWvg "Decommission an inventory record that you want to remove from Telecommunications Network Inventory."). Let's say, you must update the IP address of a router in your network. This router is part of a complex network, and you aren't sure how changing the IP address affects the rest of the network. So, in this scenario, for a safe update of the router's IP address, use the CI revision. With the help of revise CI, you firstly, duplicate the router CI and all of its related data. Then, you change the IP address of the duplicated router and merge it back into the original CI with the help of operationalize CI. As a result, the changes are applied to the original router without disrupting the network. To learn more, see [Revise a configuration item using design and assign](https://servicenow-prod.fluidtopics.net/XCiEjcg32JclHrxWSGKK7g "Revise a CI (Configuration Item) of the connection to update a CI in the Telecommunications Network Inventory application.") and [Operationalize a configuration item](https://servicenow-prod.fluidtopics.net/icCEqr2EF8tNbojINwto0g "Operationalize a Configuration Item so that you can finalize the changes and apply them on the original CI.").