How to turn autonomous network ambition into measurable outcomes

Automation, AI, and cloud-native architectures are gaining strength across communications service providers (CSPs), but a persistent gap remains: translating those capabilities into repeatable, demonstrable business outcomes. We introduced Ericsson Business Value Pathways specifically to close that gap. Each pathway is a structured, end-to-end journey that connects a business or operational intent to a measurable outcome. It describes how an initial objective is translated into intent, situational awareness, analysis, decision, execution, and verification, with continuous feedback from the result.

In TM Forum terms, the intent connects the business, service, and resource domains: business intent is expressed and prioritized; service orchestration decomposes that intent into service actions; resource-domain automation executes and reports back, closing the loop.

This perspective matters because autonomous behavior is not created by a single AI model or a product feature. It emerges when data, analytics, agentic AI, workflows, and governance act together across the complete pathway.

TM Forum’s High Value Scenarios (HVS) provide a common language for measuring this progression. An HVS is a specific operational flow, such as fault management, where autonomy levels advance from Level 0 (manual) to higher levels where the scenario can be executed with minimal (Level 4) or no human intervention (Level 5).

When assessing scenarios, it is important to focus on the maturity of the pathway, not on counting AI features. A pathway may have sophisticated analytics or recommendations and still remain at Level 2 or Level 3 if execution, recovery or verification require significant human intervention.

Figure 1: Different assessment routes for the pathways, one credibility standard

Each Business Value Pathway is aligned to the most relevant TM Forum HVS, providing a common foundation for applying the autonomy lens to business value, as shown in Figure 1:

• Zero-touch product launch: An AI-driven catalog with automation to translate business opportunities into new products and offers faster across channels. The pathway aligns with the Business Innovation – Product Definition HVS where commercial intent is translated into product and offer definition and subsequently into catalog and channel execution. The original assessment applied an approach aligned with the TM Forum Autonomous Network Level Evaluation Tool (ANLET), providing a basis for alignment with the latest Product Definition HVS.
• Agentic AI service experience: Shifts reactive problem-solving to proactive experience management, powered by data, analytics, and AI agents, connected through knowledge. It is assessed against the Service Assurance HVS, specifically where subscriber incidents are predicted, diagnosed, and resolved with far less human intervention.
• Agentic AI intelligent IT operations: Considers how monitoring, anomaly detection, fault diagnosis, recommendation, and recovery verification could form a broader operational-intelligence flow. The pathway is assessed against Fault Management HVS. Because there is no dedicated cloud/IT-focused HVS, we applied an assessment focused on equipment and infrastructure.

As shown in Figure 2, each Business Value Pathway is assessed using TM Forum’s ANLET through the Intent, Awareness, Analysis, Decision and Execution (IAADE) loop. This loop shows how a business or operational objective is translated into actionable intent and progressively carried through awareness, analysis, decision, and execution to a measurable, verified outcome.

Figure 2: TM Forum ANLET IAADE Loop: from objective to verified outcome

The purpose of the assessment is not to defend a score or assume that every pathway should progress to Level 4. It is to identify what is proven to deliver business value, where additional autonomy could strengthen the intended outcome, and which capability improvements are justified by business value, operational need, and risk. That means defining the pathway boundary, examining the IAADE flow, validating the supporting evidence, and translating the findings into a practical maturity roadmap.

This keeps the assessment anchored on the business result while using autonomy levels as a reference for maturity. The assessment establishes what is proven today, identifies capability gaps, and highlights potential improvement areas toward higher autonomy without assuming that every gap must be closed or every pathway must reach Level 4.

What makes Ericsson’s outcome-based approach different?

The differentiator is the outcome commitment. The objective is not to automate every step or to pursue the highest autonomy level for its own sake. A Business Value Pathway starts with the outcome that needs to be achieved and brings together the capabilities required to deliver and verify that result.

The appropriate autonomy level follows from the business need. For some pathways, conditional autonomy with human oversight may be sufficient; for others, greater autonomy may create additional value. The ultimate measure is whether the pathway delivers the intended business, service, or operational outcome.

• Outcome-first: Begin with the measurable business or operational outcome. Technology choices and autonomy ambition follow from what the pathway needs to achieve.
• Pathway-complete: Connect the capabilities, decisions, hand-offs, and dependencies required to deliver the intended outcome across the domains relevant to that pathway.
• Evidence-led: Establish what is demonstrably available today, what still depends on people or manual controls, and which capabilities need to mature next.
• Governed execution: Ensure that decisions can be translated into operational actions within policy, risk, security, and accountability boundaries.
• Incremental and reusable: Build autonomy through modular OSS/BSS capabilities that can be reused across Business Value Pathways, allowing CSPs to progress in manageable steps backed by return on investment (ROI) rather than through a single large transformation.
• Verification and feedback: Confirm that the action produced the intended service, operational or commercial result; recover safely when it did not; and feed the outcome into future decisions.

From Level 3 to 4: execution makes autonomy dependable

Now is the time to build strong foundations for autonomy. Detection, prediction, analysis, root-cause identification, and recommendation can increasingly support autonomous operation within defined scenarios, an important step toward Level 3 conditional autonomy.

Progressing toward Level 4 requires dependable, explainable intelligence and governed execution. The pathway must be able to translate intent into actionable policies, execute decisions within defined guardrails, provide traceability for why actions were selected, recover when actions do not work as intended, verify the resulting outcome, and retain the evidence needed for accountability and continuous adaptation.

These are not simply assessment gaps; they are the capabilities that may become increasingly important where greater autonomy is required to strengthen or protect the intended outcome. In the Agentic AI service experience pathway, greater autonomy may require insights to be translated into service policies and automated remediation with safe recovery. In the Agentic AI intelligent IT operations pathway, value may come from extending autonomous handling to additional fault scenarios while strengthening controlled implementation and recovery. In the Zero-touch product launch pathway, higher autonomy may require reliably translating commercial decisions into catalog, OSS/BSS, and channel execution, supported by consistency checks and post-launch verification.

Figure 3: Progressing toward Level 4, from cognitive intelligence to governed, verified execution

Where additional autonomy is justified by business value and operational need, progression from Level 3 toward Level 4 should be viewed as a progressive journey rather than a single technology milestone. Each pathway can advance through well-defined scenarios, measurable outcomes, and increasing levels of trusted automation. Business Value Pathways provide the structure to identify the next step, prioritize the most valuable improvements and demonstrate progress in business terms.

By combining the Business Value Pathways approach, HVS-based assessment, OSS/BSS expertise, and autonomous networks capabilities, we can help transform existing investments in AI, automation, and orchestration into dependable, outcome-oriented autonomy. The destination is not autonomy for its own sake, but the ability to convert business and operational objectives into verified outcomes with confidence and progressively less human intervention.

Business Value Pathways define the outcome to be achieved; the assessment shows how mature the pathway is today and which capabilities could enable higher autonomy. Business value, ROI, risks, and operational need then determine how far the pathway should progress. Together, they give CSPs a practical way to decide where additional autonomy creates sufficient value to justify further investment.

• Learn how Business Value Pathways deliver measurable business outcomes
• See how Ericsson’s OSS/BSS portfolio promotes faster service launches and smarter operations
• Discover how you can modernize OSS/BSS, drive efficiency, and accelerate growth