Revision, operationalization, and decommission of a Configuration Item

  • Release version: Washingtondc
  • Updated February 1, 2024
  • 2 minutes to read
  • Summarize
    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

    Configuration Item (CI) revisions allow you to safely update network attributes and connection elements of operational CIs, specifically for logical and physical connections. This process ensures that all relevant configuration items can be revised as needed using the Telecommunications Network Inventory application.

    Show full answer Show less

    Key Features

    • CI Revision: Modify network-configured attributes and connection elements for logical and physical connection CIs by utilizing the revise CI feature.
    • Operationalization: After a revision request is created, the selected CI is cloned, including its related tables (attributes, connection elements, relations), allowing for changes on the cloned record.
    • Automatic Decommissioning: Upon successful operationalization, the cloned CI is automatically decommissioned, ensuring a streamlined process.

    Key Outcomes

    Using CI revisions allows for safe updates without disrupting network operations. For example, if you need to add an ENET for increased LAG capacity or update a router's IP address, creating a CI revision will enable you to clone the existing configuration, implement changes, and merge them back into the original CI seamlessly. This process minimizes risks associated with direct changes to active configurations.

    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.

    Overview

    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

    Using the change, after you create a revision request for a CI record, the selected CI is cloned. During this process, it clones the Configuration Item and all its related tables such as, its attributes, connection elements, and relations. To customize the cloning process or the related tables, see Customize the CI cloning process.

    After successful cloning, it enables you to perform changes on the cloned Configuration Item record, as required. Using the operationalization process, you can merge and finalize the changes. Further, all the changes are applied to the original Configuration Item and the cloned Configuration Item is decommissioned automatically. However, you can't create a revision of an active revised Configuration Item, you can update the cloned Configuration Item as required at any time. To operationalize and decommission a CI record, see Revise a configuration item and Decommission an inventory record respectively.

    Use case

    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, Operationalize a configuration item. Here, the cloned CI is decommissioned automatically. To learn more, see Decommission an inventory record.

    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 and Operationalize a configuration item.