/// TELECOM · OSS/BSSOSS/BSS Development & Integration
The systems that take a telecom service from order to activation to bill — built, connected and modernised one piece at a time, for operators, ISPs and MVNOs.
Message on WhatsApp
TRUSTED BY TEAMS
OSS/BSS is the software that runs a telecom business: business support systems handle customers, products, orders and billing, while operations support systems handle the network, its inventory and the activation of every service.
The trouble in most operators is rarely one system on its own. It is the gaps between them — orders that stall, products defined differently in each system, and staff retyping data from one screen into another. Sodio builds and integrates telecom BSS and OSS for operators, ISPs and MVNOs, and modernises older stacks without an all-at-once replacement.
/// IS CUSTOM RIGHT FOR YOU?
When a Full OSS/BSS Suite Is the Right Answer
Tier-one operators run OSS/BSS suites from vendors such as Amdocs, Ericsson and Netcracker, and newer cloud-native BSS products serve smaller operators. If one covers what you need, use it. Custom work earns its place around, between and in place of the pieces that do not fit.
A suite fits when
- You are replacing everything and can wait for it
- Your products fit the suite's standard model
- You have the budget and team for a large programme
- One vendor for everything suits you
Custom development and integration fit when
- You need to keep some systems and connect the rest
- Your products, bundles or business accounts do not
- You are an ISP, MVNO or regional operator sizing the stack to the business
- You want to avoid being locked into a single vendor
/// THE OSS/BSS STACK
The OSS/BSS Stack, System by System
/// WHAT WE BUILD
What We Build and Integrate
Integration layer
Order orchestration
Product catalogue
Service and resource inventory
Provisioning and activation
Mediation
Field service
Legacy modernisation
Data migration
Automated testing
/// ORDER TO ACTIVATION TO BILL
From Order to Activation to Bill
The customer places an order
CRM and order management. What goes wrong: invalid product combinations accepted
The order is broken into services
Product catalogue. What goes wrong: products defined differently in different systems
Steps are run in order
Order orchestration. What goes wrong: orders stalling between systems
The service is set up
Inventory, activation and field service. What goes wrong: network records that do not match reality
The service is watched
Network monitoring. What goes wrong: faults nobody links to the customer
The customer is charged
Mediation, charging and billing. What goes wrong: services that are live but never billed
/// WHERE STACKS BREAK
Where OSS/BSS Stacks Break
///AI IN OSS/BSS
Where AI Helps OSS/BSS
OSS/BSS work is full of repetitive checking and fixing. AI helps most where it takes that work off people and catches problems earlier.
Orders that fix themselves
Stalled orders diagnosed from their history, with known problems resolved automatically and the rest sent to a person.
Testing every change
Test cases generated for every change to products, prices and integrations, so regressions are caught before release.
Documentation and configuration
Engineers ask questions of specifications and runbooks, and get configuration drafts to review.
Stalled orders diagnosed from their history, with known problems resolved automatically and the rest sent to a person.
Test cases generated for every change to products, prices and integrations, so regressions are caught before release.
Engineers ask questions of specifications and runbooks, and get configuration drafts to review.
/// COMPARE
Full Suite, Cloud-Native BSS or Custom OSS/BSS Transformation
/// COST AND TIMELINE
What Drives the Cost and Timeline
A first integration — typically one order journey running end to end across your existing systems — usually arrives within 30 days, with a production build of the first stage in 90. Larger transformations are delivered stage by stage after that.
The cost moves with six things: how many systems are involved; how complex your products and business orders are; how much legacy data has to move; how closely the work follows TM Forum standards; the testing effort, especially where billing is affected; and order and usage volumes.
/// FAQ
Frequently Asked Questions
OSS/BSS is the collective name for the software that runs a telecom business. Operations support systems (OSS) run the network: inventory, provisioning, activation, monitoring and the collection of usage records. Business support systems (BSS) run the business: customers, products, orders, charging, billing and payments. Together they take a service from the moment it is sold to the moment it is billed.
OSS faces the network and BSS faces the customer. OSS knows what equipment exists, what is configured on it and whether it is working. BSS knows who the customer is, what they bought, what they owe and how they pay. Most problems in a telecom operation happen where the two meet — when an order has to become a working service, or usage has to become a bill.
They are standard interfaces, published by the telecom industry body TM Forum, for common OSS/BSS functions — for example product catalogue management (TMF620), product ordering (TMF622), service ordering (TMF641) and inventory (TMF638 and TMF639). Building on them means systems can be connected and replaced without rewriting every integration.
Rarely. Large, all-at-once BSS replacements have a long record of running over time and budget. It is usually safer to put a standard integration layer in front of the existing systems, then replace them one piece at a time behind it, with customers and orders moving across in stages.
Yes. Most operators keep some of their existing platforms. We connect to them through their APIs, message interfaces or files, fill the gaps between them, and replace only the parts that are holding the operation back.
With automated end-to-end testing across every system a change touches, and parallel running for anything that affects billing. A change to a product or a price can break orders, activation and invoices at once, so each change is tested along the whole path before it reaches customers.
/// RELATED SERVICES
Related Industries and Services
Routes where scope overlaps with OSS/BSS.
/// GET STARTED
Start With the Order That Gets Stuck
Tell us which orders most often need someone to fix them by hand, and which systems they pass through. We will prepare a free solution architecture for connecting them — and a staged plan for modernising the stack behind them.