The whole group, one row.
Every operating company's spend on one row, in its own currency and the group's, compared megabit for megabit once monitoring is connected.
Request a pilot
- What it does
- Rolls spend up through service, site, carrier account, operating company and group, in each entity's functional currency and the group's presentation currency, and delivered bandwidth with it once monitoring is connected.
- What it reads
- The monthly cost and utilisation facts for every service, plus the metric definition version, coverage, service count and currency basis that each published figure was computed under.
- What stays yours
- Your numbers, inside your group. Comparison runs between your own entities on your own contracts, and every published figure states the fraction of the period it actually observed.
- Where it shows up
- The board pack, the carrier negotiation, and the shortlist of services a review should start with.
Also inside this capability
Each row opens to what it does and where it stands.
Budgets
- Against actuals
- Budgets per operating company, set against what was billed, in the group's presentation currency.
- On every order
- Every order carries a budget check.
- Status
- Built.
The assistant
Short, and honest about what it needs.
- What it does
- Answers questions over your own data in Riopex.
- What it can see
- Only what the person asking can see. It reads with that person's permissions.
- What it needs
- Your organisation's own AI key. Until one is connected, the assistant is unavailable.
- Status
- Built.
Who uses it
- The reader
- Group finance and the group CIO, who present the number, and the carrier negotiator who has to defend it.
- The question
- What does the group pay per delivered megabit, by operating company, country and carrier, and how much of that figure did we actually observe?
- What they get
- One fact row per service per month, rolled up to every scope at a frozen presentation rate, cost per megabit delivered compared across entities with its coverage, and a review list ordered by what is worth an hour.
- Where it starts
- Two operating companies with services on the spine and one month of bills. Utilisation joins the comparison as bindings are confirmed.
How it is built
Spend by any cut
By operating company, by country, by carrier, by billing currency, by service family. The dimensions are columns on the fact row rather than fields in a blob, which is exactly what makes them aggregate.
Cost per megabit delivered
The headline metric wherever coverage allows it, always labelled with that coverage. Where a monitoring binding is still to come, the contracted-capacity version stands in and says so. Both are stored definitions with versions rather than ad-hoc dashboard arithmetic.
Shared backbone, apportioned
A charge that lands at account or section level is split by an explicit allocation rule into shares that sum exactly, with the remainder assigned to the largest share so amounts conserve to the minor unit. An allocation never edits an invoice line.
A review list
The output is an ordered list of services worth a human hour, each with its role, contract and coverage attached. Where a gate failed, the reason is shown, because an unknown role is an onboarding task rather than a verdict.
What you get
One figure at every scope
A group total and an operating company total are the same query at a different level. There is one definition of the metric, versioned, and every published figure names the version it was computed under.
A board pack that holds still
The presentation rate is frozen onto the roll-up when the month is fixed. A restated rate next week adds a row and leaves the figure already presented exactly as it was.
A shortlist, with its reasons
The output is an ordered list of services worth a human hour, each with its role, contract and coverage attached, and every gate that failed stated beside it.
How it works
- Fix the monthCost and utilisation are stored per service per month, both rebuildable from source. Nothing is computed live from raw invoices at read time.
- Fix the rateThe presentation rate for a group, a month and a currency pair is resolved once and frozen onto the roll-up, so a rate restated next week cannot move a figure already presented.
- Roll upThe same measures are held at every scope, so a group total and an operating company total are the same query at a different level rather than two implementations that drift.
- CompareEntities are compared on delivered megabits rather than on invoice totals. A service with no meaningful capacity denominator is counted in the total and held out of the comparison, so the figure stays defensible.
One comparison, end to end
The same 100 Mbps MPLS port in two operating companies, one in Riyadh and one in Nairobi, compared for one month.
- Two cost facts
- Each port's month is fixed from its invoice line: one billed in SAR, one in KES, each held as billed, in its entity's functional currency and in the group's presentation currency.
- Two utilisation facts
- Each port's delivered megabits come from its bound interface, with coverage: 99% in Riyadh, 71% in Nairobi after a monitoring outage.
- The rate
- The month's presentation rate for each currency pair is resolved once and frozen onto the roll-up, and both figures name it.
- The comparison
- Cost per megabit delivered is computed under the same metric version for both. The Nairobi figure is published with its 71% coverage beside it, and the pane says so before anyone reads the number.
- The review list
- The Riyadh port costs twice the Nairobi port per delivered megabit. Its role is primary, its contract has no minimum this service helps meet, and coverage clears the bar, so it lands on the review list with its reasons.
Questions about the group view
Which currency does the board see?
The group's presentation currency, with each operating company's functional currency one level down and the billed amount beneath that. All three are held, so a figure can be traced back to the line it came from.
Can we change the metric definition?
The definition is versioned, and every published figure names the version it used. A new version is a new definition rather than an edit, so last quarter's figures stay comparable with themselves.
How far back does the view go?
As far back as the invoices you give us. Monthly facts are rebuilt from source, so a year of historic invoices becomes a year of comparable months, with coverage marked as missing where no utilisation exists for them.
Who can see the whole group?
A group administrator, through one audited database function that is the only path across the entity boundary. Everyone else sees the operating companies they hold a membership in.
Related capabilities
