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


---

# Network inventory models

# Network inventory models {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 6 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 Network inventory models

Network inventory models in the Telecommunications Network Inventory application enable you to track detailed technical information from manufacturers about network assets, such as telecommunications equipment and network interfaces.
These models encapsulate metadata including names, dimensions, compatible interface cards, and configurations, providing a standardized foundation when creating inventory records.
Defining these models and their relationships allows you to accurately represent your telecommunications infrastructure.
Show full answer Show less  

## Types of Inventory Models

The application supports multiple types of inventory models, each capturing specific metadata:

* **Facility Models:** Represent physical characteristics and behavior of facility hardware like power, HVAC, and connectivity components in data centers.
* **Equipment Models:** Contain vendor-provided metadata defining consistent characteristics across equipment instances.
* **Equipment Holder Models:** Define containers such as racks, cabinets, bays, and slots, with slot models representing different slot types (e.g., power slot, fan slot).
* **Interface Card Models:** Define attributes consistent across card instances.
* **Network Interface Models:** Capture physical and behavioral characteristics of network interfaces.
* **Physical Connection Models:** Capture metadata about physical connections.
* **Logical Connection Models:** Capture metadata about logical connections.
* **Cable Models:** Define cable-related metadata.
* **Strand Models:** Capture metadata about strands.
* **Network Topology Models:** Capture metadata defining network topology.

## Network Model Relationships

Relationships between inventory models define compatibility and connectivity within the network infrastructure. Key relationship types include:

* **Rack to Slot:** Compatibility between rack and slot models for equipment models.
* **Equipment to Slot:** Compatibility of slots and their quantity with equipment models.
* **Equipment to Network Interface:** Compatibility of network interfaces and their count with equipment models.
* **Slot to Interface Card:** Compatibility between slot and interface card models, enforcing root product model selections.
* **Interface Card to Slot:** Compatibility of slot models with interface card models.
* **Interface Card to Network Interface:** Compatibility of network interfaces with interface card models.
* **Physical Connection to Logical Connection:** Linking physical connections to logical ones.
* **Logical Connection to Logical Connection:** Defining relationships between logical connections.
* **Physical Connection to Network Interface:** Linking physical connections to network interfaces.
* **Logical Connection to Network Interface:** Linking logical connections to network interfaces.
* **Rack to Equipment and Cabinet to Equipment:** Associating equipment holders with equipment models.
* **Logical Connection to Channel:** Associating logical connections with channel models.

These relationships ensure accurate modeling of equipment compatibility and network connectivity, supporting effective management of telecommunications infrastructure.

## Accessing Inventory Models

You can access and manage inventory model forms through the Inventory Models node available in the Network Inventory Workspace List view, facilitating efficient creation and maintenance of your network inventory data.  
You define an inventory model in the Telecommunications Network Inventory application so that you can track the technical information from the manufacturer about a network asset such as the telco equipment or a network interface.

## Inventory models overview {#using-inventory-models-tni__section_hy4_xxn_htb}

A network inventory model contains the assets, services, and the relationships that define the infrastructure of your telecommunications networks. An inventory model contains the metadata for the name, number,
dimensions, compatible interface cards, and configurations from the manufacturer. When you instantiate an inventory record by using the design and assign function, your inventory record contains this standard manufacturer
information. To learn more about how to create an inventory model record, see [Create inventory models](https://servicenow-prod.fluidtopics.net/nc25yxLMMjHEnPV6HtY1KQ "As an inventory catalog manager, you can use a series of forms to define the metadata for each network model in the Telecommunications Network Inventory. During this process, you also specify the relationships between each of these models.").

After you create the inventory models, you can then define the relationships between the various network model entities. You can also define the compatibility between these entities. To learn more about model relationships, see [Network model relationships](https://servicenow-prod.fluidtopics.net/Te50HeS2xscvIjU~5MQjxw#using-inventory-models-tni__section_yps_kn2_cyb).

## Types of inventory models {#using-inventory-models-tni__section_cpm_nhv_jtb}

You can create the following types of inventory models:  

Facility Models
:   A network interface model captures the physical characteristics and data about the behavior of a facility hardware, as designated by the product manufacturer. Facility hardware represents the power, HVAC, network, and
    their connectivity in a data center.

Equipment Models
:   An equipment model represents the metadata that is provided by a vendor or manufacturer for the equipment. It defines the consistent
    characteristics across the various instances that are created for the equipment. An instance is an individual occurrence of a network asset at a site or datacenter. To learn more, see [Create an equipment model](https://servicenow-prod.fluidtopics.net/eA5xP31rQASdB4Otj7ldCA "Create an equipment model in the Telecommunications Network Inventory application as the first requirement for setting up the process to generate your network asset instances. You create an equipment model record every time a vendor or original equipment manufacturer (OEM) introduces new equipment for your use.").

Equipment holder models
:   An equipment holder model represents the metadata for the representation of containers, including the bays, cabinets, cages, line ups, relay
    racks, and slots. A Container Type field refers to the type of container that the equipment model represents To learn more, see [Create an equipment holder model](https://servicenow-prod.fluidtopics.net/6e2ViZCCPrn4CzhBtqnQoA "Create an equipment holder model in the Telecommunications Network Inventory application to define the physical characteristics data of the equipment holder according to the product manufacturer's recommendations. You create an equipment holder model every time a vendor or original equipment manufacturer (OEM) introduces a new equipment holder for your use.").

    The modeling guidelines for the slots vary according to the telecommunications service provider. The individual slot models are represented by the types of slots. Examples are a route processor slot, power slot, fan slot, or a generic slot model.. To learn more, see [Create an equipment holder model](https://servicenow-prod.fluidtopics.net/6e2ViZCCPrn4CzhBtqnQoA "Create an equipment holder model in the Telecommunications Network Inventory application to define the physical characteristics data of the equipment holder according to the product manufacturer's recommendations. You create an equipment holder model every time a vendor or original equipment manufacturer (OEM) introduces a new equipment holder for your use.").

Interface card models
:   A card model defines the card's metadata, which are the attributes that are consistent across the various instantiated cards of that model.. To learn more, see [Create a card model](https://servicenow-prod.fluidtopics.net/DRHUYTtS6RgEY5fozmGo9Q "Create a card model in the Telecommunications Network Inventory application to define the physical characteristics data of the card as per the product manufacturer's recommendations.").

Network interface models
:   A network interface model captures the physical characteristics and data about the behavior of a network interface, as designated by the product manufacturer. To learn more, see [Create a network interface model](https://servicenow-prod.fluidtopics.net/AS5wY_Z7zGi5vyV43cnFhw "Create a network interface model in the Telecommunications Network Inventory application to define the physical characteristics data of the network interface as per the product recommendations of the manufacturer.").

Physical connection model
:   A physical connection model captures the metadata for the physical connection. To learn more, see [Create a physical connection model](https://servicenow-prod.fluidtopics.net/D3M0iNKWx125dkTw8o0vNA "Create a physical connection model in the Telecommunications Network Inventory application to define the metadata for the different physical connections. In the physical connection model, you can import models, attach a file or an image, add or remove optional fields, and add compatibilities and substitutions.").

Logical connection model
:   A logical connection model captures the metadata for the logical connections. To learn more, see [Create a logical connection model](https://servicenow-prod.fluidtopics.net/oNqOyeOe5Hdxch8GJqcnPg "Create a logical connection model in the ServiceNow Telecommunications Network Inventory application to define the metadata for the different logical connections. In the logical connection model, you can import models, attach a file or an image, add or remove optional fields, and add compatibilities and substitutions.").

Cable model
:   A cable model captures the metadata for the cable. To learn more, see [Create a cable model](https://servicenow-prod.fluidtopics.net/y5Kp7MBZFRGHUEaNEFV5Uw "Create a cable model in the Telecommunications Network Inventory application to define the physical characteristics data of the cable according to the product recommendations of the manufacturer.").

Strand model
:   A strand model captures the metadata for the strand. To learn more, see [Create a strand model](https://servicenow-prod.fluidtopics.net/OK71TbWDjcqoFbKvcBbrIw "Create a strand model in the Telecommunications Network Inventory application to define the physical characteristics data of the strand according to the product recommendations of the manufacturer.").

Network topology model
:   A network topology model captures the metadata for the topology. To learn more, see [Create a network topology model](https://servicenow-prod.fluidtopics.net/dPtBgXMr3Q1f93w6W3JrYQ "Create a network topology model in the Telecommunications Network Inventory application to define the metadata for the topology according to your recommendations. You can use a topology model to create a record by using the design and assign function.").

## Network model relationships {#using-inventory-models-tni__section_yps_kn2_cyb}

A model relationship captures the relationships between the inventory models. By defining the relationships between the various network model entities, you can also define the compatibility between these entities.  
When setting up model relationships, you select one of the following options in the Relationship Type field:

--None--
:   No network model relationship exists.

Rack to Slot
:   Relationship between a rack model and a slot model. This relationship indicates that the rack and the slot models are compatible with the equipment model.

Equipment to Slot
:   Relationship between an equipment model and a slot model. This relationship indicates that the number of slots and the slot models are compatible with the equipment model.  
    Note:  
    * The Parent product model field shows a list of all the equipment models related to the Telecommunications Network Inventory application.
    * The Child product model field shows only the slot models.
    {#using-inventory-models-tni__ul_zrd_nkv_wvb}

Equipment to Network interface
:   Relationship between an equipment model and a network interface model. This relationship indicates the interface model and the number of interfaces that are compatible and supported with the equipment model.  
    Note:  
    * The Parent product model field shows a list of all the equipment models related to the Telecommunications Network Inventory application.
    * The Child product model field shows a list of all the network interface models related to the Telecommunications Network Inventory application.
    {#using-inventory-models-tni__ul_i2y_ljm_fwb}

Slot to Interface Card
:   Relationship between a slot model and an interface card model. This relationship enforces the Root product model field where an equipment model or a card model should be selected.  
    Note:  
    * The Root product model field shows a list of all the equipment models related to the Telecommunications Network Inventory application.
    * The Parent product model field shows the models of both the slots and subslots.
    * The Child product model field shows a list of all the interface card models.
    {#using-inventory-models-tni__ul_gfn_hnv_wvb}

Interface card to Slot
:   Relationship between an interface card model and a slot model. This relationship indicates that the slot model is compatible with the interface card model.  
    Note:  
    * The Parent product model field shows a list of all the interface card models.
    * The Child product model field shows only the models of the subslots.
    {#using-inventory-models-tni__ul_wdl_wkn_fwb}

Interface Card to Network interface
:   Relationship between an interface card model and a network interface model. This relationship indicates that the number of interfaces in the network interface model are compatible with the interface card model.  
    Note:  
    * The Parent product model field shows a list of all the interface card models.
    * The Child product model field shows a list of all the network interface models.
    {#using-inventory-models-tni__ul_ern_dln_fwb}

Physical Connection to Logical Connection
:   Relationship between the models of a physical connection to a logical connection.  
    Note:  
    * The Parent product model field shows a list of all the physical connection models.
    * The Child product model field shows a list of all the logical connection models.
    {#using-inventory-models-tni__ul_qhm_gln_fwb}

Logical Connection to Logical Connection
:   Relationship between one logical connection model to another logical connection model.  
    Note:  
    * The Parent product model field shows a list of all the logical connection models.
    * The Child product model field shows a list of all the logical connection models.
    {#using-inventory-models-tni__ul_avb_lln_fwb}

Physical Connection to Network Interface
:   Relationship between a physical connection to a network interface.  
    Note:  
    * The Parent product model field shows a list of all the physical connection models.
    * The Child product model field shows a list of all the network interface models.
    {#using-inventory-models-tni__ul_tgj_nln_fwb}

Logical Connection to Network Interface
:   Relationship between a logical connection to a network interface.  
    Note:  
    * The Parent product model field shows a list of all the logical connection models.
    * The Child product model field shows a list of all the network interface models.
    {#using-inventory-models-tni__ul_v3z_pln_fwb}

Rack to Equipment
:   Relationship between a rack and the equipment.  
    Note:  
    * The Parent product model field shows all equipment holders that have Container type as Rack.
    * The Child product model field shows all equipment models related to the Telecommunications Network Inventory application.
    {#using-inventory-models-tni__ul_ith_xln_fwb}

Cabinet to Equipment
:   Relationship between a cabinet and the equipment.  
    Note:  
    * The Parent product model field shows all equipment holders that have Container type as Cabinet.
    * The Child product model field shows all equipment models related to the Telecommunications Network Inventory application.
    {#using-inventory-models-tni__ul_awn_cqn_fwb}

Logical Connection to Channel
:   Relationship between a logical connection and the channel.  
    Note:  
    * The Parent product model field shows a list of all the logical connection models.
    * The Child product model field shows a list of all the channel models that have Behaviour as Channel.
    {#using-inventory-models-tni__ul_lyg_hzc_nzb}

To learn more about how to model your network inventory relationships, see [Modeling network inventory relationships](https://servicenow-prod.fluidtopics.net/VsOdKS1GIzk6jr35c0kmSQ "You model your network inventory relationships in the Telecommunications Network Inventory application so that you can use them in the inventory template relationships to create your network inventory records.").

## Accessing Inventory Model forms {#using-inventory-models-tni__section_ojk_qm1_m5b}

You can access the inventory model forms in the Inventory Models node in the Network Inventory Workspace List view.