Vendor Comparison at a Glance
High-level comparison of 10 major BSS/OSS vendors: suite heritage, tier classification, functional coverage (CRM, CPQ, catalogs, COM, SOM, ROM), key customers, and strengths vs weaknesses.
This section provides a single high-level comparison of the ten major BSS/OSS suite vendors you are most likely to encounter in a telco transformation programme — covering heritage, market tier, functional coverage, and key customers in one consolidated view.
Vendor Overview
The table below consolidates heritage, tier classification, and functional scope into a single reference. Tier 1 vendors typically serve 100+ operators with >$500M annual BSS/OSS revenue. Tier 2 vendors serve smaller segments or specific functional niches — tier reflects scale and breadth, not quality.
Consolidated Vendor Overview
| Vendor | Tier | Coverage | Geography |
|---|---|---|---|
| Amdocs | T1 | Full BSS+OSS incl. BPMN | Global |
| Ericsson | T1 | Full OSS + Charging. No CRM/CPQ | Global |
| Netcracker | T1 | Full BSS+OSS | Americas, Japan, ME |
| Comarch | T2 | Full BSS+OSS. No BPMN | Europe, Middle East |
| CSG | T2 | Billing, COM, SOM. No ROM | N. America, APAC |
| Hansen | T2 | Catalog, COM, SOM, BPMN. No ROM | APAC, Europe |
| Cerillion | T2 | CRM, Catalog, COM, SOM. No ROM | ME, Europe, Caribbean |
| Qvantel | T2 | CRM, Catalog, COM, SOM, BPMN. No ROM | Nordics, Europe |
Key Customer Relationships
Vendor–operator relationships often shape product roadmaps. Understanding flagship deployments helps explain vendor strengths and strategic direction.
Major Customer Relationships
| Vendor | Anchor / Flagship Customers | Typical Customer Profile |
|---|---|---|
| Amdocs | AT&T, T-Mobile US, Vodafone Group, Bell Canada, TELUS, Three UK | Tier 1 operators, particularly North American and European groups |
| Ericsson | Telia Company, Swisscom, Telefónica, Turkcell, du (UAE) | Operators with Ericsson RAN — BSS/OSS cross-sold with network contracts |
| Netcracker | Rakuten Mobile (greenfield flagship), Liberty Global, Altice, Zain Group, KDDI | Mix of greenfield and large incumbent operators |
| Comarch | Orange (multiple OpCos), T-Mobile Poland, KPN, Play | European Tier 1–2 operators where cost-effectiveness matters |
| Hansen | BT (catalog), Orange (catalog), Telia (CPQ), Spark NZ | Large operators buying catalog/CPQ alongside another vendor's CRM/billing |
| Cerillion | Batelco, Omantel, Jersey Telecom, FarEasTone, Sure Group | Mid-market, island/regional operators wanting SaaS delivery |
| Qvantel | Elisa, DNA (Telenor), Virgin Media O2 (MVNO platform) | MVNOs, sub-brands, greenfield digital-first launches |
BPMN 2.0 Support by Vendor
BPMN 2.0 is now the dominant standard for defining executable orchestration workflows in SOM and ROM. However, not every vendor uses BPMN natively — some use proprietary workflow engines or state-machine-based orchestration instead. This matters because BPMN adoption affects portability, tooling choices, and the skills required from your delivery team.
BPMN 2.0 Orchestration Support
| Vendor | BPMN 2.0 Support | Notes |
|---|---|---|
| Amdocs | Yes | Uses BPMN-based orchestration in its SOM/fulfilment layer. Workflow definitions are executable BPMN 2.0 models. |
| Ericsson | Yes | BPMN 2.0 orchestration in the Ericsson Orchestrator (SOM/ROM). Leverages standard BPMN tooling. |
| Netcracker | Embedded engine | Vendor-embedded workflow engine with proprietary extensions. Supports BPMN-style modelling but not pure BPMN 2.0 portability. |
| Comarch | No | Uses a proprietary workflow engine for orchestration. Workflow definitions are not BPMN 2.0 models — they are vendor-specific configurations within the Comarch OSS stack. |
| Hansen | Yes | BPMN 2.0 support in catalog-driven order orchestration workflows. |
| Cerillion | Yes | BPMN 2.0 process definitions used in order management and fulfilment workflows. |
| Qvantel | Yes | Cloud-native stack uses BPMN 2.0 for order orchestration flows. |
| CSG | Partial | Workflow orchestration available but primarily through proprietary configuration rather than standard BPMN 2.0. |
Choosing a Vendor
No single vendor wins on every dimension. The right choice depends on operator profile, budget, geography, and which capabilities you need as own-IP versus partner-integrated.
- Full-stack, single vendor → Netcracker or Comarch (genuine BSS+OSS own-IP). Amdocs for BSS breadth, but expect a separate OSS vendor.
- Ericsson RAN alignment → Ericsson BSS for charging/catalog/SOM, paired with a partner CRM and potentially Hansen for CPQ.
- Fast SaaS deployment → Cerillion. Strong TMF conformance, months not years.
- MVNO or greenfield brand → Qvantel. Cloud-native, no legacy, fast to launch.
- Best-of-breed catalog/CPQ → Hansen, integrated into your existing CRM/billing stack.
- Service orchestration / OSS → Ericsson or Netcracker for integrated OSS orchestration.
Vendor Comparison Takeaways
- Only Netcracker and Comarch offer genuine full-stack BSS + OSS as own-IP. Every other vendor has gaps requiring partner integration.
- Tier 1 vendors (Amdocs, Ericsson, Netcracker) bring scale but also higher cost, longer timelines, and lock-in risk.
- Suite age does not equal quality — Qvantel (youngest) and Amdocs (oldest) can both be the right choice depending on context.
- Vendor–operator relationships (Ericsson↔Telia, Amdocs↔AT&T, Netcracker↔Rakuten) heavily influence roadmaps — check if your needs align.