Structure

The ETSI Software Development Group OpenOP is organized into a multitude of modules (Module Development Groups) which are responsible for different technical aspects of the project. These modules report to the Technical Steering Committee (TSC) and are responsible for the overall technical project governance. Ultimately, the TSC reports back to the Leadership Group (LG) which sets the vision for the project.

Module Development Groups (MDG)

The development of the project is split into multiple modules that are detailed below.

Data Lab (DL)

The Data Lab module is led by Vasiliki Parousidou of Intracom Telecom and introduces DataOps capabilities into the OpenOP platform, building on work from the 6G-DALI EU project. It enables data services orchestration, AI pipelines, data analytics exposure and dataspace-based sharing of data and models across federated environments. By leveraging dataspace connectors, Data Lab supports trusted, governed and policy-driven exchange of data, models and related assets — aligned with broader EU data space and AI Factory directions. The module complements the platform’s existing service exposure, orchestration, federation and AI integration layers with a structured approach for making data and analytics capabilities consumable in an interoperable and reusable way across domains and testbeds.

AI Integration Module (AI²)

The AI module is led by Konstantinos Chartsias of Intracom Telecom and provides an AI-native interface to the Open Operator Platform. It enables natural language interaction and AI-driven automation, allowing users and applications to communicate with the platform using conversational commands rather than traditional API calls. AI² simplifies complex platform operations by translating high-level intents into concrete actions across the underlying components.

Federation Manager (FM)

The Federation Manager module is led by Sergio Giménez of i2CAT and handles inter-operator federation. It manages federation agreements between different Open Operator Platform instances and coordinates shared Availability Zones, enabling cross-operator resource sharing. Through the East/Westbound Interface (E/WBI), the Federation Manager allows Application Providers to seamlessly access capabilities and resources across multiple operators without needing to interact with each one individually.

Open Exposure Gateway (OEG)

The Open Exposure Gateway module is led by George Papathanail of Intracom Telecom and serves as the Northbound Interface entry point of the platform. It exposes standardized APIs to Application Providers, giving them access to telecom network and Edge Cloud capabilities — such as deploying application instances on Edge Cloud Availability Zones or configuring Quality on Demand sessions — without requiring knowledge of the underlying operator infrastructure.

Portal (PO)

The Portal module is led by Marinela Mertiri of Intracom Telecom and provides a web-based management interface for the Open Operator Platform. It offers an intuitive graphical environment through which administrators, developers and researchers can monitor, configure and interact with the platform’s components, manage application lifecycles and visualize the state of available resources and services.

Service Resource Manager (SRM)

The Service Resource Manager module is led by Paris Stentoumis of Intracom Telecom and acts as the brains of the platform. It manages the full application lifecycle and translates technology-agnostic requests from the Northbound Interface into technology-specific actions on the Southbound side. The SRM is responsible for orchestrating resources, coordinating with Transformation Functions, and ensuring that application requirements are met across the available infrastructure.

Transformation Function SDK (TF SDK)

The Transformation Function SDK module is led by Konstantinos Togias of Industrial Systems Institute and provides technology-specific adapters that implement the Southbound Interface. These adapters enable the platform to support heterogeneous Edge Cloud and network infrastructure — such as Kubernetes, 3GPP NEF — by translating the platform’s internal operations into the specific protocols and interfaces required by each underlying technology.