| \n\nChange model\n\n | \n\nDescription\n\n |
|---|---|
| \n\nAdd cable\n\n | \n\nChange model to create a change task for adding a card. To learn more, see the add card form in [Change request and change task forms](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/telecom-network-inventory/telecommunications-network-inventory/change_request_forms.md).\n\n |
| \n\nAdd Card\n\n | \n\nChange model to create a change request for adding an interface card. To learn more, see the add card form in [Change request and change task forms](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/telecom-network-inventory/telecommunications-network-inventory/change_request_forms.md).\n\n |
| \n\nCreate inventory equipment\n\n | \n\nChange model to create a change request for creating inventory equipment. To learn more, see the create equipment form in [Change request and change task forms](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/telecom-network-inventory/telecommunications-network-inventory/change_request_forms.md).**Note:** To see the compute and create logical connection form, see [Compute and Create Logical Connection form](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/telecom-network-inventory/telecommunications-network-inventory/compute-and-create-logical-connection-form.md).\n\n |
| \n\nCreate logical connection\n\n | \n\nChange model to create a change request for creating a logical connection. To learn more, see the [Change request and change task forms](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/telecom-network-inventory/telecommunications-network-inventory/change_request_forms.md).**Note:**\n\n- To update or revise a logical connection CI, see [Revise a configuration item using design and assign](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/telecom-network-inventory/telecommunications-network-inventory/revise-a-configuration-item.md).\n- To modify logical connection endpoints, see [Modify logical connection endpoints model](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/telecom-network-inventory/telecommunications-network-inventory/create-a-change-request-by-using-modify-logical-connection-endpoints-model.md).\n\n |
| \n\nCreate physical connection\n\n | \n\nChange model to create a change request for creating a physical connection. To learn more, see [Change request and change task forms](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/telecom-network-inventory/telecommunications-network-inventory/change_request_forms.md).**Note:**\n\n- To update or revise a physical connection CI, see [Revise a configuration item using design and assign](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/telecom-network-inventory/telecommunications-network-inventory/revise-a-configuration-item.md).\n- To modify physical connection endpoints, see [Modify physical connection endpoints](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/telecom-network-inventory/telecommunications-network-inventory/create-a-change-request-by-using-modify-physical-connection.md).\n\n |
| \n\nCreate Rack/Cabinet\n\n | \n\nChange model to create a change request for creating and visualizing a rack or cabinet. To learn more, see [Change request and change task forms](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/telecom-network-inventory/telecommunications-network-inventory/change_request_forms.md).\n\n**Note:**\n\n1. For creating a rack or cabinet, ensure that the following exist:\n\n - A model in equipment holder model with **Model categories** as **Equipment Rack**.\n - A relationship in network model relationships with the **Relationship type** as **Rack to Slot**.\n - A template in the inventory template where the **inventory model** has a rack model.\nA rack is created based on the selected rack model in the template, and the rack slots are created based on the rack template.\n\n2. To add equipment to a rack, see [Create a change request from Network Inventory Workspace](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/telecom-network-inventory/telecommunications-network-inventory/create_a_change_request_in_tni.md).\n\n |
| \n\nAdd equipment to Rack/cabinet\n\n | \n\nChange model to add a new or existing equipment to a rack. To learn more, see [Change request and change task forms](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/telecom-network-inventory/telecommunications-network-inventory/change_request_forms.md).\n\n |
| \n\nRemove Equipment or Shelf from Rack/Cabinet\n\n | \n\nChange model to remove an equipment or a shelf from a rack or cabinet slot. To learn more, see [Change request and change task forms](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/telecom-network-inventory/telecommunications-network-inventory/change_request_forms.md).**Note:** Shelf cannot be removed if it is related to any equipment.\n\n |
| \n\nIP address allocation\n\n | \n\nChange model to create a change request for IP address allocation. To learn more, see the IP address allocation form in [Change request and change task forms](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/telecom-network-inventory/telecommunications-network-inventory/change_request_forms.md).\n\n |
| \n\nPhone number allocation\n\n | \n\nChange model to create a change request for a phone number allocation. To learn more, see the Manage phone number form in [Change request and change task forms](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/telecom-network-inventory/telecommunications-network-inventory/change_request_forms.md).\n\n |
| \n\nField\n\n | \n\nDescription\n\n |
|---|---|
| \n\nNumber\n\n | \n\nChange request number.\n\n |
| \n\nRequested by\n\n | \n\nUser who has requested the change. This field is available in the Change Requests list view so that you can see who requested a particular change.\n\n |
| \n\nCategory\n\n | \n\nCategory of this change request. Select **Other** if your category isn’t in the list.\n\n |
| \n\nService\n\n | \n\nBusiness service that you want to make available for this change request.\n\n |
| \n\nService offering\n\n | \n\nService option that consists of one or more service commitments that uniquely define the level of service. You can select the different levels of performance and features for a service through service offerings. You must select a service to filter the available service offerings.\n\n |
| \n\nConfiguration item\n\n | \n\nConfiguration item \\(CI\\) that the change applies to.\n\n |
| \n\nPriority\n\n | \n\nPriority of this change request.\n\n |
| \n\nRisk\n\n | \n\nRisk level for the change.Select one of the following options:\n\n- **High**\n- **Moderate**\n- **Low**\n\n |
| \n\nImpact\n\n | \n\nMeasure of the effect of a change on the business processes.\n\n |
| \n\nShort description\n\n | \n\nSummary of the change.\n\n |
| \n\nDescription\n\n | \n\nDescription of the change in detail.\n\n |
| \n\nModel\n\n | \n\nChange model that is associated with the Telecommunications Network Inventory change request. After selecting the change model tile, the associated model appears in this field. You can also manually select one of the following options:\n\n - **Add Interface Card**\n\nChange model that is used to add an interface card in an equipment slot.\n\n- **Create Inventory Equipment**\n\nChange model that is used to add equipment when using an inventory template in a site or equipment holder.\n\n- **Create Logical Connection**\n\nChange model that is used to create a logical connection between two network interfaces.\n\n- **Create Physical Connection**\n\nChange model that is used to create a physical connection between two network interfaces.\n\n- **Emergency**\n\nChange model that is used for the Telecom Network Inventory emergency changes.\n\n- **GPON Broadband Service**\n\nChange model that is used to fulfill a Gigabyte Passive Optical Network \\(GPON\\) broadband order request.\n\n- **Normal**\n\nChange model that is used for the Telecommunications Network Inventory normal changes.\n\n\n **Note:** These change models are available in the **Changes** > **All** > **New** window.\n\n |
| \n\nState\n\n | \n\nCurrent state of this change request, New, or closed.\n\n |
| \n\nAssignment group\n\n | \n\nGroup working on the change request.\n\n |
| \n\nAssigned to\n\n | \n\nUser that the change is assigned to. If an assignment rule applies, the change is automatically assigned to the appropriate user or group.- New\n- Design In Progress\n- Design Review\n- Design Complete\n\n |
| \n\nField\n\n | \n\nDescription\n\n |
|---|---|
| \n\nClose code\n\n | \n\nClose code that best describes the reason you’re closing this change request. Select one of the following options:- **Successful**\n- **Unsuccessful with issues**\n- **Unsuccessful**\n\n |
| \n\nClose notes\n\n | \n\nAny additional notes that describe the outcome of closing this change request.\n\n |
| \n\nFields\n\n | \n\nDescription\n\n |
|---|---|
| \n\nNumber\n\n | \n\nChange task identification number.\n\n |
| \n\nChange request\n\n | \n\nChange request number under which this change task was created.\n\n |
| \n\nConfiguration item\n\n | \n\nConfiguration item \\(CI\\) that the change is applied to.\n\n |
| \n\nRequest type\n\n | \n\nRequest type. Depending on your selection, the record producer form under the task attributes gets updated. This field represents the type of change request. Select any one of the following:- **Revise CI**\n\nThis type of request definition enables you to select a CI that you want to revise and clones the selected CI details and related items. The **Configuration item** field is automatically updated with the cloned CI name having suffix as revised.\n\nAll the changes made to the CI are now applied to the cloned CI. Also, both original and duplicated CIs can be found under **Affected CIs** tab. To customize the cloning process, see [https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/telecom-network-inventory/telecommunications-network-inventory/clone-and-revise-a-ci.md](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/telecom-network-inventory/telecommunications-network-inventory/clone-and-revise-a-ci.md).\n\n- **Add cable**\n\nThis type of request definition enables you to create a cable record.\n\n- **Add Card**\n\nThis type of request definition enables you to select a site and equipment model when you add interface cards. To learn more about equipment instantiation, see [Design and assign]().\n\n- **Create equipment**\n\nThis type of request definition enables you to select a network site and an inventory template for equipment instantiation. If you want to place your equipment inside a rack, you can select an equipment holder.\n\n- **Create Physical Connection and Create Logical Connection**\n\nThese types of request definitions have similar sets of site and equipment selection fields for the physical or logical connections between your start \\(A\\) and end \\(Z\\) locations. You can only select those interfaces that are associated with the designated equipment model for the A-start and Z-end interfaces.\n\nFor the instantiation of physical or logical connections, you must select a physical connection model or a logical connection model, depending on the type of connection that you want to create between the two sites. For a logical connection, this internal code creates a CI record, and additional path elements.\n\n- **Logical connection - Path compute**\n\nThis type of request definition has a set of site and equipment fields for start and end locations.\n\nFor initiation of the path compute of the logical connection, you must select logical connection model. To learn more, see [Compute and Create Logical Connection form](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/telecom-network-inventory/telecommunications-network-inventory/compute-and-create-logical-connection-form.md).\n\n- **Modify members of a topology**\n\nThis type of request definition enables you to create a cable record. o learn more about modifying a network topology record, see [Add or remove a member to network topology record](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/telecom-network-inventory/telecommunications-network-inventory/modify-network-topology-record-design-assign.md).\n\n- **IP Address Allocation**\n\nThis type of request definition enables you to instantiate an IP address allocation and assign new services to the IP addresses. To learn more, see IP address allocation form in [Change request and change task forms]().\n\n- **Phone Number Allocation**\n\nThis type of request definition enables you to instantiate a phone number allocation. You can allocate, de-allocate, and create numbers that are provided externally. To learn more, see the Manage phone number form in [Change request and change task forms]().\n\n\n |
| \n\nShort description\n\n | \n\nShort description for this order task.\n\n |
| \n\nDescription\n\n | \n\nDescription of this order task.\n\n |
| \n\nState\n\n | \n\nState of this change task. Select one of the following options:- **Pending**\n\nTask is waiting for an action from the user.\n\n- **Open**\n\nNo action is taken on this task yet.\n\n- **In Progress**\n\nTask processing is in progress.\n\n- **Closed**\n\nChange task is complete.\n\n- **Canceled**\n\nChange task has been canceled.\n\n\n |
| \n\nAssignment group\n\n | \n\nName of the group that is responsible for this task. Select the search icon \\(\\[Omitted image \"search.png\"\\] Alt text: Search icon.\\) to select a group from the list.\n\n |
| \n\nAssigned to\n\n | \n\nDepending on the selected group, the users who are assigned to the list are shown. Select the search icon \\(\\[Omitted image \"search.png\"\\] Alt text: Search icon.\\) to see the list of users.\n\n |
| \n\nWork notes\n\n | \n\nFree-form work order note text.\n\n |
| \n\nUpdate\n\n | \n\nOption to save changes that you made to the order task.\n\n |
| \n\nClose Task\n\n | \n\nOption to change the state of the order task to **Closed**.\n\n |
| \n\nDelete\n\n | \n\nOption to delete this order task.\n\n |
| \n\nFields\n\n | \n\nDescription\n\n |
|---|---|
| \n\nInventory template\n\n | \n\nName of the inventory template for the equipment model. The instantiation process uses it to generate a network asset instance in the designated network site.**Note:**\n\n- Depending on the selected inventory template, a list of the optional templates appears at the bottom of the form.\n- When you select an optional template, the current template values are overwritten.\n- This field is applicable only for Create inventory equipment.\n\n |
| \n\nEquipment holder\n\n | \n\nName of the telco equipment holder. Select a rack or a cabinet where the equipment can be installed.**Note:**\n\n- The **Telco equipment holder** field lists all racks and cabinets.\n- This field is applicable only for Create inventory equipment.\n\n |
| \n\nNetwork site\n\n | \n\nName of the network site in which the process is instantiating the equipment.\n\n |
| \n\nRack/Cabinet template\n\n | \n\nTemplate name of the rack template where you want to add all the slots to.\n\n**Note:**\n\n- Based on the selected **Rack template**, **Stockroom location**, and **Asset** the slots, network sites, and related network sites are added.\n- This field is applicable only for Create rack.\n\n |
| \n\nStockroom Location\n\n | \n\nName of the stockroom location where the asset is located.\n\n To learn more, see [Telecommunications Network Inventory integration with Hardware Asset Management](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/telecom-network-inventory/telecommunications-network-inventory/integration-with-hardware-asset-management.md).\n\n |
| \n\nAsset\n\n | \n\nName of the asset that is associated with this record.\n\n To learn more, see [Telecommunications Network Inventory integration with Hardware Asset Management](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/telecom-network-inventory/telecommunications-network-inventory/integration-with-hardware-asset-management.md).\n\n |
| \n\nField\n\n | \n\nDescription\n\n |
|---|---|
| \n\nOperation Type\n\n | \n\nType of operation. Select one of the following options:- **Create IP network subnet**: Creates a network subnet with a CIDR value.\n\n**Note:** For the IP network subnet creation, the Create IP Subnetwork flow action is initiated. To learn more, see [Create IP subnetwork function](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/telecom-network-inventory/telecommunications-network-inventory/create_ip_subnetwork.md).\n\n- **Convert CIDR to IP addresses**: Converts a single or multiple CIDRs to IP addresses and stores them in an IP address allocation.\n\n**Note:** For the CIDR-to-IP address conversion, the CIDR-to-IP range flow action is initiated. To learn more, see [CIDR to IP range function](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/telecom-network-inventory/telecommunications-network-inventory/cidr_to_ip_range.md).\n\n\n |
| \n\nName\n\n | \n\nName for this IP allocation.\n\n |
| \n\nIP pool\n\n | \n\nParent pool of this IP address allocation.\n\n |
| \n\nIP network subnet CIDR\n\n | \n\nCIDR value.\n\n |
| \n\nManaged Network\n\n | \n\nIP address or allocation that you can select and assign a network to.\n\n |
| \n\nOwned by configuration item\n\n | \n\nConfiguration item that owns this allocation.\n\n |
| \n\nIP network subnet\n\n | \n\nNetwork subnet that you searched for and selected to convert its CIDR-to-IP addresses. **Note:** This field is used only for converting the CIDR-to-IP address.\n\n |
| \n\nFields\n\n | \n\nDescription\n\n |
|---|---|
| \n\nAction\n\n | \n\nAction that you can select:- **Allocate**: Allocates the numbers from a block\n- **De-allocate**: De-allocates the numbers. The status of the numbers is changed to Quarantine.\n\n**Note:** When you select this action, you must select an allocation or the selected numbers that you want to deallocate. This action results in changing the status to Quarantine.\n\n- **Ported-in**: Includes the numbers that are moved from another operator. The numbers are stored in a telephone number allocation of telephone numbers only.\n\n**Note:** Multiple allocations get created if the numbers aren’t in a series of numbers. Also, by default, the numbers are changed to the assigned or the ported-in status.\n\n- **Create**: Creates the phone number allocation for the numbers that are assigned to an external telephone block. You’re assigning the numbers to a network inventory-based phone number allocation.\n\n |
| \n\nService\n\n | \n\nService for these numbers. The selected service gets assigned to the numbers.**Note:** Ensure that you’ve created a service for this phone number. To learn more, see [Manage your network functions](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/telecom-network-inventory/telecommunications-network-inventory/services.md).\n\n |
| \n\nQuantity\n\n | \n\nTotal number of required phone numbers.**Note:** This field disappears for a deallocated action.\n\n |
| \n\nPhone number allocation\n\n | \n\nAvailable number allocations that are based on the provided information that you enter. You can select a phone number allocation for your line number.\n\n |
| \n\nLine number\n\n | \n\nEnter your required line number in xxxx-xxxx or xxx-xxx or xxx, xxx-xxx format.**Note:** Multiple telephone number allocations are created if the line number isn’t in a series of numbers. Also, the status of these numbers gets updated to either assigned or ported-in and the availability is No.\n\n |