Telecom service inventory software that connects what you sell to what delivers it
Trace every service to the resources underneath it.
Build an auditable relationship between customer-facing services, technical services, logical resources and physical infrastructure. Investigate impact, fulfil orders and answer operational questions from one inventory model.
Four layers, connected
Product and customer-facing services sit on resource-facing technical services; technical services consume logical resources; logical resources map onto physical infrastructure. XIMS keeps catalog, order, service and resource inventories conceptually distinct — but linked — so each layer answers its own questions accurately.
Inventory objects
- Services and circuits
- Links and endpoints
- Devices and interfaces
- VLANs
- IP resources
- Number resources
- Access components
- Locations
- Ownership and status history
Object coverage follows the implemented scope of each deployment.
Navigate in both directions
From a customer service, find every supporting resource. From a failed device or circuit, identify potentially affected services. Impact accuracy depends on complete, maintained relationships — the inventory is a discipline, and XIMS gives it lifecycle controls to stay true.
Lifecycle and governance
Plan, reserve, allocate, activate, modify, suspend, cease and retire — each transition with approval, ownership and timestamp history. Data-model controls prevent invalid cross-domain assignments where implemented.
Orders and fulfilment
Order context reserves and allocates resources, creates fulfilment tasks, records activation evidence and updates inventory state — so the inventory reflects the network as delivered, not as intended. TM Forum-aligned interfaces are described only where implemented and verified; alignment is not certification.
Assurance and impact
Inventory relationships enrich alarms, incidents, planned maintenance and service-impact investigation with the services and customers behind each resource. XIMS complements — it is not positioned as a complete NMS beyond the functions that exist.
XonIPAM and XIMS relationship
Frequently asked questions
What is the difference between service and resource inventory?
Service inventory records what customers consume; resource inventory records the logical and physical assets that deliver it. Connecting the two is what makes impact and fulfilment questions answerable.
How does this relate to a CMDB?
A CMDB tracks IT configuration items broadly; telecom service inventory models services, circuits and network resources with telecom lifecycle and relationship semantics.
Does it include IP and number inventory?
Yes — through XonIPAM, which supplies governed IP address and telephone-number resources into the inventory model.
Are TM Forum APIs supported?
TM Forum-aligned and implemented interfaces are available where verified for the deployment; alignment does not imply certification.
Can we migrate from spreadsheets or legacy systems?
Yes. Migration uses controlled mapping, trial loads and reconciliation so relationships arrive complete rather than assumed.