TOM

Telecom Operations Map

Management →
Introduced in Rel-4 Also in: Core Network

TOM is the Telecom Operations Map, a TM Forum framework adopted by 3GPP that models telecom business processes for Fulfillment, Assurance, and Billing, providing a blueprint for OSS and BSS.

Category
Management
Introduced
Rel-4
Where
Management
Also touches
1 segments
Specifications
6 specs
TOM Description Purpose Related Classification Specifications

Description

The Telecom Operations Map (TOM), developed by the TeleManagement Forum (TM Forum) and referenced within 3GPP specifications, is a comprehensive, high-level framework that describes the key business processes required for a telecommunications service provider. It is not a 3GPP-invented protocol but an industry model that 3GPP aligns with for defining management and operations aspects. The TOM organizes processes hierarchically, focusing on the core vertical value chains of a service provider: Customer Care Processes and Service Development & Operations Processes. Its primary goal is to provide a standard reference model to guide the development of Operational Support Systems (OSS) and Business Support Systems (BSS), enabling automation, interoperability, and efficiency.

At its core, the TOM is built around the FAB model: Fulfillment, Assurance, and Billing. Fulfillment processes handle everything from order capture to service activation and configuration. Assurance processes are responsible for maintaining service quality, including performance monitoring, problem handling, and fault recovery. Billing processes manage rating, invoicing, and revenue collection. These three are considered the core customer-facing operations processes. Beneath them, the TOM defines Support & Readiness processes, which include functions like network inventory management, network provisioning, and workforce management. These support processes ensure the infrastructure is ready to execute the FAB processes. The model also defines Supplier/Partner Relationship Management processes.

Within the 3GPP context, specifications that reference the TOM (such as those in the 32-series on Telecommunication Management) use it as a foundation for defining more detailed, technology-specific management requirements. For example, 3GPP TS 32.101 outlines the principles for telecommunication management and aligns them with the TOM framework. It ensures that the management systems for 3GPP networks (e.g., for 5G Network Slice management) are designed with a process-oriented view that integrates with a service provider's overall OSS/BSS architecture. The TOM provides the business process context into which 3GPP's detailed network management interfaces (like the Itf-N reference point) and information models must fit. It helps ensure that automated processes for provisioning a 5G QoS flow or assuring a network slice lifecycle can be mapped to broader enterprise workflows for order-to-cash and trouble-to-resolve.

Purpose & Motivation

The Telecom Operations Map was created by the TM Forum to address the historical chaos and high costs associated with telecom service provider operations. Before such frameworks, each provider developed proprietary, siloed OSS/BSS systems that were difficult to integrate, automate, and adapt to new services. This led to long time-to-market for new services, high operational expenses (OPEX), and poor customer experience. The TOM provided a neutral, industry-agreed blueprint that allowed vendors and providers to discuss requirements and develop systems using a common language and process model.

3GPP's adoption and reference of the TOM in its management specifications serve a critical purpose: bridging the gap between the detailed, network-technology-specific management protocols defined by 3GPP and the broader business and operational context of the service provider. By aligning with TOM, 3GPP ensures that the management capabilities it standardizes for 4G/5G networks can be seamlessly integrated into the service provider's larger operational environment. It solves the problem of technology management being an isolated island. For instance, the TOM motivates the definition of standardized management services for network slicing (e.g., slice provisioning, performance assurance) that directly map to the Fulfillment and Assurance processes in the TOM, enabling end-to-end automation of slice-as-a-service offerings.

Classification

Part ofOSS
Related approachesBSS

Evolution Across Releases

Rel-4 Initial

Initial adoption of TOM concepts within 3GPP management specifications. 3GPP TS 32.101 (Telecommunication management; Principles and high level requirements) was established, formally referencing the TM Forum TOM to provide the business process context for all subsequent 3GPP management work. This laid the foundation for a process-oriented approach to managing 3G networks.

Expansion of management specifications for IP Multimedia Subsystem (IMS) and All-IP networks. The TOM framework guided the definition of management processes for these new services, ensuring provisioning, fault, and configuration management for IMS aligned with the broader Fulfillment and Assurance processes.

Introduction of LTE and the Evolved Packet Core (EPC). Management specifications for the new EPC elements (MME, S-GW, P-GW) and LTE radio network were developed within the context of the TOM, ensuring the operational processes for 4G could be integrated into service providers' existing OSS landscapes modeled on TOM/eTOM.

Management for 5G and Network Slicing. The TOM's process model is critically applied to the lifecycle management of network slices. Specifications define how slice instantiation, activation, and assurance map to the Fulfillment and Assurance processes, enabling the commercialization of slicing with automated OSS integration. The framework's principles are extended to manage new 5G core network functions and services.

Explore further

Broader topics and technologies where TOM plays a role.

Defining Specifications

3GPP specifications that define or reference TOM, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 23.060 vj00 GPRS Service Description Stage 2 Rel-19
TS 32.101 vj00 Management principles and high-level requirements Rel-19
TS 32.140 vj00 Subscription Management (SuM) requirements Rel-19
TS 32.150 vj00 IRP Concept and Definitions Rel-19
TS 44.064 vj00 GPRS Logical Link Control (LLC) Protocol Rel-19
TS 48.018 vj00 BSS-SGSN Interface for GPRS Control Rel-19