Greenfield BSS/OSS for B2B data communications after the TDC Denmark merger
Delivering a greenfield BSS/OSS transformation for B2B data communications, implementing Ericsson/Cisco-based target stacks across Norway and Sweden.
- Ericsson
- Cisco
- Greenfield BSS/OSS
- B2B data communications
Context
What was happening?
The merger with TDC Denmark brought together B2B data communications businesses with separate systems, product sets and operating practices. Rather than extend either legacy estate, the decision was to build a greenfield BSS/OSS target stack for B2B data communications.
Challenge
What problem needed solving?
Stand up a new BSS/OSS stack for enterprise data communications across two countries, on Ericsson and Cisco platforms, while existing customers continued to be served and the merged organisation was still forming.
- Two national businesses, Norway and Sweden, with their own networks and legacy systems.
- B2B connectivity products — multi-site, contract-specific and long-lived — that consumer-shaped stacks handle badly.
- A greenfield build with no option to inherit undocumented behaviour from the legacy systems.
Architecture
What was the architectural approach?
A greenfield, Ericsson/Cisco-based BSS/OSS target stack, deployed as a common architecture across Norway and Sweden with country-specific content and network integration rather than two separate builds.
- 01Target stack
Ericsson/Cisco-based BSS/OSS components — greenfield, not extended legacy
- 02Common architecture
One design for B2B data communications
- 03Country deployment
Norway and Sweden — local content and network integration
My role
What I actually did
Delivery of the greenfield BSS/OSS transformation for B2B data communications — the target stacks across Norway and Sweden, on Ericsson and Cisco platforms.
Transformation
What changed?
The merged B2B data communications business gained a single target architecture instead of two inherited estates. Greenfield forced the product, service and resource models to be made explicit from the start rather than reverse-engineered from legacy behaviour.
Outcome
What was achieved?
Ericsson/Cisco-based BSS/OSS target stacks for B2B data communications in Norway and Sweden. Commercial and migration metrics are not published here.
What I learned
The broader architectural insight
- B2B connectivity needs a model built for multi-site, long-lived services, not an adapted consumer stack.
- One architecture across countries works when the differences are pushed into content and adapters.
- Post-merger transformation is an organisational design problem wearing a systems programme.
Related thinking
Why B2B connectivity is different from B2C
B2C architecture optimises for volume and uniformity. B2B connectivity is multi-site, multi-party, contract-specific and long-lived — and architectures built for one rarely serve the other.
Why catalog-driven architecture matters
The catalog is where an operator's knowledge of how products become services should live. When it lives in orchestration code instead, every launch is a project.
Product-by-product migration vs big bang
Neither approach is right in general. The choice depends on estate size, product coupling, legacy risk and whether the organisation can govern a long coexistence.