Corporate Mobile Telecommunications Optimisation · Technical White Paper
Corporate Mobile Telecommunications Optimisation
A method for reconstructing a fragmented multi-entity mobile estate, building a pooled usage model from observed behaviour, and governing it afterwards so the fragmentation does not return.
6 · The pooled model
Built from observed usage, not a tariff brochure
The pool was sized from historical usage across the analysed population rather than from a generic allowance assumption. That is the difference between a bundle that fits the estate and one the estate has to fit.
Pooling works because individual allowances are wasteful in both directions at once: some users never approach theirs while others routinely exceed theirs and pay out-of-bundle rates. Aggregating the two removes a cost that exists only because the allowances were separate.
8 · Pooled pricing is not a flat guarantee forever
The proposal described pooled bearer bundles without ordinary out-of-bundle charges for included categories — subject to fair-usage mechanics and excluded services.
Those two qualifications do real work. A pooled model has limits, review points and services that sit outside it, and treating it as unlimited is how an organisation discovers a charge it believed it had negotiated away.
9 · Spend management
Why visibility is part of the commercial result
Scroll table sideways →
| Control capability | Use in the operating model |
|---|---|
| Near-real-time spend visibility | Identify abnormal or emerging spend before it becomes a month-end surprise. |
| Historical reporting | Track trends, and test whether the pooled baseline remains fit for purpose. |
| Department and user allocation | Create accountability without breaking the shared commercial model. |
| Policy and exception alerts | Flag behaviour falling outside agreed business rules. |
| Traffic reporting | Analyse voice, data, SMS and international categories. |
| Subscriber administration | Central management of SIMs and selected service actions. |
| Management information distribution | Push reporting to cost owners and decision makers. |
The platform was incorporated into the enterprise solution without a separate service charge. That matters because the value of a pooled tariff depends on visibility: without central reporting, an organisation can move from fragmented tariffs to a pooled tariff and still lack the information needed to control behaviour.
10 · Device economics
Three questions that must stay separate
Device economics make mobile proposals deceptively hard to compare. A tariff can look expensive because it carries a device subsidy, or artificially cheap because the handset is funded elsewhere.
The three questions are: what the organisation pays for connectivity, what it pays or commits for devices, and what device standard employees are entitled to receive. Conflating them makes tariff comparison unreliable — and encourages employees to treat an upgrade as an entitlement rather than a business asset decision.
10.1 · Device controls
Five rules that follow from that separation
- Create a device policy by role or operational requirement, not by historical tariff entitlement.
- Track device funding separately from recurring network usage.
- Ensure upgrade eligibility does not automatically trigger replacement where the current device remains serviceable.
- Control early upgrades, premium-device pay-ins and lost or damaged replacement through an explicit approval framework.
- Keep residual device obligations visible during any supplier or tariff migration.
13 · Multi-entity governance
Group leverage without erasing legal separation
A consolidation exercise naturally pulls towards a single account, because that is where the commercial leverage is. The constraint here was that participating entities are separate legal persons with separate liability, and the structure had to respect that.
The architecture therefore centralises commercial treatment and reporting while preserving entity separation — group scale for negotiation, individual accountability for obligation. That is a design input, not a compliance check to run afterwards, because unwinding a collapsed account structure is considerably harder than designing one correctly.
14 · Implementation
The sequence that protects specialist services
Approve the structure
Confirm participating entities, subscriber population, usage categories and the commercial proposal.
Complete entity authorisations
Obtain the approvals needed to access data and alter account structure for each participating legal entity.
Validate the subscriber inventory
Confirm owner, cost centre, contract state, device obligation and service purpose for every line.
Activate the enterprise architecture
Move the agreed population into the pooled structure without disrupting specialist services — the machine-to-machine and telemetry connections that pooling would break.