LensReading which lens this session carries.

Operate · the run state

Every queue, one day, one canvas

This is the operation as it stood at the close of Sat, May 9. 36 queues across 12 towers, ranked not by how large they are but by how fast they are changing …

The documents behind it
Day on screen
Sat, May 9
Sun, Aug 17365 modeled daysSun, Aug 16
Back to the last modeled day

Health

What the day did to the operation

Arrival against service is the only pair that tells you whether tomorrow is worse than today.

The binding constraint on this day
Invoice processing in Source-to-Pay — 228,050 items standing and growing by 1,172 a day.

Of the 36 queues on this canvas, this one is ranked first because releasing it frees the most work: it holds 8.4% of everything standing, and it is taking on 1,172 more items a day than it clears, so the share is rising. At the day service rate of 2,544 items, and only if nothing else arrived, what is already standing in it is 89.6 days of work. Its oldest item has been waiting 45.4 d, and 754 of the 2,544 items it did serve cleared outside commitment.

The name recorded against most of the work in this queue in the sampled ledger week is Adaeze Nwachukwu. That is who this constraint belongs to.

228,050
Standing
8.4%
Share of all standing work
3,716
Arrived on the day
2,544
Served on the day
-1%
Against its own normal
45.4 d
Oldest item

Detail on the record

The blockage map

Every queue in the operation, grouped by tower.

All queues at the close of the day

36 queues · 2,728,202 items standing · deepest is 228,050

■ 90%+ inside commitment■ 75 to 90%■ under 75%
S2PSource-to-Pay472,685 standing · 17.3% of the operation
Invoice processing
228,050+1,17245.4 d
Buying desk
175,956-1,21053.8 d
Supplier operations
68,679-46336.8 d
H2RHire-to-Retire404,180 standing · 14.8% of the operation
Payroll operations
203,046+41848.2 d
Time and claims
163,093+75141.5 d
Employee lifecycle
38,041-4114.8 d
ITSIT Service334,120 standing · 12.2% of the operation
Incident desk
138,639+24756.3 d
Change and access
98,424+65644.4 d
Service requests
97,057-51667.6 d
M2DMake-to-Deliver319,662 standing · 11.7% of the operation
Move and deliver
169,971-22677.9 d
Make and release
142,454+9524.6 d
Quality control
7,237+378.4 d
O2COrder-to-Cash277,126 standing · 10.2% of the operation
Order desk
203,900-3197.9 d
Billing and credit
59,577+44910.4 d
Cash and collections
13,649-47317.6 d
AIOAI Operations254,380 standing · 9.3% of the operation
Agent run desk
107,956+12019.7 d
Model routing
97,628+41130.7 d
Prompt and policy
48,796-19719.1 d
C2LConcept-to-Launch199,561 standing · 7.3% of the operation
Artwork studio
87,544+1687.8 d
Formulation
84,658-12919.3 d
Launch gates
27,359+13610.3 d
R2RRecord-to-Report176,051 standing · 6.5% of the operation
Postings desk
131,194+865.8 d
Reconciliation
22,719-29011.9 d
Close management
22,138-25525.6 d
A2LAwareness-to-Lead78,363 standing · 2.9% of the operation
Media operations
42,972+28827.1 d
Trade promotion
23,308+4312.8 d
Campaign briefing
12,083-2005.2 d
P2PPlan-to-Perform73,448 standing · 2.7% of the operation
Sales and operations planning
27,158+9049.8 d
Replenishment
24,899+13839.9 d
Forecast desk
21,391-8340.4 d
LGLLegal Operations71,783 standing · 2.6% of the operation
Contract desk
46,445-18416.1 d
Obligation management
14,261+4313.0 d
Matter management
11,077+8332.5 d
D&AData and Analytics66,843 standing · 2.5% of the operation
Report certification
28,642+1838.4 d
Metric governance
25,278-12861.5 d
Data quality
12,923-858.5 d

Three numbers follow each bar: items standing at the close, the day net change, and the age of the oldest item in the queue. The bars are an exhaustive map of the operation — all 36 queues appear, and their standing depths sum to the 2,728,202 on the tile above. A queue opens the series with work already in it, so standing depth is not arrivals minus service.

What to pick up

Flow rather than stock

Ranked by how much work releasing the queue would free — standing depth plus five days of the rate at which it is falling behind.

Every queue, ranked by what releasing it frees

20 queues are taking on more than they clear

#QueueTowerArrivedServedNetStandingNormalvs normalDays of workInsideOldest
1Invoice processingS2P3,7162,544+1,172228,050231,094-1%89.670%45.4 d
2Payroll operationsH2R2,3701,952+418203,046190,578+7%104.084%48.2 d
3Order deskO2C2,1722,203-31203,900203,345+0%92.667%97.9 d
4Buying deskS2P2,2363,446-1,210175,956180,513-3%51.179%53.8 d
5Move and deliverM2D1,8482,074-226169,971160,709+6%82.084%77.9 d
6Time and claimsH2R2,9572,206+751163,093170,617-4%73.995%41.5 d
7Make and releaseM2D1,7481,653+95142,454136,984+4%86.291%24.6 d
8Incident deskITS1,7731,526+247138,639139,866-1%90.988%56.3 d
9Postings deskR2R2,1372,129+8131,194138,897-6%61.666%65.8 d
10Agent run deskAIO1,5731,453+120107,956102,338+5%74.393%19.7 d
11Change and accessITS1,8921,236+65698,42496,418+2%79.667%44.4 d
12Model routingAIO1,5861,175+41197,62893,687+4%83.165%30.7 d
13Service requestsITS1,1981,714-51697,05794,028+3%56.672%67.6 d
14Artwork studioC2L872856+1687,54485,379+3%102.374%87.8 d
15FormulationC2L1,1931,322-12984,65881,284+4%64.086%19.3 d
16Supplier operationsS2P1,2081,671-46368,67975,193-9%41.185%36.8 d
17Billing and creditO2C3,1282,679+44959,57767,399-12%22.263%10.4 d
18Prompt and policyAIO780977-19748,79647,444+3%49.973%19.1 d
19Contract deskLGL1,0281,212-18446,44544,420+5%38.390%16.1 d
20Media operationsA2L753465+28842,97241,104+5%92.496%27.1 d
21Employee lifecycleH2R1,4731,514-4138,04137,706+1%25.175%14.8 d
22Report certificationD&A557539+1828,64228,743-0%53.187%38.4 d
23Launch gatesC2L682546+13627,35926,386+4%50.168%10.3 d
24Sales and operations planningP2P568478+9027,15825,982+5%56.867%49.8 d
25ReplenishmentP2P546408+13824,89923,374+7%61.077%39.9 d
26Metric governanceD&A377505-12825,27826,078-3%50.175%61.5 d
27Trade promotionA2L863820+4323,30822,294+5%28.492%12.8 d
28ReconciliationR2R1,8512,141-29022,71931,501-28%10.695%11.9 d
29Close managementR2R731986-25522,13826,318-16%22.573%25.6 d
30Forecast deskP2P402485-8321,39122,510-5%44.169%40.4 d
31Obligation managementLGL449406+4314,26111,663+22%35.184%13.0 d
32Cash and collectionsO2C7191,192-47313,64918,752-27%11.583%17.6 d
33Data qualityD&A665750-8512,92316,815-23%17.265%8.5 d
34Campaign briefingA2L1,4111,611-20012,08317,611-31%7.565%5.2 d
35Matter managementLGL334251+8311,07710,779+3%44.170%32.5 d
36Quality controlM2D370333+377,2376,049+20%21.792%8.4 d

"Normal" is the mean standing depth for that same queue over the 27 modeled days before the one on screen, so it is a comparison of a queue with itself rather than with any other queue. "Days of work" divides what is standing by what was served on the day. Both are unavailable at the start of the series, where there are no prior days to average.

Now versus normal

2 queues are more than ten percent above their own 27 day mean

LGLObligation management14,261 standing against a normal of 11,663 · +22%
M2DQuality control7,237 standing against a normal of 6,049 · +20%
The commitment on the day
37,194 of 47,458 items served cleared inside commitment — 78.4%.

10,264 items cleared outside their commitment. They are spread across 36 queues, and the deepest single contributor is Billing and credit with 982. Commitment here is measured against what was served on the day; items still standing have not yet been judged against it.

900,433
Documents a week
36
Queues on the canvas
365
Days you can travel

Actions

What is waiting on a person

A queue is worth acting on when it is growing, not when it is large.

Operations

What this desk is allowed to start

A surface that only reports is not operable.

Trigger and bound

This page can rank every queue by depth, by growth and against its own prior distribution, and name the one whose release frees the most work.

Live observability

What the record shows right now

Direction of travel on the day on screen, an exhaustive partition of all 36 queues: each queue either grew, drained or held level.

Current distribution

36 queues

Growing2569%
Draining822%
Level38%

Is policy and strategy coming to fruition

Whether the written intent is holding here

79.6% of what was served on the day cleared inside commitment, with 1,636,528 items left standing.

Nothing on the record settles this

The written position is that work is managed by flow rather than by backlog size, and that a commitment is a promise about each item rather than an average.

What this page is, and what it is not

This page animates a modeled series. The 365 days between Sun, Aug 17 and Sun, Aug 16 were generated from a fixed seed for Brightvale, an invented company, and nothing on this canvas is attached to a running queue in any real system. Moving the day changes which generated row is being read. It does not replay anything that happened.

Brightvale Consumer Group is an invented company.

Two conventions matter for reading it. Queues open the series carrying work, so standing depth is not the running total of arrivals minus service, and the two should not be reconciled against each other. And unlike the ledger, none of this is sampled: arrival, service and depth are full population counts, so multiplying them by fifty to match the ledger sample would be wrong in both directions.

The binding constraint is computed, not chosen. It is the queue with the highest standing depth plus five times the rate at which it is falling behind — a deliberate weighting that puts growth ahead of size. A different weighting names a different queue, and the ranking below it changes with the day on screen.