LensReading which lens this session carries.

Explain this number

Transactions a week across the towers

The weekly transaction volume of the twelve shared services towers added together.

The whole catalog
Right now
900,433
transactions
What kind of number
Modeled
Produced by an assumption we chose. Plausible, and not taken from a system of record.
Freshness
Modeled estate, refreshed at seed.
Owned by
Oscar Duarte
Function Leader

How it is computed

Sum of the weekly transaction field over tower rows.

The query that produces it
sum of txWeek over GbsTower
Source
GbsTower
12 rows on record
Rows read to answer
12
counted on this page load
Unit
transactions

900,433 transactions a week across 12 shared services towers.

Modeled run rate. It does not reconcile with the sampled ledger week and is not meant to.

The records behind it

Named rows, read live. These are the actual records the figure is standing on, not a sample chosen to illustrate it.

s2pSource-to-Pay Tower142,093 a week · 80.0% touchless
h2rHire-to-Retire Tower126,636 a week · 70.0% touchless
o2cOrder-to-Cash Tower107,549 a week · 80.0% touchless
r2rRecord-to-Report Tower87,512 a week · 72.0% touchless
itIT Service Tower85,277 a week · 80.0% touchless

Where it appears and how to reach it

This figure is rendered on Shared Services. Open that page →

Figures that only make sense beside it

What this figure is, and what it is not

Modeled run rate. It does not reconcile with the sampled ledger week and is not meant to.

Thirty-four figures carry a definition, a basis, an owner and a live query. Those are the figures on the surfaces built for this mechanism. Most numbers elsewhere in the product do not have an entry here yet, and this catalog says so rather than implying whole-product coverage.

You are seeing this as requester. The figure above was recomputed when this page loaded, so it is as fresh as the rows themselves.