01 of 07 · Network operations
What supported the move from NOC MVP to production
Three things, from pilot to production.
87%Alarm-noise suppression
42sMedian time to root cause
84%Notes accepted as written
250Historical situations measured
At a Tier-1 Nordic operator, a multi-agent pipeline now turns fault situations on the 4G/5G Packet Core into ranked root causes and a recommended action. The MVP took six months for six use cases, and the operator funded production on the measured results.
01
Flows the NOC can audit
A deterministic four-step flow (retrieve, annotate, recommend, format) instead of an open agent loop. Every output is reproducible, so engineers could check the agent's work. They accepted 84% of its notes as written.
02
Inference inside the tenancy
Public models were ruled out on network-data confidentiality. An open-weight model runs behind a gateway on the operator's own Kubernetes, with the embeddings on persistent storage. Tracing runs end to end, and the operator's identity provider sits at the gateway.
03
A KPI baseline agreed with operations first
Alarm-noise suppression and time to root cause were measured against 250 historical situations before anyone argued about the design. The numbers that came out, 87% suppression and a median of 42 seconds, are the numbers that funded production.