OSS/BSS

OSS/BSS, in telecommunications, refer to operations support system and business support system. The distinction emphasizes a separation of concerns between maintaining network operations and the business around which that network is built. Communications service providers support a broad range of services and functions with their OSS/BSS. BSS primarily consists of order capture, Customer Relationship Management and Telecommunications billing whereas OSS covers Order Management, Network Inventory Management and Network Operations.

OSS and BSS are the software, processes and data capabilities that allow network owners to operate and monetise communications services. OSS traditionally focuses on network and service operations such as assurance (fault-fix) and fulfilment (service activations), while BSS supports product management, customer engagement and revenue processes. In practice, modern platforms span both domains to enable end-to-end automation across product, service and network lifecycles.

Previously OSS and BSS were more clearly separate entities^[1] but the term OSS/BSS (or occasionally BSS/OSS) has been in use since at least 2000.^[2][3] The interface, for example, between the BSS capturing an order and the OSS fulfilling it could be quite simple.^[4]

Early OSS concepts emerged from the ITU-T Telecommunications Management Network (TMN) architecture, notably Recommendation M.3010, which defined functional, information and physical architectures for managing heterogeneous telecom networks. TMN built upon OSI management principles codified in X.700, which also popularised the FCAPS model of management functions.

From the late 1990s, industry frameworks consolidated OSS/BSS practices. The TM Forum Business Process Framework (eTOM) organised processes for fulfilment, assurance and billing, providing a common language for operators and suppliers, and later informed cloud-era architectures.

Now, with more complicated and differentiated products and services being offered much closer liaison between the two is required, for example processing an order may require information on the services the customer already has, the network they are using, and currently available resources.

The TM Forum Open Digital Architecture (ODA) groups OSS and BSS capabilities into modular software components, organised on a components map and deployed on an ODA “Canvas”. These components provide a neutral way to describe functions that have traditionally been labelled OSS or BSS, improving plug-and-play interoperability through standard Open APIs.

ODA component groups commonly referenced in telecom operations include:

• Engagement Management - customer and partner touch-point functions such as interaction management, marketing communications, and lead and opportunity management
• Party Management - master data, roles and permissions, privacy and problem management for parties such as customers, partners and employees
• Core Commerce Management - commercial lifecycle functions including product catalogue, product configuration, order capture and validation, usage management, payments, and billing sub-components such as bill calculation, bill generation, billing accounts and debt collection
• Production - service and network delivery functions such as service cataloguing, qualification, ordering, inventory and quality management, plus resource-level cataloguing, inventory, configuration and activation, discovery and reconciliation, testing, and workforce and work order management
• Intelligence Management - analytics and policy components used to optimise and automate processes across domains, supporting observability and closed-loop control patterns
• Common and Canvas operators - cross-cutting platform capabilities including identity, document, location and API management that support the components above, and the ODA Canvas runtime that standardises deployment and operations

Mapping to traditional OSS/BSS usage

• Capabilities often described as BSS are concentrated in Engagement Management, Party Management and Core Commerce Management - for example, product catalogue, order capture, charging, billing and customer interactions
• Capabilities often described as OSS are concentrated in Production - for example, service and resource catalogues, inventories, activation, assurance and workforce management
• Intelligence Management and Common components cut across both, providing data, analytics and shared platform services. ODA’s functional architecture explicitly supports refactoring legacy OSS/BSS into these modular components to improve agility and interoperability

Prior to publishing the TM Forum ODA component map, TM Forum utilised The Application Map (TAM), which formed part of the Frameworx model. A Simplified TAM model has been proposed as a more compact OSS/BSS capability map oriented to smaller operators using off-the-shelf systems.

Multiple industry programmes formalise OSS/BSS interoperability and modularity:

• TM Forum Open Digital Architecture (ODA) - A component-based blueprint for cloud-native OSS/BSS, aligned with a catalogue of Open APIs that standardise interactions between components and partners. Conformance programmes certify supplier implementations.
• MEF Lifecycle Service Orchestration (LSO) - A framework and API suite for automating end-to-end service lifecycles across provider domains, covering both business and operational interfaces.
• ONAP (Open Network Automation Platform) - A Linux Foundation project providing policy-driven design, orchestration and automation for physical, virtual and cloud-native network functions, used for service lifecycle management in multi-domain environments.

Contemporary OSS/BSS programmes emphasise cloud-native software, API-first integration, data pipelines, and AI-enabled automation. Operators increasingly adopt observability, closed-loop assurance and AIOps techniques to manage complexity across domains and multi-cloud scale. Recent operator surveys and vendor-neutral analyses highlight cross-domain data integration and automation as priorities for customer experience and operational efficiency.

Generative AI and machine learning are being incorporated into service design, assurance and care workflows within OSS/BSS, augmenting human operations with intent-driven orchestration and copilots, while raising new governance and data quality considerations.

OSS/BSS capabilities align to process frameworks and standards. TMN and OSI management standards define foundational management concepts and interfaces, while TM Forum frameworks structure business processes and component boundaries. MEF LSO and TM Forum Open APIs address inter-provider and intra-stack interoperability, supporting plug-and-play integration across heterogeneous vendor ecosystems.

• Telecommunications Management Network (TMN)
• FCAPS
• Open Digital Architecture
• Lifecycle Service Orchestration
• Open Network Automation Platform

Service providers in this area have even more requirements for an integrated OSS/BSS system.^{[citation needed]} Examples include eCommerce, self-management, real time reporting, and fraud prevention.

• Passionate About OSS - What are OSS BSS ^[5]- extended overview of OSS/BSS history, standards and scope (external explanatory resource)