Network Model Relationship fields
Summarize
Summary of Network Model Relationship fields
The Network Model Relationship form in the Yokohama release enables ServiceNow customers to define and manage various types of relationships between network model components. This is essential for accurately modeling compatibility and hierarchy in the Telecommunications Network Inventory application, improving network design and inventory management.
Show less
Key Features
- Name: Manufacturer-assigned name for the network model relationship.
- Relationship type: Defines the nature of the relationship between models, such as Rack to Rack Slot, Equipment to Slot, Equipment to Network Interface, Slot to Card, Card to Slot, Card to Network Interface, Physical Connection to Logical Connection, and more. Each relationship type determines which models appear as parent or child options.
- Parent product model: The parent in the relationship, selected from relevant equipment holders, racks, slots, cards, interfaces, or other applicable categories depending on the relationship type.
- Child product model: The child in the relationship, filtered by model category to ensure compatibility (e.g., slots, subslots, network interfaces, strands).
- Root product model: Used specifically for Slot to Card relationships to define a grandparent model (equipment or card) ensuring compatibility.
- Count: Specifies the number of child product models that can be created under a parent model for certain relationship types, facilitating template creation.
- Sequence: Defines the order of child entities in a relationship when multiple child models exist; automatically increments based on existing relationships.
- Parent and Child bandwidth: Available in Logical Connection to Channel relationships to specify bandwidth capacities.
Practical Implications
By using these fields and relationship types, customers can accurately model network infrastructure components and their interdependencies. This enables better inventory accuracy, equipment compatibility enforcement, and streamlined network design workflows within the Telecommunications Network Inventory application.
Each relationship type controls which models are selectable as parents and children, ensuring data integrity and reflecting real-world compatibility constraints. The inclusion of attributes like count and sequence supports detailed template creation and ordering of model components.
Next Steps
To utilize this functionality, customers should define network model relationships according to their network architecture needs, selecting appropriate relationship types and models. Refer to the related task "Define a network model relationship" for guided configuration.
The Network Model Relationship form enables you to create a network model relationship.
| Field | Description |
|---|---|
| Name | Manufacturer-assigned name of the network model relationship that is specified by the model manager. |
| Relationship type | Type of relationship. Select one of the following options:
|
| Count | Numbers of child product models that can be created under a parent product model when a template is created. Note: This attribute is only for Equipment to Slot, Rack to
Slot, Equipment to Network Interface, Interface card to Slot, Interface card to
Network Interface, Cable to Strand, and Logical Connection to
Channel relationship types. |
| Root product model | Grandparent model of the interface card for compatibility. Either select the equipment model or the interface card model. Then, select the search icon ( Note: This attribute is only visible for the Slot to Interface card relationship type. |
| Parent product model | Product model that is the parent to the child product model. Select the search icon ( Note: In the Rack-to-Slot relationship, the parent product model is the equipment holder model with the model category as Rack. |
| Child product model | Product model that is the child to the parent product model. Select the search icon ( Note: In the Rack to Slot relationship, the child product model is the equipment holder with model category as Slot. |
| Sequence | Sequence number of the child entities for a model relationship. If you enter a number in the Count field, the Sequence field appears. The default value is 1. If the parent model has multiple relationships, the sequence number for the first relationship is set to 1 and the number following the highest value of the first relationship is set for the consecutive relationships. For example, let's say that your equipment has a model relationship with two slots and two ports. When the relationship is created, the sequence number of the slots and ports are set to 1 and 3. Note: This attribute is only for Rack to Slot, Equipment to Slot, Equipment to Network Interface, Interface card to Slot,
Interface card to Network Interface,
Cable to Strand, and Logical Connection to Channel relationship types. |
| Parent bandwidth | Bandwidth of the parent product model. Note: This attribute is only visible for the Logical Connection to Channel relationship type. |
| Child bandwidth | Bandwidth of the child product model. Note: This attribute is only visible for the Logical Connection to Channel relationship type. |