Engineering
They fail at integration — which is where we work. The specifications exist. The hard part is that a disaggregated network has to be integrated, tested, certified and then operated across suppliers who have never had to interoperate, and kept working as each of them ships software on its own schedule.
O-RAN engineering
RU / DU / CU split behaviour, Open Fronthaul over eCPRI at Split 7.2x, and the O1 management surface. We read these interfaces; we never write to them.
RU/DU/CU · Open Fronthaul · O1Test cases, reference configurations and integration playbooks for multi-vendor combinations. This is the work that decides whether an open estate can actually be operated at all.
Test design · reference configs · playbooksHow management and orchestration layers consume normalized data, and what a diagnostic layer has to expose to be useful to them rather than duplicative of them.
SMO · Non-RT RIC · policy surfacesPTP (IEEE 1588) lock, holdover and offset behaviour at the fronthaul, and its correlation with throughput degradation — one of the least-served areas in a mixed estate.
IEEE 1588 · SyncE · holdover analysisEquipment
Radio access and adjacent network equipment, specified against published interface definitions rather than one vendor's implementation — then built, configured, verified and shipped by the same technical team that wrote the spec.
Requirement definition and technical specification written against 3GPP and O-RAN interface definitions.
Assembly, firmware loading and parameter configuration using our own reference configurations.
Functional and interoperability verification before shipment, against the configuration it is sold into.
Kitting, labelling and documentation, so what arrives on site is ready to install, not ready to debug.
Receipt, staging, dock handling and outbound distribution — capability the company already operates.
Radio units and adjacent access hardware, specified for the band plan, split architecture and fronthaul budget of the deployment it is going into.
Fronthaul and backhaul elements, timing distribution and the sync chain that a Split 7.2x deployment lives or dies on.
Server and edge platforms for DU/CU hosting and O-Cloud footprints, sized against the workload rather than a catalogue.
Advisory
A defined engagement against one specific fault or degradation, run on exported performance data. No integration, no network access. This is how most customer relationships begin.
Remote and on-site support bringing multi-vendor equipment into service, working from reference configurations we maintain rather than improvising per site.
Independent before-and-after measurement of a software upgrade, a parameter campaign, or a supplier's performance claim. The party making the claim cannot credibly be the party measuring it.
Technology-roadmap work for operators and equipment suppliers moving toward open, disaggregated networks — including where not to disaggregate.
Continuous access to the diagnostics platform, priced on cells under management rather than on seats.
Who we work with
Multi-vendor estates with small internal tooling teams — the primary market for equipment supply and diagnostics alike.
Enterprise, campus and venue deployments, where equipment supply and integration support are typically bought together.
QA and integration organisations that need vendor-neutral verification before a release reaches the field.
Delivery partners on multi-vendor builds who need reference configurations and interoperability evidence they did not have to generate themselves.
Standards, data handling and neutrality
These are not policies that can be relaxed for a single customer. They are properties of how the systems are built.
Engineering work follows 3GPP and O-RAN ALLIANCE specifications. Reference configurations are stated against published interface definitions rather than one vendor's implementation, so a customer can check our work against the standard rather than against our word.
Read-only access to data the operator already exports. No inbound connection to the network, no write path anywhere in the codebase, and no subscriber identifiers ingested in the current release.
Least-privilege read credentials scoped to the export directory, encryption in transit and at rest, per-customer separation, and a full audit log of access and export.
We do not act as a channel for the RAN vendors whose equipment our reports assess. That independence is precisely what makes a verification report usable in a supplier conversation.
Engineering engagement
Scoped investigations start from exported data and finish with an evidence pack you can take to your supplier.