NPO Mobile Data & Telecommunications Optimisation · Technical White Paper
NPO Mobile Data & Telecommunications Optimisation
Usage reconstruction, package right-sizing and portal governance — together with a full account of how the cut-over broke down and what each failure teaches.
4 · The default package
Why a uniform allowance loses money twice
Most connections sat on a common 2GB bundle while recorded usage ranged from negligible to repeatedly above that level. That single decision produces two opposite forms of leakage at once: stranded allowance on the quiet lines, and top-up or out-of-bundle exposure on the busy ones.
It also rules out the obvious remedy. A pure downgrade strategy would have created avoidable top-up cost and user disruption on the lines that genuinely needed more — which is why the right-sized model widened the range in both directions rather than moving everyone down.
7 · Why top-up economics had to be modelled
The financial logic depended on using smaller packages safely. Without central monitoring and quick top-up capability, aggressive right-sizing would merely transfer cost risk into operational disruption.
The portal is therefore part of the commercial solution rather than a feature alongside it. A smaller package is only cheaper if the organisation can see when a line is about to exceed it and act in time.
11 · What went wrong in implementation
Six breakdowns, and the control each one teaches
Scroll table sideways →
| Breakdown | Observed effect | Control lesson |
|---|---|---|
| The user and package list changed outside the agreed analytical process | Intended downgrades were not carried consistently into the order. | Every order revision must be reconciled back to the approved optimisation model. |
| Additional users and different service decisions introduced late | The population no longer matched the original migration plan. | Maintain a version-controlled master list with formal change approval. |
| KuTh removed from parts of supplier and client communication | The transition coordinator lost visibility of critical decisions. | One accountable cut-over owner must remain copied on every migration change. |
| Incumbent cancellation proceeded before replacement readiness | Users experienced a period without working replacement SIMs. | Cancellation is a gated milestone, not a calendar event. |
| Package assumptions were reintroduced | Some users were treated as though the lower tiers did not exist. | The approved tariff catalogue must be embedded in order validation. |
| Distribution complexity underestimated | Physical readiness lagged behind the commercial decision. | Treat logistics as a critical-path workstream with branch-level confirmation. |
The implementation record is valuable precisely because it is not a perfect success narrative. It records a breakdown after a well-defined commercial and operating design had already been developed.
12 · Corrective management afterwards
What the later schedule shows
A retained schedule records 28 line-level upgrade or downgrade instructions — numerous reductions from 2GB to 500MB or 1GB, and targeted increases for specific high-use lines and routers.
- Many standard 2GB lines were later directed to lower tiers.
- Some high-use connections were upgraded rather than forced downward.
- Router-type demand was treated separately from ordinary user demand.
- The existence of later changes reinforces the need for ongoing usage review after implementation — package size is a managed variable, not a one-time decision.
17 · Why this is published separately from the corporate case
Two engagements inside one capability
Scroll table sideways →
| Dimension | Corporate mobile | NPO mobile |
|---|---|---|
| Primary problem | Fragmented multi-entity estate with voice, data, roaming and specialist connections. | Reseller-based data estate with package mismatch and limited direct administrative control. |
| Core lever | Shared enterprise pooling, group leverage, tariff and governance redesign. | Direct carrier migration plus line-level package right-sizing. |
| Headline result | 15.0% supplier-quoted reduction on analysed pooled spend. | 30.7% equivalent-migration model; 40.8% usage-right-sized model. |
| Operating-control focus | Spend-management platform, pooled tolerance, device funding, account governance. | Portal top-ups, package changes, line capping, SIM logistics, branch distribution. |
| Implementation lesson | Approvals, migration and validation remained to be completed in the retained pack. | Migration was contracted but cut-over sequencing broke down, producing operational disruption. |
Both sit within Mobile Telecommunications Optimisation, and they address materially different commercial architectures. Combining them into one case study would blur the method and make the percentages appear more comparable than they are.
18 · Publication status
The retained evidence is sufficient to publish the commercial models, package architecture, operating controls and implementation lessons.
It is not sufficient to present the 40.8% as a fully achieved recurring cash saving, because the pack does not provide a complete post-migration billing run proving sustained realisation after the disrupted cut-over.
That distinction protects the credibility of the case rather than diminishing it.