‍

Why did EWE decide to transform its OSS architecture and become TMF-compliant?

I think it's important to understand that we are not seeking certification or full compliance. We try to follow the principles of ODA whenever possible and useful for us. Our focus is primarily on the interfaces and processes between the Production and Core Commerce domain. Within a domain, we then follow a pragmatic approach. In the end, it is a continuous transformation.

The reasons for this transformation are clear to us. The common language and definitions that the TMF provides. Interfaces that are clearly defined and for the first time enablea plug-and-play architecture. And, of course, the overarching concepts such as catalogue-driven products and services.

In the future, we will be able to react even faster to changes in the market and to customer requirements. We will also have a completely different basis for working with suppliers of ODA components.

We are also already seeing a change in the way different CSPs in Germany engage with each other. In the past, there were always very specific solutions for the German market to ensure wholesale/wholebuy processes. Initiatives such as FIT or the Wholesale Broadband Project are positive examples of how the TM Forum can help transforman entire industry.

What were some of the strategic considerations for EWE when selecting Alvatross as your OSS vendor?

Certainly Alvatross' clear commitment to the TM Forum and the principles of the ODA. This helped us a lot during the entire tender process. We always had the feeling that we were speaking a common language with Alvatross.

A further crucial element was the immediate sense of alignment and shared principles and values with our partner Alvatross. By this I mean the way we approach problems and challenges in projects. We have a very agile organization with a clear“hands-on” and “get stuff done” mentality.

‍Spending a year writing specifications and requirements for the vendor before we start the project? Those days are over.

In your opinion, what has been the most impactful aspect of EWE’s partnership with Alvatross so far?

The fact that Alvatross brings a different perspective to the table, in addition to a great deal of experience when it comes to CSP specific know-how. Especially when it comes to processes, we Telcos often tend to implement things the way they have always been done. Alvatross doesn't hold back here and has the courage to question our old habits.

How does the implementation of TM Forum’s ODA-ready solutions supportEWE’s broader goals?

We have been using the TM Forum's Telecoms Application Map (TAM) to further develop our OSS landscape for some time now. However, practice has shown that only a few software vendors have worked with it, which has often made the search for suitable solutions or even just a common understanding of the problem domain more difficult.

In addition, the market often favored comprehensive full-stack solutions that offered a wide range of functions but were often faced with considerable implementation challenges in practice.

For most CSPs, the OSS environments have grown over time and through technological change in the infrastructure. ODA-Ready solutions offer us, for the first time, the opportunity to specifically replace or modernize individual capabilities of our platform or to close blind spots. This is possible thanks to modularization, Open API specifications and clear descriptions of the components.

As a result, we can take a much more targeted approach in our IT projects and don't have to turn everything inside out at the same time.

What advice would you give other telcos considering a similar transitionto ODA-compliant systems?

I recommend first identifying the part of the IT environment that is causing the greatest challenges. The transition should start there and then other components can be gradually brought in.

We have completely abandoned the big bang approach. Instead, small increments that are manageable and made available to the organization at an early stage should be implemented. This allows added value and acceptance by all stakeholders to be created much earlier. Despite all the agile frameworks, the cultural aspects should not be underestimated. Such a transition project must be flanked from day 1 by solid change management, key user groups and change promoters.

‍