Journey Towards Autonomous Network Operations with AI/ML and Dark NOC
bt · Telecommunications · year n/a · source Agentic: yes · promotional bias: med · source-backed · extracted with prompt 0.5.6 (schema v2)
Generated from extraction.json — do not edit by hand. Every claim cites verbatim source evidence; stated means the quote directly asserts the claim, implied means it supports it indirectly.
Problem
Domain: Telecommunications network operations and autonomous NOC transformation
BT wants to modernize mobile network operations from siloed, manual monitoring toward a DarkKnock vision where networks self-heal, self-optimize, and use AI/ML to analyze data, detect anomalies, perform root cause analysis, and predict failures. The immediate problem is not model choice but the scale, fragmentation, and quality of network data and the organizational shift from network engineering to software-driven operations.
Constraints:
- BT operates one of the largest mobile networks in the UK
- the network includes thousands of radio sites, thousands of gateways, a huge IP network, distributed core, and distributed IMS
- network elements produce petabytes of data
- current operations rely on basic SNMP, syslogs, siloed expertise, and many bespoke tools
- data needs cleaning, access, architecture, topology, and governance before prediction
- domain expertise across radio, core, transmission, IMS, and devices must be represented in data and models
- humans still need to diagnose design issues and failure causes even if machines keep service running
- the DarkKnock goal is explicitly a vision and continuous improvement journey, not a finished deployment
Architecture
BT's approach with AWS starts by fixing network data: cleaning petabytes of element-manager output, creating sensible data architecture, opening access across silos, building a network/knowledge graph, and turning data into governed data products. On top of that foundation, BT plans an AI continuum where traditional ML and generative AI work together in an agentic AI framework. Target use cases include automated data analysis, root cause analysis, service impact analysis, anomaly detection, predictive maintenance, radio network optimization, and eventually application-aware networking. Machines may make immediate continuity decisions while humans investigate deeper design or failure causes.
Diagram confidence: reconstructed (reconstructed from prose).
flowchart LR Network_element_data_sources["Network element data sources"] --> Network_management_services["Network management services"] Network_management_services --> Bespoke_monitoring_tools["Bespoke monitoring tools"] Network_element_data_sources --> Data_cleaning_architecture["Data cleaning architecture"] Data_cleaning_architecture --> Knowledge_graph_topology["Knowledge graph topology"] Knowledge_graph_topology --> Governed_data_products["Governed data products"] Governed_data_products --> AI_continuum_models["AI continuum models"] AI_continuum_models --> Agentic_AI_framework["Agentic AI framework"] Bespoke_monitoring_tools --> Unified_monitoring_intelligence["Unified monitoring intelligence"] Agentic_AI_framework --> Unified_monitoring_intelligence Agentic_AI_framework --> Machine_continuity_decisions["Machine continuity decisions"] Machine_continuity_decisions --> Containerized_network["Containerized network"] Machine_continuity_decisions --> Human_network_experts["Human network experts"] Unified_monitoring_intelligence --> Human_network_experts Agentic_AI_framework --> Application_aware_networking["Application-aware networking"]
Components
| Component | Role | Interacts with |
|---|---|---|
Network element data sources |
Radio sites, gateways, IP network, distributed core, IMS, and element managers producing operational data. | Network management services, Data cleaning architecture |
Network management services |
Existing monitoring layer receiving element-manager data and supporting SNMP/syslog workflows. | Network element data sources, Bespoke monitoring tools |
Bespoke monitoring tools |
Hundreds of function-specific tools that BT wants to consolidate into broader intelligence. | Network management services, Unified monitoring intelligence |
Data cleaning architecture |
Foundational phase that cleans network data and makes it usable before prediction or AI/ML. | Network element data sources, Knowledge graph topology |
Knowledge graph topology |
Network graph/topology/discovery layer that connects previously siloed network data. | Data cleaning architecture, Governed data products, AI continuum models |
Governed data products |
Shared data assets governed across the organization instead of replicated across units. | Knowledge graph topology, AI continuum models |
AI continuum models |
Traditional ML and generative AI models selected by task and orchestrated together. | Governed data products, Agentic AI framework |
Agentic AI framework |
Coordinates ML and GenAI capabilities for RCA, service-impact analysis, anomaly detection, prediction, and automated analysis. | AI continuum models, Unified monitoring intelligence, Machine continuity decisions |
Unified monitoring intelligence |
Planned larger monitoring system that consolidates tool output and automates network data analysis. | Bespoke monitoring tools, Agentic AI framework, Human network experts |
Machine continuity decisions |
Automated decision path intended to keep service running, such as traffic movement away from faulty nodes. | Agentic AI framework, Containerized network, Human network experts |
Containerized network |
Modern network substrate where traffic can be shifted from faulty nodes to working nodes. | Machine continuity decisions |
Human network experts |
Radio, core, transmission, IMS, device, and software-skilled engineers who investigate failures, design issues, and process automation. | Unified monitoring intelligence, Machine continuity decisions |
Application-aware networking |
Future vision where the network adjusts itself for the applications customers use. | Agentic AI framework, Machine continuity decisions |
Data flow
Network elements push data into network management services, where BT currently monitors with SNMP and syslog expertise across silos. The modernization path cleans and structures that data, opens access across disparate systems, builds topology/knowledge graphs and data products, then runs ML and GenAI models in an agentic AI framework. The framework supports analysis, RCA, service-impact analysis, anomaly detection, predictive maintenance, and optimization. For continuity events, machines are intended to keep the network running while humans investigate why the failure happened.
4 supporting quotes
Why this architecture
BT is deliberately sequencing data foundations before autonomy because the network is too large, siloed, and domain-specific for AI to succeed on dirty or inaccessible data. The architecture uses knowledge graphs and governed data products to make operational data usable, then applies the right AI tool for each task: rules for simple event decisions, ML for prediction/classification, and GenAI for more complex reasoning. Human experts remain responsible for deeper diagnosis and design judgments.
4 supporting quotes
Models used: traditional ML models · generative AI models · agentic AI framework · AI continuum · knowledge graph · predictive analysis models
Scale
- BT describes its mobile network as one of the largest in the UK.“we have one of the largest networks in UK and we have thousands of radio sites”transcript, stated
- The network includes thousands of radio sites.“we have one of the largest networks in UK and we have thousands of radio sites”transcript, stated
- The network includes thousands of gateways.“we have thousands of gateways, a huge IP network, massive distributed core network, massive distributed IMS network.”transcript, stated
- The data volume is described as petabytes and petabytes.“take the data that comes out of network in petabytes and petabytes and try to clean that data and make sense out of that data that comes out.”transcript, stated
- The current tool landscape includes hundreds and hundreds of bespoke function-specific tools.“move away from having hundreds and hundreds of tools that are very bespoke for a function”transcript, stated
- The speaker frames the roadmap in terms of the next two years.“from the perspective of the next two years that you see, how do you see your journey towards this dark knock vision that you have?”transcript, stated
Alternatives considered (roads not taken)
Apply AI before fixing network data
Rejected because: BT says data cleaning and architecture must happen before prediction or AI/ML.
Keep many function-specific monitoring tools
Rejected because: BT wants a larger intelligence system that consolidates tools and automates analysis.
Use generative AI as the universal solution
Rejected because: AWS frames the system as an AI continuum where ML and GenAI are selected for the right job.
Fully replace human operators with machines
Rejected because: The described division is machines keeping service going while humans analyze why failures occurred.
Patterns
data-quality-loop (data)
BT treats data cleaning, architecture, access, data products, and governance as the prerequisite for any AI/ML or autonomous operations work.
model-routing (architecture)
The AI continuum chooses between traditional ML, GenAI, and simpler rules based on the job rather than forcing one model family onto every network problem.
tool-use-orchestration (operations)
The target system consolidates many bespoke network tools, topology/discovery services, data products, analytics, ML, and GenAI into a unified operations intelligence layer.
observability-tracing (operations)
The transformation is built around making network telemetry, syslogs, topology, anomalies, and service-impact signals accessible for automated analysis.
human-in-the-loop-gate (governance)
The autonomous-operations vision still assigns humans to investigate failures and design issues after machines act to preserve service continuity.
Tradeoffs
Start with data foundations before autonomous AI.
Chose data cleaning, architecture, graph, governance, and upskilling over jumping directly to predictive or GenAI automation.
Rationale: BT says prediction and AI come after the data is cleaned and made sensible.
Consolidate monitoring intelligence instead of maintaining specialized tool silos.
Chose a broader network monitoring/intelligence system over hundreds of bespoke function-specific tools.
Rationale: Consolidation should make data analysis more automated and reduce tool demand.
Use a mix of rules, ML, and GenAI.
Chose AI continuum with the right tool for the job over forcing every event into a generative AI workflow.
Rationale: Some event decisions can be simple rules, some are better ML predictions, and some may benefit from GenAI reasoning.
Let machines handle immediate continuity while humans diagnose root causes.
Chose machine action for keeping the network running plus human investigation over fully autonomous diagnosis and remediation with no expert follow-up.
Rationale: BT wants machines to protect service availability, but humans still need to understand whether failures reflect design issues or other root causes.
Gotchas (what bit them)
AI automation cannot compensate for dirty or inaccessible network data.
Root cause: The network produces petabytes of data across element managers, silos, and management systems, but it must be cleaned and structured first.
Resolution: BT and AWS start with data cleaning, sensible architecture, topology, discovery, and knowledge graphs before prediction.
Domain expertise has to be translated into data and models.
Root cause: Network problems span radio, core, transmission, IMS, and devices, and expert reasoning is distributed across specialized teams.
Resolution: BT plans upskilling plus data/model representations that encode domain knowledge for automated decisions.
Tool sprawl prevents holistic root-cause analysis.
Root cause: Hundreds of bespoke tools observe functions or modules independently, making cross-domain correlation hard.
Resolution: BT wants a bigger monitoring/intelligence system that consolidates tools and automates data analysis.
Autonomy is a journey, not a one-time system launch.
Root cause: DarkKnock requires data foundations, upskilling, process cleanup, AI/ML, prediction, and ongoing optimization.
Resolution: The speaker frames DarkKnock as a vision and continuous improvement program with foundations currently being built.
Predictive maintenance must serve both service continuity and security.
Root cause: Network anomalies may be operational failures or security events such as unexpected container access.
Resolution: BT includes anomaly detection and predictive analysis in the DarkKnock roadmap.
Evaluation
The transcript does not describe a deployed evaluation harness or production metrics for the DarkKnock system. The evaluation stance is roadmap-oriented: first build data foundations and upskill teams, then use analytics, RCA, service-impact analysis, anomaly detection, predictive maintenance, and optimization to measure operational value. Success is framed around service continuity, lower operations cost, better monetization, and more automated data analysis.
Metrics: data cleanliness and accessibility · network graph/topology completeness · automated data analysis coverage · root cause analysis support · service impact analysis support · anomaly detection · predictive maintenance · cost of operations · continuous service availability · radio network optimization
4 supporting quotes
Outcomes
- BT has started the journey with AWS by focusing on data cleaning, architecture, knowledge graphs, and foundations.
- The speakers describe DarkKnock as a vision and continuous improvement program rather than a completed autonomous NOC.
- The target use cases include automated data analysis, RCA, service impact analysis, anomaly detection, predictive maintenance, cost reduction, and radio network optimization.
- BT is upskilling network teams toward software-driven operations.
- The future vision includes application-aware networking where the network adjusts itself for applications.
BT describes one of the largest UK mobile networks, with thousands of radio sites, thousands of gateways, a huge IP network, massive distributed core and IMS networks, petabytes of network data, hundreds of bespoke tools, and a next-two-years roadmap focused on data foundations and upskilling before deeper AI/ML automation.