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 Tue, Apr 21. 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
Tue, Apr 21
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 — 235,010 items standing and growing by 356 a day.

Of the 36 queues on this canvas, this one is ranked first because releasing it frees the most work: it holds 8.6% of everything standing, and it is taking on 356 more items a day than it clears, so the share is rising. At the day service rate of 11,484 items, and only if nothing else arrived, what is already standing in it is 20.5 days of work. Its oldest item has been waiting 9.2 d, and 1,584 of the 11,484 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.

235,010
Standing
8.6%
Share of all standing work
11,840
Arrived on the day
11,484
Served on the day
-1%
Against its own normal
9.2 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,356 items standing · deepest is 235,010

■ 90%+ inside commitment■ 75 to 90%■ under 75%
S2PSource-to-Pay493,276 standing · 18.1% of the operation
Invoice processing
235,010+3569.2 d
Buying desk
181,362+2,29316.3 d
Supplier operations
76,904-6128.5 d
H2RHire-to-Retire394,664 standing · 14.5% of the operation
Payroll operations
184,937+1,99610.5 d
Time and claims
172,563+52320.2 d
Employee lifecycle
37,164+3103.6 d
ITSIT Service327,832 standing · 12.0% of the operation
Incident desk
140,226+49124.8 d
Change and access
95,526-98319.8 d
Service requests
92,080+1,09412.1 d
M2DMake-to-Deliver297,145 standing · 10.9% of the operation
Move and deliver
156,742+1,80216.6 d
Make and release
134,594+6826.3 d
Quality control
5,809+864.2 d
O2COrder-to-Cash294,334 standing · 10.8% of the operation
Order desk
203,485-68621.4 d
Billing and credit
71,044-1,1508.2 d
Cash and collections
19,805+2422.4 d
AIOAI Operations238,771 standing · 8.8% of the operation
Agent run desk
100,542+4646.7 d
Model routing
92,453+46014.2 d
Prompt and policy
45,776+5110.8 d
R2RRecord-to-Report202,410 standing · 7.4% of the operation
Postings desk
142,314-1,2278.0 d
Reconciliation
33,422-1,6534.9 d
Close management
26,674-5718.4 d
C2LConcept-to-Launch189,985 standing · 7.0% of the operation
Artwork studio
84,814+1722.7 d
Formulation
79,260+1827.3 d
Launch gates
25,911+3284.6 d
A2LAwareness-to-Lead81,423 standing · 3.0% of the operation
Media operations
40,616-2914.4 d
Trade promotion
21,799+3555.9 d
Campaign briefing
19,008-1,0422.8 d
D&AData and Analytics73,170 standing · 2.7% of the operation
Report certification
28,470+1236.9 d
Metric governance
26,310-14414.7 d
Data quality
18,390+146.8 d
P2PPlan-to-Perform71,752 standing · 2.6% of the operation
Sales and operations planning
25,755-31912.7 d
Forecast desk
23,254-1254.4 d
Replenishment
22,743-79.5 d
LGLLegal Operations63,594 standing · 2.3% of the operation
Contract desk
42,365+188.0 d
Matter management
10,676+1206.8 d
Obligation management
10,553+1162.9 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,356 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

23 queues are taking on more than they clear

#QueueTowerArrivedServedNetStandingNormalvs normalDays of workInsideOldest
1Invoice processingS2P11,84011,484+356235,010238,097-1%20.586%9.2 d
2Order deskO2C8,2768,962-686203,485210,391-3%22.776%21.4 d
3Payroll operationsH2R9,2407,244+1,996184,937172,674+7%25.564%10.5 d
4Buying deskS2P10,0247,731+2,293181,362165,670+9%23.595%16.3 d
5Time and claimsH2R9,1238,600+523172,563163,703+5%20.183%20.2 d
6Move and deliverM2D8,5276,725+1,802156,742143,889+9%23.386%16.6 d
7Incident deskITS5,4034,912+491140,226138,735+1%28.565%24.8 d
8Postings deskR2R6,6187,845-1,227142,314133,039+7%18.193%8.0 d
9Make and releaseM2D6,5285,846+682134,594133,646+1%23.067%6.3 d
10Agent run deskAIO5,1574,693+464100,542101,737-1%21.494%6.7 d
11Service requestsITS5,4904,396+1,09492,08085,408+8%20.989%12.1 d
12Change and accessITS4,8435,826-98395,52697,653-2%16.473%19.8 d
13Model routingAIO3,6973,237+46092,45386,844+6%28.697%14.2 d
14Artwork studioC2L3,2623,245+1784,81484,308+1%26.186%22.7 d
15FormulationC2L3,7253,543+18279,26073,060+8%22.483%7.3 d
16Supplier operationsS2P5,2355,847-61276,90476,844+0%13.283%8.5 d
17Billing and creditO2C8,1859,335-1,15071,04475,178-5%7.677%8.2 d
18Prompt and policyAIO3,0012,950+5145,77645,997-0%15.583%10.8 d
19Contract deskLGL4,5454,527+1842,36542,650-1%9.492%8.0 d
20Media operationsA2L2,0162,045-2940,61640,117+1%19.962%14.4 d
21Employee lifecycleH2R4,6094,299+31037,16432,081+16%8.684%3.6 d
22ReconciliationR2R4,9776,630-1,65333,42242,867-22%5.072%4.9 d
23Report certificationD&A1,8411,718+12328,47026,823+6%16.684%6.9 d
24Launch gatesC2L1,9411,613+32825,91126,627-3%16.164%4.6 d
25Close managementR2R2,6743,245-57126,67426,199+2%8.267%8.4 d
26Metric governanceD&A1,3651,509-14426,31026,588-1%17.479%14.7 d
27Sales and operations planningP2P1,5391,858-31925,75526,339-2%13.964%12.7 d
28Trade promotionA2L2,6622,307+35521,79921,317+2%9.484%5.9 d
29Forecast deskP2P1,6091,734-12523,25423,184+0%13.472%4.4 d
30ReplenishmentP2P1,4781,485-722,74324,192-6%15.381%9.5 d
31Cash and collectionsO2C3,2042,962+24219,80520,925-5%6.776%2.4 d
32Campaign briefingA2L5,0976,139-1,04219,00826,406-28%3.185%2.8 d
33Data qualityD&A2,8922,878+1418,39018,297+1%6.476%6.8 d
34Matter managementLGL1,000880+12010,6769,656+11%12.172%6.8 d
35Obligation managementLGL2,1472,031+11610,55311,231-6%5.282%2.9 d
36Quality controlM2D1,2841,198+865,8096,832-15%4.880%4.2 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

H2REmployee lifecycle37,164 standing against a normal of 32,081 · +16%
LGLMatter management10,676 standing against a normal of 9,656 · +11%
The commitment on the day
129,988 of 161,479 items served cleared inside commitment — 80.5%.

31,491 items cleared outside their commitment. They are spread across 36 queues, and the deepest single contributor is Payroll operations with 2,612. 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.