Home/Traditional & Open RAN
Our approach

From RAN Automation
to SMO Orchestration

Unison was not designed in a specification document. It was built in production environments, solving real operator problems and has evolved from deep RAN automation tooling into a full SMO platform as the industry moved from traditional proprietary RAN to Open RAN. That history is its most important asset.

See the platform Explore all products
Our approach

Built for operational reality

The O-RAN Alliance specification describes how a next-generation RAN management architecture should work in principle. In practice, the operators running the world's largest networks still have 70–80% of their RAN on traditional Nokia, Ericsson, and Huawei infrastructure and they need a platform that works today, not one that works when the spec is fully implemented.

Unison addresses both realities. Elements of the O-RAN specification are implemented where they deliver value, particularly around the Non-RT RIC framework, rApp-based automation, and open PM interfaces. Where the specification does not yet map to what operators actually need, we solve the problem directly rather than waiting for the standard to catch up.

Traditional RAN, day one value
For Nokia, Ericsson, Huawei, and ZTE environments, Unison delivers CM governance, C-SON optimisation, PM analytics, fault management, and zero-touch deployment, through direct OSS integration, no O-RAN interfaces required. This is where Unison has operated in production for over a decade.
Open RAN, practical adoption
For Samsung, Mavenir, and Parallel Wireless environments, Unison extends the same automation and orchestration capabilities through O-RAN interfaces where available. As operator networks transition, Unison transitions with them, without requiring a platform change.
Mixed estates, the real world
Most operators run a mixed estate and will do so for the foreseeable future. Unison is designed for this reality, a single platform with a single data model across Nokia, Ericsson, Huawei, Samsung, and Mavenir, regardless of which interfaces each vendor exposes.
Evolution

Ten years of operator experience, built in

The automation capabilities in Unison today exist because WIM Technologies built them in production, not because a specification said they should exist. That means every capability has been validated in live operator environments before it reaches the next deployment.

2014, RAN automation roots
WIM Technologies founded. Initial focus on configuration management and automated discrepancy resolution for traditional multi-vendor RAN, Nokia, Ericsson, Huawei. The problem being solved: operators managing hundreds of thousands of parameters across three vendor OSS environments manually.
2016–2019, C-SON and closed-loop automation
Expansion into centralised SON applications, ANM, AIM, ALB, AES, and others, running closed-loop optimisation across the same vendor estates. Deployed at Vodafone UK. The platform begins to look less like a toolset and more like an orchestration layer.
2020–2022, SMO framework and Open RAN
As the O-RAN Alliance specifications matured, Unison adopted the SMO framework structure, Non-RT RIC, rApp lifecycle management, and open PM interfaces, building on an existing automation capability rather than starting from a blank specification. Samsung and Mavenir support added.
2023–2024, AI and Tier 1 expansion
Unison AI launched as a conversational intelligence layer across live network data. The platform now covers the full RAN lifecycle, deployment, configuration, performance, fault management, optimisation, and AI, for both Traditional and Open RAN environments.
2025–2026, European and North American operator joint SMO RFP invitation
Participating in one of the most significant SMO and Non-RT RIC procurements in operator history. The platform being evaluated today is the same one that has been running in production for over a decade.
Where O-RAN specifications apply

Specification where it delivers value, pragmatism where it doesn't

Unison draws on the O-RAN Alliance architecture in areas where the specification addresses real operational needs. These are not marketing claims, they are capabilities deployed in production environments where operators have chosen to use open interfaces.

Non-RT RIC
rApp framework and lifecycle management
The Non-RT RIC framework, rApp onboarding, execution, conflict detection, and termination, is implemented based on O-RAN Alliance specifications. This is where the spec maps directly to a problem operators actually have: managing multiple automation applications with potentially conflicting objectives.
PM
O-RAN PM interface support
For Open RAN nodes where file-based or streaming PM interfaces are available, Unison ingests data through those interfaces. For traditional vendor OSS environments, Unison uses direct OSS integration, because that is what works and what operators have.
Cloud
Cloud-native and containerised deployment
Unison is Kubernetes-native and Helm-packaged, deployable on GCP GKE, Azure AKS, OpenStack, and OpenShift. This aligns with O2 interface concepts where operators run cloud-native infrastructure, and is validated in the Bell Canada GCP deployment.
Policy
A1 policy management
Where near-RT RIC environments exist in operator networks, Unison supports A1 policy delivery from the Non-RT RIC. In environments where they do not yet exist, Unison's own automation layer delivers equivalent policy enforcement directly through OSS interfaces.
Get started

A platform built around operator outcomes.

Unison is not the cheapest option, and it is not the most expensive. It is the platform that has been tested at Tier 1 scale across Traditional and Open RAN environments, by operators with genuine accountability for network performance.

See it in action View customer outcomes
Request a demo