Viva Bolivia Taps Totogi Ontology for Revenue-Led Network Planning Across Azure and On-Premises

For enterprise IT readers, the interesting part is not another AI label. It is the attempt to give systems in different environments a consistent understanding of the business. The selection is confirmed; a spending turnaround is not yet demonstrated. Totogi’s announcement provides no quantified savings, implementation schedule, or independently evaluated investment results.

From busy towers to business value​

According to Totogi, the connected model will cover Viva’s sites continuously, expose cost to serve at customer and site level, and relate network performance to the operator’s SuperApp and advertising business. Those are vendor-described capabilities, not measured outcomes from this deployment.

TelcoForge’s October 1 coverage also describes revenue attribution as the investment criterion being added to capacity metrics. That distinction matters: the announcement does not say Viva will abandon traffic analysis or engineering requirements. It proposes a broader basis for deciding where capital should go.

The analytical question is straightforward: does the busiest site necessarily deserve the next upgrade? Traffic measures activity; the proposed model is intended to connect that activity to commercial value. The sensible interpretation is that economics should inform capacity planning—not become an excuse to ignore congestion, reliability, or coverage needs.

A dashboard can tell a planner that a site is busy. The harder question is whether improving it produces enough additional value to justify the expense. That is the decision Viva and Totogi say they want to address.

What Microsoft Azure does—and does not—mean here​

Azure’s role is specific: some of Viva’s existing vendor and internally developed applications run in Microsoft’s public cloud, and Totogi says its platform will connect them with on-premises systems. The announcement does not establish that Totogi Ontology itself is hosted on Azure, name particular Azure services, or identify a Microsoft partnership.

This makes the story a hybrid-environment integration project rather than an Azure product launch. The distinction may sound small, but it prevents a familiar reporting shortcut: connecting to a cloud-hosted application is not the same thing as running the entire solution in that cloud.

Totogi’s general product documentation supplies useful architectural context. It describes the Ontology as a semantic layer above existing business-support, operational-support, and network systems. Each application maps into shared definitions so that entities, relationships, processes, and actions can be interpreted consistently across the estate. The documentation also says the product can work above an existing data lake rather than requiring its replacement. These are descriptions of the product’s design, not verification of Viva’s implementation.

The practical test: explain the recommendation​

For an IT or network team evaluating this approach, the important questions are less glamorous than the AI branding:

• How is revenue attributed when a customer uses multiple sites?
• Which costs are assigned to a site, and which remain shared?
• How fresh are the commercial and network inputs?
• Can planners trace a recommendation back to its assumptions?
• Who approves an investment decision?

These are evaluation questions, not disclosed features of Viva’s deployment. They distinguish a useful decision-support system from a confident-looking answer whose accounting cannot be explained.

One relevant detail appears in Totogi’s broader documentation: it says actions can be staged as scenarios, reviewed by a person, and committed afterward, with the permitted scope of AI action adjustable. That establishes a vendor-described human-review capability, but the Viva announcement does not specify whether—or how—the operator will use it.

A selection, not a completed turnaround​

Viva’s project is a concrete example of applying AI to investment prioritization across existing cloud and on-premises applications. Its immediate significance is the proposed connection between network conditions and business economics, not a proven financial recovery.

The next meaningful evidence would be an explained investment decision and a measured result: what Viva chose differently, why, and whether the outcome justified the spending. Until then, the disciplined verdict is promising decision-support architecture—with the return on investment still awaiting its report card.