Inventory Management – Resource & Service Inventory
Learning Objective: Understand telecom inventory management – the systems that track physical and virtual resources (routers, ports, IP addresses) and the logical services built on them (VPNs, VoLTE, broadband). Inventory is the operational "single source of truth" for provisioning, assurance, and billing.
Inventory as the "Single Source of Truth"
OSS systems rely on inventory as the authoritative source for network resources, service relationships, and operational state. Inaccurate inventory leads directly to provisioning failures, incorrect impact analysis, and automation issues. Inventory must be continuously reconciled with the actual network.
What is Telecom Inventory?
Telecom inventory is the system of record for all network assets – both physical and logical – and their relationships. It answers questions like:
- Which routers are deployed in Mumbai, and which ports are free?
- Which customers are served by a specific gNB (5G base station)?
- What IP addresses are allocated to which network functions?
- If a fibre cable fails, which services are impacted?
Physical vs Logical Inventory
- Physical inventory: Routers, line cards, ports, fibres, racks, antennas, GPS coordinates, serial numbers.
- Logical inventory: VLANs, VPNs, IP subnets, MPLS tunnels, 5G slices, network function instances.
- OSS platforms maintain relationships between physical and logical layers for assurance, provisioning, and impact analysis.
Inventory tracks what resources and services exist. Topology describes how those resources connect and depend on each other across the network. Both are needed for complete operational visibility.
Two Core Types of Telecom Inventory
Resource Inventory (TMF639)
Physical and virtual network assets:
- Network elements – routers, switches, gNBs, OLTs
- Physical ports, line cards, transceivers, cables
- IP addresses, VLANs, MPLS labels
- Software versions, license entitlements
- Site locations, rack positions, geographic coordinates
Service Inventory (TMF638)
Logical services built on resources:
- Customer VPNs (L2VPN, L3VPN, EVPN)
- VoLTE, 5G slices, broadband connections
- Private network segments, enterprise connectivity
- SLA tiers (Gold, Silver, Bronze)
- Service relationships – which resources support which services
How Resource and Service Inventory Connect
A single resource may support multiple services. A single service may depend on multiple resources.
Why Inventory Matters in Real Operations
- Service impact analysis: When a router fails, inventory tells you which customer VPNs, broadband connections, and voice services are affected.
- Provisioning automation: Inventory must know which ports are available before activating a new service.
- Capacity planning: Inventory tracks utilisation trends to predict when new hardware is needed.
- Disaster recovery: Accurate inventory is essential for network restoration after outages.
- Audit and compliance: Operators must know what assets exist, where they are located, and their software versions.
- BSS integration: Service inventory maps customer-facing products to underlying network resources.
Real-World Example: Inventory in Action
A customer orders a new 1Gbps enterprise VPN:
- BSS sends order to OSS
- Resource inventory checks available port capacity on the customer's access router
- Resource inventory reserves an IP address from the available pool
- Service inventory creates a new service record referencing the reserved resources
- Provisioning system configures the router using data from inventory
- Service inventory marks the service as ACTIVE and returns service ID to BSS
Inventory can be populated in two ways:
- Automated discovery: Discovery systems or EMS platforms collect network data via SNMP, Netconf, gNMI, or vendor APIs and synchronize it with inventory systems.
- Manual entry / import: Legacy networks may require spreadsheets or bulk imports.
- Reconciliation: Inventory systems continuously verify that their records match actual network state. Mismatches cause provisioning errors.
Modern orchestration systems increasingly use inventory dynamically to determine resource availability, policy compliance, and automated placement decisions for services and network slices.
Large operators often have multiple inventory systems (RAN inventory, transport inventory, core inventory, service inventory). East-West interfaces synchronize data across these systems to maintain a unified view.
TM Forum Standards for Inventory
| Standard | Purpose | Example Use |
|---|---|---|
| TMF639 (Resource Inventory) | Standard API for physical/virtual resource management | Query available router ports, retrieve device details |
| TMF638 (Service Inventory) | Standard API for service inventory and service state management | Create VLAN service, retrieve service status, map service to resources |
| SID (Shared Information/Data Model) | Standard data models for inventory entities | Resource attributes, service relationships, topology structures |
Connection to BSS
Inventory is the bridge between network resources and customer-facing products:
- Product catalog: BSS product definitions reference inventory resource groups
- Order feasibility: BSS checks inventory availability before accepting customer orders
- Customer bills: Service inventory maps usage records to customer accounts
- SLA management: Service inventory tracks which SLAs apply to which services
Real-World Inventory Challenges
- Inventory drift: Network changes made manually (via CLI) without updating inventory system
- Multi-vendor complexity: Each vendor models inventory differently (different MIBs, YANG models)
- Legacy systems: Old inventory data may be incomplete or inaccurate
- Dynamic cloud environments: Virtual resources (CNFs, VNFs) appear/disappear frequently
- Synchronization latency: Delay between network change and inventory update causes provisioning failures
Common Interview Questions
Q1. What is the difference between resource inventory and service inventory?
Resource inventory tracks physical and virtual network assets (routers, ports, IP addresses). Service inventory tracks logical services built on those resources (VPNs, VoLTE, broadband). They are linked by relationships – a service depends on underlying resources.
Q2. Why is inventory critical for service assurance?
When a fault occurs on a resource, inventory tells you which services and customers are affected. Without this mapping, you cannot determine impact or prioritize repairs.
Q3. How does inventory support provisioning?
Inventory tracks which resources are available, reserved, or in-use. Before provisioning a service, OSS checks inventory for free capacity, reserves it, and updates status after activation.
Q4. What TMF APIs are used for inventory?
TMF639 for resource inventory, TMF638 for service inventory, and SID for data modelling.
Q5. What causes inventory drift and how is it managed?
Inventory drift occurs when network changes are made without updating inventory (e.g., CLI changes). It is managed through reconciliation – periodic automated discovery to detect and correct mismatches.
Key Terms
Takeaways for You
- Resource inventory tracks physical and virtual network assets (routers, ports, IP addresses, licenses).
- Service inventory tracks logical services built on resources (VPNs, VoLTE, 5G slices).
- Service impact analysis uses inventory relationships to determine which customers are affected by a fault.
- Inventory discovery & reconciliation ensure inventory matches actual network state.
- Inventory is the "single source of truth" – inaccurate inventory causes provisioning failures and automation issues.
- TM Forum standards: TMF639 (resource), TMF638 (service), SID (data model).
- Inventory federations synchronizes across multiple inventory systems in large operators.
- Physical vs logical inventory – both must be maintained and linked for complete visibility.
- Inventory drift – manual network changes without inventory updates – is a major operational challenge.
Recommended Next Learning Path