BSS/OSS Transformation Simulator
Describe your current landscape, key challenges, and transformation goals. The simulator assesses your scenario against established migration patterns and provides a recommended strategy, including risks, roadmap, governance checkpoints, and vendor considerations.
Quick-start presets
Scale & Network Segment
Current State
High
Heavy legacy — deeply entangled systems, undocumented integrations, custom middleware, and years of accumulated technical debt.
Medium
Moderate legacy — multiple systems with some point-to-point integrations, partial documentation, and known workarounds.
Low
Minimal legacy — few systems, clean integrations, or a relatively new stack with limited technical debt.
None
No centralised product or service catalog. Products are defined in CRM, billing, or spreadsheets with no structured decomposition.
Partial
A product catalog exists but is incomplete — may cover commercial products without CFS/RFS decomposition, or only some product families.
Mature
A structured, centralised catalog drives product definition with clear CFS/RFS decomposition and is consumed by downstream systems.
Manual
Orders are fulfilled manually — staff use multiple systems, email, and spreadsheets to provision services on the network.
Semi-Auto
Some automation exists (e.g. scripts, basic workflows) but manual intervention is still required for most order types.
Orchestrated
A service orchestrator (SOM/ROM) drives automated fulfilment end-to-end — orders decompose and execute with minimal human touch.
Fragmented
No single view of active services. Inventory data is spread across billing, CRM, network EMS, and spreadsheets with frequent discrepancies.
Partial
A service inventory exists but does not cover all products or network layers. Some data gaps and reconciliation issues remain.
Strong
A reliable service and resource inventory provides an accurate, real-time view of what each customer has and how it maps to the network.
Loose
BSS and network/OSS systems are largely independent. Provisioning uses standard APIs or simple interfaces with minimal vendor lock-in.
Moderate
Some direct dependencies between BSS processes and specific network platforms. Changes to one side require coordination with the other.
Tight
BSS processes are deeply coupled to specific network/OSS platforms — custom integrations, vendor-specific protocols, and hardcoded provisioning logic.
Very Bad
Billing, service, and network truth frequently diverge. No reliable single source of truth — migration confidence is low without major data cleansing.
Bad
Regular discrepancies between what billing thinks a customer has, what service inventory records, and what is actually provisioned on the network.
Good
Billing, service inventory, and network records are broadly consistent. Data reconciliation issues are rare and manageable.
No
No TMF alignment. Products use flat codes, not CFS/RFS decomposition. Architecture does not follow SID, eTOM, or ODA principles.
Partial
Some TMF concepts adopted — e.g. a product catalog with TMF620, or partial SID alignment — but not consistently applied across the stack.
Yes
Architecture follows TM Forum principles. Product/service models use CFS/RFS decomposition, APIs follow TMF Open API specs, and ODA domains are recognised.
Organisation & Appetite
1
Single business unit — one brand, one product portfolio, one set of processes.
2-3
Multiple business units — e.g. consumer and enterprise, or fixed and mobile divisions with separate product lines.
4+
Large multi-BU operator — consumer, enterprise, wholesale, and potentially international divisions with independent stacks.
Unified
Common products, processes, and workflows across all BUs in the target state. Requires product harmonisation and process convergence — higher upfront effort but eliminates duplication.
Federated
Shared platform and infrastructure but BU-specific products, commercial offers, and workflows. Each BU retains autonomy within a common technical foundation.
Independent
Each BU operates its own target stack independently. No product or process convergence — fastest per-BU delivery but no cross-BU synergies or cost sharing.
Simple
A small, well-defined product portfolio with clear boundaries. Few bundles, minimal cross-product dependencies.
Moderate
A reasonable product range with some bundles, add-ons, and cross-product relationships. Manageable but growing in complexity.
Fragmented
A sprawling product portfolio with legacy products, overlapping offers, inconsistent bundling rules, and products defined differently across systems.
Low
Conservative — prefer proven approaches, phased rollouts, and extensive testing. Willing to accept longer timelines for lower risk.
Medium
Balanced — accept calculated risks with appropriate mitigation. Comfortable with phased delivery but not overly cautious.
High
Aggressive — willing to accept significant risk for faster delivery. Comfortable with big-bang approaches and compressed timelines.
Low
No urgent deadline. Willing to invest in a thorough, well-planned transformation over a longer horizon.
Medium
Reasonable urgency. Need to show value within 12–18 months but not under immediate competitive pressure.
High
Urgent. Competitive pressure, regulatory deadlines, or business imperatives require rapid time-to-first-value.
Pain Points & Scope
BSS Only
Transform commercial systems only — CRM, CPQ, catalog, billing. OSS and fulfilment remain as-is.
OSS Only
Transform operational systems only — SOM, ROM, inventory, activation. Commercial BSS remains as-is.
E2E L2C
End-to-end Lead-to-Cash — from product catalog through order capture, fulfilment, and billing. The most common transformation scope.
L2C + T2R
Lead-to-Cash plus Trouble-to-Resolve — includes assurance, service quality, and incident management alongside the L2C flow.
Transformation Intent (optional — improves accuracy)
To generate results, please select:
an operator preset and at least one network segment