Autonomous Networks glossary
This glossary defines, in plain words, the terms used in TM Forum autonomous network assessments, from AN Levels and HVS to IAADE, IG1252, ANLET and ANLAV. Each entry links to the page that covers the topic in depth.
The scale
Autonomous Networks (AN)
Networks that can run, repair and optimise themselves with as little human intervention as possible, following the framework set out by TM Forum. The term covers both the technology and the operating model around it. See AN Levels.
AN Levels
The TM Forum scale of autonomy, from L0 (manual operation and maintenance) to L5 (full autonomous network). Each level describes which tasks are still performed by people and which are handed to systems. See AN Levels.
Level 4
The "high autonomous network" level: systems analyse and decide on their own across domains, with predictive closed loops driven by service quality and customer experience. TM Forum set Level 4 in key domains as the industry milestone for 2025. See what Level 4 changes.
AN Journey
The progression of a network towards full autonomy, as TM Forum describes it. It is specific to each operator or vendor and starts from a current baseline level. See AN Levels.
Scenarios
HVS
High Value Scenario: a defined operational use case, such as RAN Fault Management (GB1523A), on which an autonomous network level is assessed. Levels are always stated per HVS, never for a whole network. The scenarios currently available in ANN are listed on the scenarios page.
Sub-scenario
A subdivision of an HVS that groups related tasks. In ANN, each sub-scenario is a tab of the questionnaire, with its own progress and its own gap list.
GB codes
Reference codes from the TM Forum GB document series, used to identify scenarios: GB1523A for RAN Fault Management, GB1526A for RAN Energy Efficiency Optimization. The code stays the same in every language. See the scenarios page.
The method
IAADE
Intent, Awareness, Analysis, Decision, Execution: the five cognitive steps through which every task of a scenario is assessed. The higher the level, the more of these steps are performed by systems rather than people. See the IAADE cycle.
IG1252
The TM Forum Autonomous Network Levels Evaluation Methodology. It sets out how task ratings are combined into a level for a scenario, and it is reserved for TM Forum members. See our IG1252 page and the official TM Forum page.
Lbase
One of the three values in a scenario result, following the IG1252 scoring approach. Lbase is the base level reached by the tasks of the scenario. See our IG1252 page.
Lextra
The additional credit given on top of Lbase for tasks that go beyond the base level, following the IG1252 scoring approach. See our IG1252 page.
Lscenario
The resulting level of a scenario, combining Lbase and Lextra. It is the figure that sums up where the scenario stands. See our IG1252 page.
Not assessed
The status of a task, or of a score, that has no validated answer yet. In ANN it appears as a grey badge, never as zero or failure: a missing answer is not treated as a poor one. While any sub-scenario is incomplete, the overall score stays "Not assessed".
Assessment and validation
ANLET
Autonomous Network Levels Evaluation Tool: the TM Forum scenario-based questionnaires used to state an autonomous network level in a consistent and repeatable way. They are published as spreadsheets in the GB1059 series. See our ANLET page.
ANLAV
AN Level Assessment and Validation: the TM Forum service, launched in June 2025, through which ANLET evaluation data is submitted to the TM Forum for validation. The first Level 4 validation, TDC NET with Ericsson on RAN Energy Efficiency Optimization, was announced on 19 June 2025. See ANLAV readiness.
IG1392
The TM Forum white paper on autonomous network levels assessment and certification. It frames how assessments are run and recognised, and it is reserved for TM Forum members. See the official TM Forum page.
TM Forum-trained evaluator
A professional who has completed the TM Forum AN Levels skill path, including hands-on ANLET training. According to TM Forum, only evaluators who have completed that path can conduct assessments and submit them for ANLAV validation.
Evidence
Declarative evidence
Evidence that states how something is done: an attestation, a documented policy, a procedure. In the ANN evidence coverage rate, declarative evidence alone counts for half. This weighting is a CEVIA method, not a TM Forum rule. See ANLAV readiness.
Technical evidence
Evidence produced by the systems themselves, such as a system export or an execution log. In the ANN evidence coverage rate, technical evidence counts in full, following the same CEVIA method. See ANLAV readiness.
Evidence pack
The set of documents prepared for submission to the TM Forum: scoring report, gap analysis and evidence organised by sub-scenario and task. In ANN it is exported as a single archive, with the coverage and checklist status. See ANLAV readiness.
Coverage threshold
The minimum evidence coverage rate a team sets before considering an ANLAV submission. In ANN it is set at 80% by default, can be changed by anyone with write access, and is one of the items of the compliance checklist.
Roadmap indicators
KBI
The business impact indicator: the effect of autonomy on costs, incidents or revenue. In ANN it is shown as "Not measured", because it needs client-specific data that cannot be inferred from the questionnaire.
KEI
The indicator that tracks the Zero Wait, Zero Touch and Zero Trouble goals of the TM Forum vision. In ANN the three values are computed from the answers: Awareness for Zero Wait, Execution for Zero Touch, and Analysis and Decision for Zero Trouble.
KCI
The capability index: the share of tasks already at or above their target level. In ANN it is recalculated from the current answers each time it is displayed.