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


---

# Import models

# Import models {#ariaid-title1}

Release version: Australia  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Bulk-import models and their hierarchical relationships into Telecommunications Network Inventory by uploading a structured Excel file.

## Importing models overview {#import-inventory__section_hvp_crs_bjc}

You can import equipment models and their hierarchical relationships in bulk by uploading a structured Excel file. The Excel import supports these core physical hardware model types:

* Equipment Model
* Equipment Holder Model
* Card Model
* Facility model
* Interface Model

## Importing models process {#import-inventory__section_s5n_grs_bjc}

On import model request submission, the system processes each row in the Excel file and creates the following records in a single operation:

* Equipment models
* Equipment holder models
* Card models
* Network interface models

The models are based on the model class and model category specified in each row. Model relationships between these models are based on the relationship type, parent entity ID, and root entity ID values in the spreadsheet.
Model relationships are created only for the rows where the relationship type, parent entity ID, and root entity ID are defined in the Excel file.

You must manually create any model relationships not defined in the spreadsheet. To learn more, 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."). If a model already exists in the system, the record is matched and updated to prevent duplicates.

During the import, the Integration Commons for CMDB plugin runs in the background. Normalization rules are applied to manufacturer and company names to keep your data clean and standardized. The normalization rules are
applied only if the Normalization Data Service Client is installed. To learn more, see [Normalization data services](https://www.servicenow.com/docs/access?context=c_NormalizationOverview&version=australia&pubname=australia-platform-administration&ft:locale=en-US).

The import also auto-generates a first-level set of inventory templates for every equipment and card model created. Related templates are auto generated under the parent equipment template based on the defined model
relationships and the count values from the spreadsheet. The auto-generated templates provide a flat, first-level set of templates that can be enriched using the import template feature. To learn the step-by-step process of
importing models, see [Import a model](https://servicenow-prod.fluidtopics.net/gbAPPFrSmctAxdS~sYT9IQ "Create an import model request to import your collection of models, and streamline the workflow using the Telecommunications Network Inventory application.").

A detailed Import Results summary is produced. The summary shows total records processed, broken down into inserted, updated, skipped, ignored, and failed records.
**Related concepts**   

* [Importing models and templates in JSON format](https://servicenow-prod.fluidtopics.net/1TKi761VZNTGwHBoy_ptMQ "Import equipment models and inventory templates together in a single operation using JSON format in the Telecommunications Network Inventory application.")
* [Exporting hierarchy of models and templates](https://servicenow-prod.fluidtopics.net/sD6KPuceB93NTC~0yaBqzg "Export equipment models, inventory templates, and related records to support development-to-production migration of network inventory data.")