Network Inventory Overview

What network inventory means in telco — the runtime record of physical and logical resources on the network, managed by solutions like Ericsson Adaptive Inventory.

What "Network Inventory" Means in Telco

In this platform, inventory refers exclusively to physical and logical network resources — the devices, ports, cables, VLANs, IP addresses, spectrum, and topology that make up the operator's infrastructure. Network inventory answers the fundamental question: "What physical and logical resources exist on my network, what state are they in, and what is available for use?"

Network Inventory (Resource Inventory)

The runtime repository of all physical and logical resources deployed on the operator's network. Tracks devices, ports, cables, VLANs, IP addresses, spectrum, network slices, VNFs, and topology relationships. Managed via TMF639 Resource Inventory Management API. This is the infrastructure-level source of truth that ROM, activation engines, capacity planning, and service assurance depend on.

Scope Clarification

Product Inventory (SLM / TMF637) and SLM (TMF638) — which track what customers have bought and what CFS/RFS instances are running — are covered in Module 3: Order Management. This module focuses on the physical and logical network layer: TMF639 Resource Inventory.

What Network Inventory Tracks

Physical vs Logical Resources

Aspect	Physical Resources	Logical Resources
Examples	Routers, switches, OLTs, ONTs, cables, racks, cards, ports	VLANs, IP addresses, VRFs, QoS policies, VNF instances, network slices
Lifecycle	Installed → Commissioned → In-Service → Decommissioned	Created → Assigned → In-Use → Released
Capacity concern	Port exhaustion, shelf space, fibre pair availability	VLAN ID exhaustion, IP pool depletion, slice capacity

Topology & Resource Relationships

Network inventory is not a flat list of devices. It models topology — the containment, connectivity, and dependency relationships between resources. These relationships are what make inventory useful for fault correlation, capacity planning, and activation.

Containment: A chassis contains cards; a card contains ports; a rack contains chassis
Connectivity: Port A on Switch 1 connects to Port B on Switch 2 via a fibre link
Dependency: A VLAN depends on the underlying ports; a VNF depends on the compute host
Grouping: Resources in an aggregation ring; devices in a PoP; all ports in an access node

Topology in Practice

When OLT-EAST-07 fails, network inventory tells you: it contains 16 line cards with 256 ports, 190 of which have active ONT connections. This containment and connectivity topology is what enables automated service impact analysis — without it, fault management is manual guesswork.

Resource Catalog vs Resource Inventory

Aspect	Resource Catalog (Design-Time)	Resource Inventory (Runtime)
Purpose	Define what types of resources CAN exist	Track what resources ACTUALLY exist on the network
Example entry	"Huawei MA5800 OLT" specification with port types and capacity	"OLT-EAST-07, serial #HW2024-0847, location: Building A Rack 12"
Change frequency	Updated when new equipment types are introduced	Updated constantly — every install, swap, decommission, allocation
TMF API	TMF634 Resource Catalog Management	TMF639 Resource Inventory Management

Why Network Inventory Is Critical

Network inventory is consumed by nearly every OSS process. If it does not reflect reality, the consequences cascade across fulfilment, assurance, and planning.

Order Fulfilment: ROM queries inventory for available ports, IPs, and VLANs. Inaccurate inventory causes activation failures or double-allocation.
Fault Management: Topology enables automated impact analysis — from a failed device to affected customers. Without it, every fault requires manual investigation.
Capacity Planning: Tracks utilisation of ports, IP pools, and spectrum. Enables proactive expansion before exhaustion.
Network Discovery: Polling the live network to detect drift between inventory records and actual state — essential for maintaining accuracy in brownfield environments.

The Inventory Accuracy Problem

Many operators struggle with network inventory accuracy. Physical resources get swapped without updating systems. Manual provisioning bypasses inventory updates. Legacy migrations leave ghost entries. The result is a growing gap between what inventory says and what actually exists on the network.

Common Accuracy Issues

Stale entries (removed devices still in inventory), phantom availability (resources marked "free" that are in use), orphaned logical resources (VLANs with no physical port), and missing topology (connectivity not modelled). These compound over time — mature operators implement continuous reconciliation, polling network elements and comparing against inventory records to detect drift.

Source of Record

Network Inventory Source of Record

Entity	System of Record	System of Engagement	System of Reference	Notes
Physical Resource (device, port, cable)	Resource Inventory	Field Operations / Logistics	Network Planning, Capacity systems	Network inventory owns physical asset state and location.
Logical Resource (VLAN, IP, VRF, policy)	Resource Inventory	ROM / Activation engine	SLM, IPAM	Logical allocations tracked and lifecycle-managed here.
Network Topology	Resource Inventory	Network Discovery / SDN controllers	Fault Management, Capacity Planning	Containment and connectivity relationships modelled here.

Section 4.1 Key Takeaways

"Inventory" here means physical and logical network resources — devices, ports, VLANs, IPs, topology
Product Inventory (SLM) and SLM are outputs of order management, covered in Module 3
Topology modelling (containment, connectivity, dependency) enables fault correlation and capacity planning
Resource Inventory is the Source of Record for infrastructure state — managed via TMF639
Inventory accuracy is one of the hardest operational challenges — reconciliation against the live network is essential