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


---

# Model and template naming

# Model and template naming {#ariaid-title1}

Release version: Australia  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read  
The equipment model establishes default naming patterns for CIs (configuration items). Inventory templates inherit those patterns and can override them per related template.

## Equipment models and inventory templates {#how-models-and-templates-define-names__the-two-layers}

An equipment model defines a class of equipment, capturing structural facts like slot count, card types, and naming patterns for slots and interfaces.

An inventory template represents a way to configure equipment for your environment, selecting card models for slots, defining sub-component templates, and carrying naming patterns for CIs.

One model supports multiple templates. For example, the Cisco ASR 9006 model is the basis for both the Edge Template and the Router Template --- two configurations serving different network roles.

## Inheriting naming patterns from models {#how-models-and-templates-define-names__how-template-inherits-from-model}

When you create an inventory template, the system generates related templates matching the model's structure automatically. Name Pattern fields are pre-populated with the corresponding model
defaults. Slot and interface related templates inherit the model's naming patterns.

After creation, each related template
owns
its naming pattern independently. Changing the pattern on one related template has no effect on its siblings or on the model. To restore a related template's pattern to the model's default, you must edit the field manually.

## Customizing individual template patterns {#how-models-and-templates-define-names__how-overrides-behave}

After you create related templates, each template owns its own Name Pattern field. You can edit any template's pattern independently without affecting others. This enables you to customize naming conventions for exceptions, such as when a slot requires non-standard naming to integrate
with an external tool.

When you override a Name Pattern in a related template, the Inventory Template Overview tab displays the resolved name for each template as a tree node label. Inconsistencies appear together. For example, ten
slots following the standard pattern produce `Slot -1`, `Slot -2`, and so on, while an eleventh slot edited manually shows `Slot-11`. Review these differences to identify naming problems
before the template creates CIs.

## Roles and permissions {#how-models-and-templates-define-names__who-works-at-each-layer}

The role required to edit naming patterns differs by layer:

* The Inventory Catalog Manager role edits naming patterns at the equipment model level and establishes the organization's naming convention.
* The Inventory Template Manager role creates and updates inventory templates, including editing the inherited naming patterns on related templates.

Users who create CIs from existing templates don't write or edit naming patterns --- they use the names the patterns produce.

## Benefits of the two-layer model {#how-models-and-templates-define-names__what-two-layer-model-achieves}

Separating model and template responsibilities lets you:

* Define an organization-wide naming convention once, at the model level, so every template based on that model starts with the same defaults.
* Adjust individual templates only where exceptions are necessary, without affecting any other templates that share the same model.
**Related concepts**   

* [Inventory template naming patterns](https://servicenow-prod.fluidtopics.net/Ur7JKaJYvarOaFuXVjwhTg "A naming pattern is a JavaScript expression that defines how a configuration item (CI) is named when it is created from an inventory template.")
* [Inventory template name generation](https://servicenow-prod.fluidtopics.net/CCrLEtlGESzt1X5cp~lJ6Q "When you instantiate an inventory template, each related template in the hierarchy produces a CI (configuration item). The CI's name comes from one of two sources, depending on whether the related template defines a naming pattern.")
* [Inventory template hierarchy view](https://servicenow-prod.fluidtopics.net/OS5FfXQqJRLARW~lpc5gSw "The Overview tab on an inventory template record shows the full template hierarchy as a tree. Use it to check resolved CI names and spot validation errors before deploying the template.")