TM Forum Autonomous Networks
Most autonomy claims are self-assessed, which is why few people believe them. TM Forum publishes a six-level scale, an evaluation methodology and a questionnaire library precisely so the answer can be evidenced. We are a certified evaluator, and we apply it to your network.
TM Forum's published scale, restated. Almost every operator that describes itself as “doing autonomous networks” is somewhere between L1 and L3.
Offline manual implementation; assisted monitoring only.
Manual implementation with online recording of events.
Automation driven by statically configured rules.
Automation driven by dynamically programmable policies; senses real-time change.
AI-assisted decisioning across domains; predictive closed loops; continuous learning.
Self-evolving closed-loop automation across services, domains and lifecycle.
A level belongs to a scenario, not to a network. There is no such thing as an “L4 operator”, and a vendor claiming to make you one has already told you they have not read the framework.
There is no single autonomy score for a network. The assessment takes one operational flow and scores it on the Intent, Awareness, Analysis, Decision and Execution activity chain, following the IG1252 methodology. TM Forum's Autonomous Networks Level 4 solution packages define those flows, and the twelve published so far are below.
| Mobile | Home broadband | Private line | Edge & computing | |
|---|---|---|---|---|
| Service delivery | IG1502A | IG1502G | ||
| Quality assurance | IG1503B | IG1503D | ||
| Complaint handling | IG1504A | |||
| Problem management | IG1505A | IG1505G |
| Main template | RAN | Core | FAN | IP | |
|---|---|---|---|---|---|
| Network planning | IG1521C | ||||
| Fault management | IG1523 | ||||
| Change management | IG1524B | ||||
| Quality optimisation | IG1525E | ||||
| Energy efficiency optimisation | IG1526A |
Published, service-orientedPublished, network-orientedNot published yet
Published packages as at August 2026. TM Forum's matrix covers further scenarios still in development, which are not listed here. IG1502G includes ODA components.
The sequence matters more than the destination. An operator that automates a scenario it cannot yet measure has bought risk, not autonomy.
Pick one operational flow and score it against the framework with the evidence recorded. This gives you a defensible starting number instead of an opinion.
Assessments almost always surface inventory and configuration gaps first. Automating on top of a model that disagrees with the live network is how you industrialise a mistake, so this comes before anything else.
The same automation runs in testing, then human-approve, then autonomous. Autonomy is a dial per scenario, not a switch for the estate.
Nothing is promoted on the strength of its own logs. A change is verified against the model and, where customer experience is what matters, against real devices.
Score the same scenario again so progression is evidenced rather than asserted. This is what a board, and increasingly a regulator, actually asks for.
A structured, auditable assessment for a chosen scenario, delivered as an Evaluator against the published methodology, with a scored result, the recorded evidence and a roadmap to the next level.
The framework is a measuring instrument, not an implementation. These are the parts of the platform that move a scenario up a level, and the transition each one bears on.
Gives automation something true to act on. Most operators discover at this step that the model and the network disagree.
Detects drift against policy and corrects it, moving from static rules toward policy-driven action.
Alarm to diagnosis to action, promoted from testing to human-approve to autonomous as confidence is earned.
Cross-domain decisioning from stated intent, with provenance on every answer and an approval gate wherever the operator wants one.
Independent confirmation that a change improved the customer's experience — the evidence a closed loop needs before it can be trusted to run itself.
These mappings are ours, offered as a way to reason about sequencing. TM Forum scores a scenario against its own questionnaire and evidence; no product, ours included, confers a level.
The last row is the one operators most often skip. Independent confirmation that a change improved the customer's experience is what turns a closed loop from a demonstration into something you would let run unattended.
Worth stating plainly, because this distinction gets blurred in our market. The framework defines two roles: the Evaluator, who runs the assessment, and the Evaluated, whose network is scored. Digitata Networks acts as Evaluator. TM Forum itself does not carry out assessments — it operates a separate validation service that verifies a submitted self-assessment used the tooling correctly and that the evidence matches the scores. That validation confirms process and evidence. It does not confirm that the network physically performs at the assessed level.
So, precisely: we are certified to run the assessment, and we can facilitate submission for TM Forum validation. Neither of those is TM Forum certifying your network, and anyone implying otherwise is selling you something.
One scenario, scored against the framework, with the evidence recorded and a roadmap to the next level. It is the least speculative way to start.