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 Mon, Feb 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
Mon, Feb 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 — 154,083 items standing and growing by 2,900 a day.

Of the 36 queues on this canvas, this one is ranked first because releasing it frees the most work: it holds 7.8% of everything standing, and it is taking on 2,900 more items a day than it clears, so the share is rising. At the day service rate of 9,825 items, and only if nothing else arrived, what is already standing in it is 15.7 days of work. Its oldest item has been waiting 3.9 d, and 2,285 of the 9,825 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.

154,083
Standing
7.8%
Share of all standing work
12,725
Arrived on the day
9,825
Served on the day
+2%
Against its own normal
3.9 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 · 1,984,391 items standing · deepest is 154,083

■ 90%+ inside commitment■ 75 to 90%■ under 75%
S2PSource-to-Pay337,521 standing · 17.0% of the operation
Invoice processing
154,083+2,9003.9 d
Buying desk
119,162+1,92310.3 d
Supplier operations
64,276+1394.7 d
H2RHire-to-Retire295,549 standing · 14.9% of the operation
Payroll operations
145,189+1,3249.7 d
Time and claims
121,360+1,4647.2 d
Employee lifecycle
29,000+4234.1 d
ITSIT Service232,354 standing · 11.7% of the operation
Incident desk
90,485+1,4166.8 d
Change and access
72,309+68412.7 d
Service requests
69,560+39212.6 d
M2DMake-to-Deliver215,499 standing · 10.9% of the operation
Move and deliver
110,253+1,9375.5 d
Make and release
99,512+2,0099.5 d
Quality control
5,734-123.0 d
O2COrder-to-Cash213,428 standing · 10.8% of the operation
Order desk
150,128+86315.2 d
Billing and credit
51,723+1426.9 d
Cash and collections
11,577-1192.6 d
AIOAI Operations183,289 standing · 9.2% of the operation
Agent run desk
73,123+1,9718.5 d
Model routing
72,518+40719.5 d
Prompt and policy
37,648+25711.4 d
C2LConcept-to-Launch144,815 standing · 7.3% of the operation
Formulation
61,509+93215.3 d
Artwork studio
60,740+74418.6 d
Launch gates
22,566+2466.7 d
R2RRecord-to-Report144,767 standing · 7.3% of the operation
Postings desk
96,939+1,8435.7 d
Reconciliation
25,863-943.5 d
Close management
21,965+3967.8 d
A2LAwareness-to-Lead62,626 standing · 3.2% of the operation
Media operations
27,880+2539.6 d
Trade promotion
18,500-755.9 d
Campaign briefing
16,246-32837.7 h
P2PPlan-to-Perform53,822 standing · 2.7% of the operation
Replenishment
19,138+4283.2 d
Sales and operations planning
18,865+3566.6 d
Forecast desk
15,819-2183.9 d
D&AData and Analytics51,361 standing · 2.6% of the operation
Report certification
19,549+29310.0 d
Metric governance
17,032+1207.0 d
Data quality
14,780-3192.3 d
LGLLegal Operations49,360 standing · 2.5% of the operation
Contract desk
29,946+5873.5 d
Obligation management
12,104+5692.7 d
Matter management
7,310+1523.3 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 1,984,391 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

29 queues are taking on more than they clear

#QueueTowerArrivedServedNetStandingNormalvs normalDays of workInsideOldest
1Invoice processingS2P12,7259,825+2,900154,083151,019+2%15.777%3.9 d
2Order deskO2C8,1007,237+863150,128138,663+8%20.776%15.2 d
3Payroll operationsH2R8,4517,127+1,324145,189119,401+22%20.494%9.7 d
4Buying deskS2P9,0627,139+1,923119,162110,466+8%16.794%10.3 d
5Time and claimsH2R11,2509,786+1,464121,360115,920+5%12.494%7.2 d
6Move and deliverM2D8,1726,235+1,937110,25394,443+17%17.763%5.5 d
7Make and releaseM2D6,3804,371+2,00999,51286,049+16%22.889%9.5 d
8Postings deskR2R8,5136,670+1,84396,93987,700+11%14.596%5.7 d
9Incident deskITS5,7674,351+1,41690,48582,588+10%20.868%6.8 d
10Agent run deskAIO5,7473,776+1,97173,12363,341+15%19.469%8.5 d
11Change and accessITS4,8224,138+68472,30962,798+15%17.584%12.7 d
12Model routingAIO3,9323,525+40772,51861,760+17%20.669%19.5 d
13Service requestsITS4,9404,548+39269,56059,769+16%15.377%12.6 d
14FormulationC2L4,3603,428+93261,50950,698+21%17.980%15.3 d
15Supplier operationsS2P5,9865,847+13964,27658,629+10%11.077%4.7 d
16Artwork studioC2L3,2562,512+74460,74053,495+14%24.294%18.6 d
17Billing and creditO2C7,7617,619+14251,72347,633+9%6.876%6.9 d
18Prompt and policyAIO3,6703,413+25737,64832,538+16%11.082%11.4 d
19Contract deskLGL5,2254,638+58729,94629,896+0%6.574%3.5 d
20Employee lifecycleH2R4,9254,502+42329,00028,986+0%6.463%4.1 d
21Media operationsA2L2,1311,878+25327,88024,873+12%14.865%9.6 d
22ReconciliationR2R6,2896,383-9425,86327,668-7%4.165%3.5 d
23Close managementR2R2,8682,472+39621,96518,361+20%8.975%7.8 d
24Launch gatesC2L2,3222,076+24622,56620,757+9%10.995%6.7 d
25ReplenishmentP2P1,8421,414+42819,13815,674+22%13.563%3.2 d
26Report certificationD&A2,0801,787+29319,54917,611+11%10.968%10.0 d
27Sales and operations planningP2P1,7211,365+35618,86516,186+17%13.894%6.6 d
28Trade promotionA2L2,7162,791-7518,50019,098-3%6.691%5.9 d
29Metric governanceD&A1,6191,499+12017,03216,848+1%11.482%7.0 d
30Campaign briefingA2L5,6335,961-32816,24622,396-27%2.773%37.7 h
31Forecast deskP2P1,4021,620-21815,81915,388+3%9.897%3.9 d
32Obligation managementLGL2,2731,704+56912,1049,496+27%7.174%2.7 d
33Data qualityD&A3,0503,369-31914,78015,585-5%4.494%2.3 d
34Cash and collectionsO2C3,1983,317-11911,57714,409-20%3.593%2.6 d
35Matter managementLGL979827+1527,3106,091+20%8.866%3.3 d
36Quality controlM2D1,1001,112-125,7345,243+9%5.290%3.0 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

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

LGLObligation management12,104 standing against a normal of 9,496 · +27%
P2PReplenishment19,138 standing against a normal of 15,674 · +22%
H2RPayroll operations145,189 standing against a normal of 119,401 · +22%
C2LFormulation61,509 standing against a normal of 50,698 · +21%
LGLMatter management7,310 standing against a normal of 6,091 · +20%
R2RClose management21,965 standing against a normal of 18,361 · +20%
AIOModel routing72,518 standing against a normal of 61,760 · +17%
M2DMove and deliver110,253 standing against a normal of 94,443 · +17%
P2PSales and operations planning18,865 standing against a normal of 16,186 · +17%
ITSService requests69,560 standing against a normal of 59,769 · +16%
AIOPrompt and policy37,648 standing against a normal of 32,538 · +16%
M2DMake and release99,512 standing against a normal of 86,049 · +16%

The first 12 of 18 are shown, deepest departure from normal first.

The commitment on the day
120,589 of 150,262 items served cleared inside commitment — 80.3%.

29,673 items cleared outside their commitment. They are spread across 36 queues, and the deepest single contributor is Move and deliver with 2,317. 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.