The Network eAcademy team initially focused on identifying a service architecture that could allow the creation of new services and workflows and that could be shared within the community in a multi-domain fashion with a corresponding orchestration process, in order to use it as a blueprint for a common framework.

In order to select suitable architecture candidates that could fit the community needs, and investigation on available architectures that aimed to solve all or some of the aspects of OAV was performed and commonalities in terms of module functionalities, APIs and data models were identified. This work was followed by a cross comparison with existing proprietary solutions in the community that could lead to harmonisation in the multi-domain environment. The initial list of analysed architectures, together with the links to their respective websites can be find below.

The work ended up with the selection of the TM Forum Open Digital Architecture (ODA, (link to the “ODA - Open Digital Architecture (TM Forum)” section)) as the functional architecture to be used as blueprint where other architectures are being mapped (link to the “Mapping Use Cases” section).