BSS vs OSS

What BSS and OSS actually are, what they own, and why the boundary between them matters.

Last updated 14 Oct 2026

Every telco runs on two families of systems — BSS on the commercial side and OSS on the technical side. Each answers one question:

BSS — Business Support Systems

The commercial engine: customer management, product catalogs, order capture, billing, and revenue management. BSS answers: "What did the customer buy, and how much do they owe?"

OSS — Operational Support Systems

The technical engine: service design, network activation, resource management, fault handling, and performance monitoring. OSS answers: "What is running on the network, and is it working?"

Why the boundary matters

Understanding where BSS ends and OSS begins is the single most important foundation for telco architecture. It decides who owns each piece of data, where an order is handed over, and which system is the source of truth.

BSS — Business Support Systems

CRM

Customer Mgmt

Product Catalog

Commercial Offers

CPQ

Configure Price Quote

COM

Order Management

Billing

Revenue & Charging

Product Inventory

Subscriptions

ERP

Finance, Stock & Logistics

OSS — Operations Support Systems

Service Catalog

CFS Definitions

Resource Catalog

RFS / Resource Specs

SOM

Service Order Mgmt

ROM

Resource Order Mgmt

Service Inventory

Active Services

Resource Inventory

Network Assets

Order Decomposition: Commercial → Service → Resource

The BSS/OSS domain split — key systems in each domain

Key Systems by Domain

BSS — The Shopfront

System	Purpose	TM Forum Domain
CRM	Manages customers, accounts, contacts, and interactions	Party Management
Product Catalog	Defines what can be sold — product offerings, pricing, rules	Product Management
CPQ	Configure, Price, Quote — helps sales build valid offers	Sales Management
Order Management (COM)	Captures and manages commercial orders	Order Management
Billing & Rating	Calculates charges and produces invoices	Revenue Management
Product Inventory	Tracks what each customer currently has (subscriptions)	Product Inventory
ERP	Finance ledger, stock, procurement and logistics — books billed revenue and supplies the hardware an order needs	Enterprise Management (eTOM) — beside the BSS, outside the ODA core

OSS — The Factory

System	Purpose	TM Forum Domain
Service Catalog	Defines CFS/RFS decomposition — how services map to resources	Service Management
Resource Catalog	Defines resource types and their configurations	Resource Management
Service Order Mgmt (SOM)	Orchestrates service-level fulfilment	Service Orchestration
Resource Order Mgmt (ROM)	Orchestrates resource-level provisioning	Resource Provisioning
Service Inventory	Tracks instantiated service instances	Service Inventory
Resource Inventory	Tracks physical and logical network resources	Resource Inventory

Why the Boundary Matters

The BSS/OSS boundary reflects a fundamental difference in data ownership, change velocity, and domain expertise. BSS is the shopfront — everything the customer sees. OSS is the factory — everything behind the scenes. A customer orders "100Mbps Broadband" through BSS. OSS figures out how to make that happen on the network. Blurring this boundary is one of the most common causes of failed telco transformations.

Section 1.1 Key Takeaways

BSS manages the commercial lifecycle: catalog, orders, billing, customer relationships
OSS manages the technical lifecycle: service design, activation, resource management, monitoring
The boundary reflects data ownership — BSS owns commercial truth, OSS owns technical truth
Integration happens through order decomposition: Commercial → Service → Resource
TM Forum frameworks (SID, eTOM, ODA) formalise this separation into standards