Test environments for BSS/OSS transformation
Building and managing the complex test environments behind Telia's BSS/OSS transformation programmes — CRM, CPQ, billing, order provisioning, ITSM and network — including configuration, network zoning, load balancing and data refresh.
- Test environments
- CRM
- CPQ
- Billing
- Order provisioning
- ITSM
- Network zoning
- Load balancing
Context
What was happening?
A BSS/OSS transformation is tested against a copy of the operator: CRM, CPQ, billing, order provisioning, ITSM and the network, wired together the way production is. Those environments are as complex as the systems they mirror, and a programme can only move as fast as they can be built, refreshed and kept coherent.
As Global Test Environment Manager at Telia Norway from 2012 to 2014, that was the job: the environments the transformation projects depended on.
Challenge
What problem needed solving?
Provide test environments that behaved like production across six system domains, kept their data current, and could be configured and refreshed at the pace of several transformation projects at once.
- CRM, CPQ, billing, order provisioning, ITSM and network environments that had to be coordinated as one.
- Network zoning and load balancing that had to match production for the tests to mean anything.
- Data refresh processes that kept environments realistic without leaking or corrupting production data.
- Multiple projects competing for the same environments.
Architecture
What was the architectural approach?
The environments were managed as a product in their own right: a defined configuration for each, explicit network zoning and load balancing that mirrored production, and repeatable data refresh processes — so that a project could ask for an environment in a known state rather than inherit whatever the last project had left.
- 01Configuration
CRM, CPQ, billing, provisioning, ITSM, network — defined per environment
- 02Network zoning & load balancing
Mirroring production topology
- 03Data refresh
Repeatable, controlled, current
- 04Handover
A project receives an environment in a documented state
What I delivered
My role and what I was accountable for
Built and managed the test environments supporting the BSS/OSS transformation projects: coordinating the CRM, CPQ, billing, order provisioning, ITSM and network environments, and managing environment configuration, network zoning, load balancing and data refresh.
Transformation
What changed?
Test environments moved from being a bottleneck each project worked around to a managed capability the programmes could plan against. It was also the ground floor of the BSS/OSS work that followed: understanding how CRM, CPQ, billing, provisioning and the network fit together, by wiring them up.
Outcome
What was achieved?
Test environments across CRM, CPQ, billing, order provisioning, ITSM and network, built and managed for the transformation projects of the period. Throughput and defect figures are not published here.
What I learned
The broader architectural insight
- Treat environments as a product with a defined state, an owner and a refresh cadence.
- The integration points between CRM, CPQ, billing and provisioning are where transformations fail; make the environments exercise them.
- Whoever manages the environments ends up understanding the whole stack — use that.
Related thinking
Legacy modernisation without a big-bang migration
The strangler pattern, applied to BSS/OSS: introduce the target architecture at a boundary, route selectively, migrate in tranches and retire on evidence.
Order decomposition as an architectural boundary
Where a product order becomes service orders, and where service orders become resource orders, are the most important seams in a BSS/OSS architecture. Place them deliberately.