Telecom Operations Map

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.

Key Features

• Defines the core FAB (Fulfillment, Assurance, Billing) operational process framework
• Provides a hierarchical model separating Customer, Service, and Network/Resource management layers
• Serves as a reference model for integrating OSS/BSS systems and achieving operational automation
• Adopted by 3GPP to provide business context for technology-specific management standards
• Promotes interoperability between different vendors' management systems and service providers' processes
• Forms the conceptual basis for more detailed frameworks like the TM Forum's Business Process Framework (eTOM)

Evolution Across Releases

Defining Specifications