---
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


---

# Create logical connection record

# Create
a logical connection record using the Design and Assign function {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 6 minutes to read  
Use the Design and Assign function to create a logical connection in the Telecommunications Network Inventory application. By creating a logical connection, you can fulfill the design request for a network service.

## Before you begin

Define the inventory records, models, model relationships, templates, and template relationships for your design criteria.

Role required: sn_ni_core.inventory_agent, sn_ni_core.network_planning_manager

## About this task

The Design and Assign home page lists the change requests that are in the Design in progress state. You can either select a change request from the list or create a change request to design a logical connection depending on
your requirement. Completion of each activity in the playbook for the Design and Assign function creates a change task for the next activity.

After you complete each activity, the network diagram updates and displays the data. You can review the network diagram for any incompleteness and update the activities accordingly.

## Procedure

1. Navigate to WorkspacesNetwork Inventory Workspace.
2. Select the design and assign icon (![Design and Assign Icon]()).  
   The Design and Assign home page is displayed.
3. Select NewCreate Logical Connection.  
   A change request is created with Design in progress and the Design and Assign window is displayed.
4. On the Setup request details card, fill in the fields.  
   {#create-logical-connection-record-design-assign-playbook__table_zxs_tmt_gtb__entry__2}

   | Field | Description |
   |-|-|
   | Number | Change request number is automatically generated to instantiate a logical connection with the Design in progress state. |
   | Category | Category of this change request. Select Other if your category isn't in the list. |
   | Priority | Priority of this change request. |
   | Short description | Summary of the design. |
   | Description | Description of the design in detail. |
   [Table 1. Setup request details form]

   {#create-logical-connection-record-design-assign-playbook__table_zxs_tmt_gtb}
5. Select Mark complete.
6. On the Setup logical connection card, fill in the fields.  
   {#create-logical-connection-record-design-assign-playbook__table_g5t_gg2_ndc__entry__2}

   | Field | Description |
   |-|-|
   | Logical connection model | Logical connection model where this logical connection is configured. |
   | Bandwidth | Bandwidth for this logical connection. Only bandwidths compatible with the logical connection model are listed here. Note: Lists all bandwidths if no compatible bandwidth is available. |
   | Network domain | Domain of ownership and responsibility for this network asset or connection. Select one of the following options: Mobility :   Network asset that is associated with the mobility equipment domain. Telco :   Network asset that is associated with the telco equipment domain. Core :   Network asset that is associated with the core equipment domain. |
   | Logical connection template | List of all templates based on the selected logical connection model. |
   [Table 2. Setup logical connection form]

   {#create-logical-connection-record-design-assign-playbook__table_g5t_gg2_ndc}
7. Select Mark complete.
8. On the Define end points card, fill in the fields.  
   {#create-logical-connection-record-design-assign-playbook__table_rkh_hg2_ndc__entry__2}

   | Field | Description |
   |-|-|
   | Start site | Originating network site for this connection. |
   | Start equipment | Originating equipment for this connection. |
   | Start interface | Originating network interface for this connection. |
   | End site | Destination network site for this connection. |
   | End equipment | Destination equipment for this connection. |
   | End interface | Destination network interface for this connection. |
   [Table 3. Define end points form]

   {#create-logical-connection-record-design-assign-playbook__table_rkh_hg2_ndc}
9. Select Mark complete.
10. On the Assign connection element card, select Add and fill in the fields to select the connection element.  
    To skip this activity, select Skip.
    {#create-logical-connection-record-design-assign-playbook__table_qth_hg2_ndc__entry__2}

    | Field | Description |
    |-|-|
    | Element type | Type of connection element. Select one from the list. * Network Interface * Physical Connection * Logical Connection * Equipment * Topology {#create-logical-connection-record-design-assign-playbook__ul_c4d_xnl_ndc} |
    | Element name | Connection element based on the event type that you're selected. By selecting the connection element, the Available capacity and Used capacity fields displays the capacity information of the connection element. |
    | Model | Model where this connection element is configured.Only compatible models based on the model relationship are displayed. |
    | Start Site | Originating network site for this connection element. Note: This field is available for Physical Connection and Logical Connection element types. |
    | End Site | Destination network site for this connection element. Note: This field is available only for Physical Connection and Logical Connection element types. |
    | Start equipment | Originating equipment for this connection element. Note: This field is available only for Physical Connection and Logical Connection element types. |
    | End equipment | Destination equipment for this connection element. Note: This field is available only for Physical Connection and Logical Connection element types. |
    | Route | Number of routes. |
    | Sequence | Number of sequences. |
    [Table 4. Assign connection element form]

    {#create-logical-connection-record-design-assign-playbook__table_qth_hg2_ndc}
11. Select Mark complete.
12. On the Assign protection element card, select Add and fill in the fields to select the protection element.  
    To skip this step, select Skip.
    {#create-logical-connection-record-design-assign-playbook__table_yqh_nh2_ndc__entry__2}

    | Field | Description |
    |-|-|
    | Start Site | Originating network site for this protection path. |
    | Start equipment | Originating equipment for this protection path. |
    | Model | Model where this protection logical connection is configured. Only compatible models based on the model relationship are displayed. |
    | End Site | Destination network site for this protection path. |
    | End equipment | Destination equipment for this protection path. |
    | Protecting logical connection | Logical connection that acts as redundancy path. |
    [Table 5. Assign protection element form]

    {#create-logical-connection-record-design-assign-playbook__table_yqh_nh2_ndc}
13. Select Mark complete.
14. On the Define number element card, select Add and fill in the fields to select the number element.  
    To skip this step, select Skip.
    {#create-logical-connection-record-design-assign-playbook__table_t5p_th2_ndc__entry__2}

    | Field | Description |
    |-|-|
    | Owned by configuration item | Configuration item (CI) that is related to the Inventory number record. |
    | Parent number type | Type of inventory number parent record belongs to. Select one from the following. * LAG * LAG Range * VLAN * VLAN range {#create-logical-connection-record-design-assign-playbook__ul_d2f_c1r_ndc} |
    | Parent number range | Range of parent number. |
    | Number Type | Type of inventory number this network inventory belongs to. Select one from the following. * LAG * LAG Range * VLAN * VLAN range {#create-logical-connection-record-design-assign-playbook__ul_tzq_51r_ndc} |
    | Number | Unassigned numbers are displayed here, and you can select multiple ones. |
    [Table 6. Define number element form]

    {#create-logical-connection-record-design-assign-playbook__table_t5p_th2_ndc}
15. Select Mark complete.
16. On the Define IP address card, select Add and fill in the fields to select the IP address.  
    To skip this step, select Skip.
    {#create-logical-connection-record-design-assign-playbook__table_nf2_zh2_ndc__entry__2}

    | Field | Description |
    |-|-|
    | IP pool | Parent pool of this IP address allocation. |
    | IP sub network | IP network subnet of this IP address allocation. |
    | Allocated IP address | Select the allocated IP addresses. |
    [Table 7. Define IP address card]

    {#create-logical-connection-record-design-assign-playbook__table_nf2_zh2_ndc}
17. **Optional:** Select Mark complete.
18. **Optional:** On the Set attributes card, select Add and fill in the fields to select the connection element.  
    If you want to skip this step, select Skip.
    {#create-logical-connection-record-design-assign-playbook__table_z44_f32_ndc__entry__2}

    | Field | Description |
    |-|-|
    | Connection name | Name of the logical connection record. Add connection name, otherwise default name is added |
    | Life cycle stage | Stage of the life cycle that this network asset is in: Deploy :   Network asset that is deployed in your network. Design :   Network asset that is being used for design purposes. End of life :   Network asset that is at the end of its useful life. Inventory :   Network asset that is an inventory item in use in the network. End of life :   Network asset that is missing and can't be located. Operational :   Network asset that is operational. Purchase :   Network asset that is in the purchase phase of its life. |
    | Life cycle stage status | Status of the network asset as it relates to the life cycle stage that it is in: In Maintenance :   Network asset that is currently in maintenance. In Use :   Network asset that is currently in use. Pending Retirement :   Network asset that is currently in maintenance. |
    | Supported by | Name of the person who supports this network asset. |
    | Supported by group | Group that supports the network inventory. |
    | Comments (Customer visible) | Any comments. |
    | Operational notes | Free-form operation note text for this network asset. For example, <kbd class="ph userinput">Check diesel fuel for generator</kbd>. |
    [Table 8. Set attributes card]

    {#create-logical-connection-record-design-assign-playbook__table_z44_f32_ndc}
19. On the Review and submit card, fill in the fields.  
    {#create-logical-connection-record-design-assign-playbook__table_tcj_sj2_ndc__entry__2}

    | Field | Description |
    |-|-|
    | Notes | Any additional notes. |
    [Table 9. Review and submit form]

    {#create-logical-connection-record-design-assign-playbook__table_tcj_sj2_ndc}
20. Select Submit.

## Result

The
change tasks are created and executed for each activity. The logical connection record is created. The created logical connection automatically associates the interface with its corresponding card or equipment.  
Note:  
The system now automatically associates each logical interface with its corresponding card or equipment. With the logical and physical interface alignment enhancement, logical interfaces (such as VLANs) and physical interfaces (such as Gigabyte Ethernet ports) are mapped to their parent equipment or card. The system establishes a parent relationship for each logical interface using the parent's unique serial number for accurate identification. This enhancement ensures consistency across systems and prevents duplicate CI creation by aligning identification and relationship logic between logical and physical interfaces.
**Related concepts**   

* [Logical connections](https://servicenow-prod.fluidtopics.net/HnM0HeI2SUU_xPhHpRs2rQ "Design and assign a logical connection in the Telecommunications Network Inventory application. By using the Design and Assign function, you can fulfill the logical connection design request of a customer.")

*[\>]: and then