This section provides a comprehensive reference mapping of eTOM processes from Level 1 domains down through Level 2 capabilities to Level 3 tasks. It covers all processes relevant to the two primary telco operational flows: Lead-to-Cash (Fulfilment) and Trouble-to-Resolve (Assurance), plus Billing/Revenue Management and the Strategy, Infrastructure & Product processes that define what gets operated.
Each row maps a specific L3 process task to its parent L2 capability, the typical system domain (BSS, OSS, or Shared), the primary owning function, and examples of generic supporting systems. This table is designed for use in architecture reviews, vendor evaluations, process-to-system mapping, and training.
📋Source: TM Forum eTOM (GB921)
This mapping is based on the TM Forum enhanced Telecom Operations Map (eTOM), published as GB921 within the TM Forum Frameworx suite. The eTOM hierarchy used here reflects the standard Operations matrix (Fulfilment × Assurance × Billing crossed with CRM × SM&O × RM&O × S/PM) and the SIP (Strategy, Infrastructure & Product) area. Process numbering follows eTOM conventions. Descriptions are written in plain English for training use.
💡How to Read This Table
The table is organised by eTOM Level 1 domain. Within each domain, Level 2 capabilities are grouped with their Level 3 tasks listed beneath. The "Typical System Type" column indicates whether the process is primarily served by BSS, OSS, or Shared systems. "Primary Owning Function" identifies the team or capability that owns the process. "Example Supporting Systems" lists generic system types (not vendor products) that typically implement or contribute to the process.
Operations — Fulfilment Processes
Fulfilment processes deliver what the customer ordered. They traverse the entire eTOM Operations matrix from CRM (commercial order capture) through SM&O (service orchestration) to RM&O (resource provisioning). These are the core Lead-to-Cash processes.
Fulfilment — CRM Layer
Fulfilment × CRM: Marketing, Selling & Order Handling (L1–L3)
eTOM L1 Domain
eTOM L2 Capability
eTOM L3 Task
Description
System Type
Primary Function
Example Systems
Fulfilment / CRM
Marketing Fulfilment Response
Determine Marketing Fulfilment Response
Assess customer response to campaigns and determine the appropriate next-best-action or follow-up
BSS
Marketing
Campaign Platform, CRM, Marketing Analytics
Fulfilment / CRM
Marketing Fulfilment Response
Issue Specific Marketing Information
Generate and deliver targeted marketing materials, promotions, and product information to qualified prospects
BSS
Marketing
Campaign Engine, Digital Channel Platform, Content Management
Fulfilment / CRM
Marketing Fulfilment Response
Track & Manage Fulfilment Response
Monitor campaign effectiveness, conversion rates, and manage the prospect engagement lifecycle
BSS
Marketing
Marketing Analytics, CRM, Campaign Platform
Fulfilment / CRM
Selling
Manage Prospect
Create and manage prospect records, track interactions across channels, and qualify leads into sales opportunities
BSS
Sales
CRM, Lead Management
Fulfilment / CRM
Selling
Qualify & Educate Customer
Assess customer needs, validate service availability at their location, and present relevant product offerings
BSS
Sales
CRM, CPQ, Product Catalog, Service Qualification
Fulfilment / CRM
Selling
Cross/Up Sell
Identify opportunities to offer additional or upgraded products to existing customers based on usage and eligibility
Assurance processes ensure that delivered services continue to work correctly. They cover the entire Trouble-to-Resolve flow: from customer-reported problems through service-level fault diagnosis to resource-level trouble resolution. Assurance also includes proactive quality monitoring and SLA management.
Assurance — CRM Layer
Assurance × CRM: Problem Handling & QoS/SLA Management (L1–L3)
eTOM L1 Domain
eTOM L2 Capability
eTOM L3 Task
Description
System Type
Primary Function
Example Systems
Assurance / CRM
Problem Handling
Create Customer Problem Report
Receive and log customer-reported issues from any channel (call centre, digital, retail, partner) as a trouble ticket
BSS
CRM / Service Desk
CRM, Trouble Ticket System (TMF621), Self-Service Portal
Assurance / CRM
Problem Handling
Isolate Customer Problem
Perform initial triage to determine if the issue is customer-side, service-side, or network-side; classify severity and priority
Shared
CRM / Service Desk
CRM, Trouble Ticket System, Service Quality Dashboard
Assurance / CRM
Problem Handling
Report Customer Problem
Provide status updates to the customer on investigation progress, expected resolution time, and any interim workarounds
Billing processes convert delivered services into revenue. They encompass the complete revenue lifecycle: usage data collection, rating and charging, invoice generation, payment processing, and revenue assurance. In eTOM, billing is a vertical process area that primarily maps to BSS systems.
Billing & Revenue Management: Full L1–L3 Mapping
eTOM L1 Domain
eTOM L2 Capability
eTOM L3 Task
Description
System Type
Primary Function
Example Systems
Billing
Billing & Collections Management
Manage Customer Billing
Generate and present customer bills/invoices based on rated usage records, recurring subscriptions, and one-time charges
Track, manage, and reconcile loyalty points, rewards accrual, and redemption across customer accounts
BSS
Loyalty / Billing
Loyalty Platform, Balance Management, CRM
Strategy, Infrastructure & Product (SIP)
SIP processes define what gets operated. While Operations processes handle day-to-day execution, SIP processes handle the design, planning, and lifecycle management of products, services, and resources. These "build" processes run on a longer cadence (weeks to months) and are essential for understanding how new products and services come into existence.
💡Why SIP Matters for Architecture
Many architects focus exclusively on Operations processes and overlook SIP. But SIP processes like "Product & Offer Portfolio Planning" and "Service Capability Delivery" define how new catalog entries are created, how service specifications are designed, and how resource types are onboarded. Without SIP, Operations has nothing to operate.
Marketing & Offer Management
SIP — Marketing & Offer Management (L1–L3)
eTOM L1 Domain
eTOM L2 Capability
eTOM L3 Task
Description
System Type
Primary Function
Example Systems
SIP / Marketing
Market Strategy & Policy
Gather & Analyse Market Information
Collect competitive intelligence, market research, customer insights, and technology trends to inform commercial strategy
Implement new resource types, network topology changes, and activation templates in the resource catalog and NMS
OSS
Network Engineering
Resource Catalog, Network Design, EMS/NMS
SIP / Resource
Resource Capability Delivery
Manage Resource Deployment
Deploy and commission new network resources, update resource inventory, and validate operational readiness
OSS
Network Engineering
Resource Inventory, EMS/NMS, Field Workforce Management
SIP — Infrastructure & Technology Governance
Infrastructure and technology governance processes define how BSS/OSS platforms are managed as technology assets — covering integration standards, API governance, data platform strategy, and shared infrastructure. These processes are often neglected in BSS/OSS architecture discussions, but they directly constrain what the operational processes can achieve.
SIP — Infrastructure & Technology Governance
L1 Domain
L2 Capability
L3 Task
Description
System Type
Primary Function
Example Systems
SIP / Infrastructure
API & Integration Governance
Define API Standards & Contracts
Establish API design standards (TMF Open API compliance), versioning policies, and contract-first development requirements across all BSS/OSS components
Shared
Enterprise Architecture
API Gateway, API Developer Portal, Schema Registry
SIP / Infrastructure
API & Integration Governance
Manage API Lifecycle
Track API versions across all BSS/OSS components, manage deprecation schedules, and enforce backward compatibility requirements
Shared
Integration Architecture
API Management Platform, Service Mesh, API Catalog
SIP / Infrastructure
API & Integration Governance
Manage Event Schema Standards
Define event schema standards (TMF688), maintain schema registry for all domain events, and enforce schema evolution rules (forward/backward compatibility)
Shared
Integration Architecture
Schema Registry, Event Catalog, Event Bus Platform
SIP / Infrastructure
Data Platform Governance
Define Data Architecture Standards
Establish enterprise data model alignment with TM Forum SID, define data ownership per domain, and maintain data catalog across all BSS/OSS components
Shared
Data Architecture
Data Catalog, Metadata Management, Master Data Management
SIP / Infrastructure
Data Platform Governance
Manage Analytics & Reporting Platform
Govern shared analytics infrastructure: data lake/warehouse ingestion, transformation pipelines, BI tooling standards, and reporting access controls
Shared
Data Architecture
Data Lake/Warehouse, ETL/ELT Platform, BI Tools
SIP / Infrastructure
Platform & Cloud Governance
Manage Shared Platform Services
Govern shared infrastructure services used by all BSS/OSS components: container orchestration, observability stack, IAM, and secret management
Shared
Platform Engineering
Kubernetes, Service Mesh, Observability Stack, IAM
SIP / Infrastructure
Platform & Cloud Governance
Manage Deployment & Release Standards
Define CI/CD standards, deployment pipeline governance, environment management, and release coordination across BSS/OSS components
Shared
Platform Engineering
CI/CD Platform, Container Registry, GitOps Tools
Key Observations from the Mapping
📋BSS/OSS Boundary Is Clear at L3
At Level 3, the BSS/OSS boundary becomes unambiguous. CRM-layer tasks (Order Handling, Problem Handling, Billing) are firmly BSS. SM&O tasks (Service Configuration, Service Quality) and RM&O tasks (Resource Provisioning, Resource Trouble) are firmly OSS. The Shared system type appears at integration points — particularly order feasibility checks and SLA management — where BSS must query OSS for technical information.
💡Fulfilment Follows a Clear Chain
The Fulfilment vertical follows a strict chain: CRM Layer (Order Handling in COM) → SM&O Layer (Service Configuration in SOM) → RM&O Layer (Resource Provisioning in ROM). Each layer generates orders for the next. This chain is the backbone of the Lead-to-Cash flow and maps directly to TMF622 → TMF641 → TMF652.
💡Assurance Flows in Reverse
Assurance processes flow in the opposite direction from Fulfilment. Resource alarms bubble up from RM&O (Resource Trouble Management) to SM&O (Service Problem Management) to CRM (Problem Handling). Impact analysis translates resource faults into customer-visible service degradation. This reverse flow requires tight correlation between resource inventory, service inventory, and customer records.
⚠️SIP Processes Are Often Neglected
Many telco architectures systematically underinvest in SIP processes. Product Lifecycle Management, Service Design, and Resource Planning are often manual, spreadsheet-based activities. This creates a bottleneck: Operations processes are automated, but the catalog and design processes that feed them are not. This is why "time to market" remains slow even after BSS/OSS modernisation.
Coverage Summary
eTOM L1–L3 Coverage Summary
Process Area
L2 Capabilities
L3 Tasks
Primary System Domain
Fulfilment / CRM
3
14
BSS (COM, CRM, CPQ)
Fulfilment / SM&O
2
10
OSS (SOM)
Fulfilment / RM&O
2
9
OSS (ROM)
Fulfilment / S/PM
1
3
Shared (Partner Mgmt)
Assurance / CRM
2
10
BSS (CRM, Trouble Ticket)
Assurance / SM&O
2
9
OSS (Fault Mgmt, Service Quality)
Assurance / RM&O
3
13
OSS (NMS, Mediation)
Assurance / S/PM
2
5
Shared (Partner Mgmt)
Billing & Revenue
4
12
BSS (Billing, Charging)
SIP / Marketing
3
8
BSS (Product Mgmt)
SIP / Service
2
4
OSS (Service Architecture)
SIP / Resource
2
4
OSS (Network Planning)
SIP / Infrastructure
3
7
Shared (Enterprise Architecture, Platform)
This mapping covers 31 eTOM Level 2 capabilities decomposed into 108 Level 3 tasks across all process areas relevant to Lead-to-Cash, Trouble-to-Resolve, and Infrastructure Governance. This represents the core operational scope that any BSS/OSS architecture must address.
eTOM L1–L3 Capability Mapping — Key Points
The eTOM Operations matrix covers 3 vertical process areas (Fulfilment, Assurance, Billing) crossed with 4 horizontal layers (CRM, SM&O, RM&O, S/PM)
At Level 3, the mapping becomes unambiguous: each task maps to a clear BSS or OSS system domain
Fulfilment follows a strict chain: COM (CRM layer) → SOM (SM&O layer) → ROM (RM&O layer), matching TMF622 → TMF641 → TMF652
Assurance flows in reverse: resource alarms (RM&O) → service impact (SM&O) → customer notification (CRM)
Billing processes are entirely BSS-owned but depend on mediation data collected by OSS systems
SIP processes (Product, Service, Resource Design) define what Operations processes execute — they are the "build" side of the framework
SIP / Infrastructure processes (API governance, data platform, cloud governance) are cross-cutting and often neglected — but they constrain what operational processes can achieve
This reference covers 31 L2 capabilities and 108 L3 tasks — use it for vendor evaluation, gap analysis, and process-to-system mapping
No CSP implements all eTOM processes — select the subset relevant to your business and map those to your systems