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 Sun, Feb 8. 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
Sun, Feb 8
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
Order desk in Order-to-Cash — 149,265 items standing and growing by 1,533 a day.

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

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

149,265
Standing
7.6%
Share of all standing work
3,474
Arrived on the day
1,941
Served on the day
+8%
Against its own normal
21.8 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,960,386 items standing · deepest is 151,183

■ 90%+ inside commitment■ 75 to 90%■ under 75%
S2PSource-to-Pay332,559 standing · 17.0% of the operation
Invoice processing
151,183+15815.7 d
Buying desk
117,239+1,45930.4 d
Supplier operations
64,137+52727.8 d
H2RHire-to-Retire292,338 standing · 14.9% of the operation
Payroll operations
143,865+11162.9 d
Time and claims
119,896+1,66831.9 d
Employee lifecycle
28,577+52510.4 d
ITSIT Service229,862 standing · 11.7% of the operation
Incident desk
89,069+84329.4 d
Change and access
71,625+57240.9 d
Service requests
69,168+48218.6 d
O2COrder-to-Cash212,542 standing · 10.8% of the operation
Order desk
149,265+1,53321.8 d
Billing and credit
51,581+3995.7 d
Cash and collections
11,696+726.3 d
M2DMake-to-Deliver211,565 standing · 10.8% of the operation
Move and deliver
108,316+1,18027.7 d
Make and release
97,503+79026.7 d
Quality control
5,746+6711.4 d
AIOAI Operations180,654 standing · 9.2% of the operation
Model routing
72,111+36248.7 d
Agent run desk
71,152+1,05134.8 d
Prompt and policy
37,391+66027.7 d
C2LConcept-to-Launch142,893 standing · 7.3% of the operation
Formulation
60,577+72232.2 d
Artwork studio
59,996+33129.5 d
Launch gates
22,320+7716.5 d
R2RRecord-to-Report142,622 standing · 7.3% of the operation
Postings desk
95,096+32219.0 d
Reconciliation
25,957+4343.8 d
Close management
21,569+11012.2 d
A2LAwareness-to-Lead62,776 standing · 3.2% of the operation
Media operations
27,627+48732.6 d
Trade promotion
18,575+32512.6 d
Campaign briefing
16,574+1187.3 d
P2PPlan-to-Perform53,256 standing · 2.7% of the operation
Replenishment
18,710+10925.4 d
Sales and operations planning
18,509+12432.9 d
Forecast desk
16,037+8214.6 d
D&AData and Analytics51,267 standing · 2.6% of the operation
Report certification
19,256+20827.3 d
Metric governance
16,912-1643.1 d
Data quality
15,099+17512.5 d
LGLLegal Operations48,052 standing · 2.5% of the operation
Contract desk
29,359+1776.8 d
Obligation management
11,535+2308.4 d
Matter management
7,158+1178.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 1,960,386 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

35 queues are taking on more than they clear

#QueueTowerArrivedServedNetStandingNormalvs normalDays of workInsideOldest
1Order deskO2C3,4741,941+1,533149,265138,119+8%76.966%21.8 d
2Invoice processingS2P3,3613,203+158151,183151,071+0%47.265%15.7 d
3Payroll operationsH2R2,2192,108+111143,865117,622+22%68.281%62.9 d
4Time and claimsH2R3,8382,170+1,668119,896115,430+4%55.394%31.9 d
5Buying deskS2P3,7042,245+1,459117,239110,055+7%52.288%30.4 d
6Move and deliverM2D2,9461,766+1,180108,31693,667+16%61.394%27.7 d
7Make and releaseM2D1,684894+79097,50385,333+14%109.170%26.7 d
8Postings deskR2R2,4312,109+32295,09687,393+9%45.194%19.0 d
9Incident deskITS1,9561,113+84389,06982,168+8%80.076%29.4 d
10Agent run deskAIO1,957906+1,05171,15262,919+13%78.585%34.8 d
11Change and accessITS1,7661,194+57271,62562,322+15%60.065%40.9 d
12Model routingAIO1,323961+36272,11160,986+18%75.070%48.7 d
13Service requestsITS2,1081,626+48269,16858,969+17%42.582%18.6 d
14Supplier operationsS2P1,6401,113+52764,13758,114+10%57.674%27.8 d
15FormulationC2L1,7381,016+72260,57749,913+21%59.685%32.2 d
16Artwork studioC2L1,081750+33159,99653,082+13%80.071%29.5 d
17Billing and creditO2C2,5222,123+39951,58147,482+9%24.378%5.7 d
18Prompt and policyAIO1,378718+66037,39132,241+16%52.178%27.7 d
19Employee lifecycleH2R1,6031,078+52528,57728,793-1%26.563%10.4 d
20Contract deskLGL1,9361,759+17729,35929,818-2%16.791%6.8 d
21Media operationsA2L856369+48727,62724,739+12%74.975%32.6 d
22ReconciliationR2R2,1871,753+43425,95727,787-7%14.864%3.8 d
23Launch gatesC2L745668+7722,32020,565+9%33.478%16.5 d
24Close managementR2R946836+11021,56918,133+19%25.873%12.2 d
25Report certificationD&A654446+20819,25617,538+10%43.272%27.3 d
26Trade promotionA2L1,018693+32518,57519,075-3%26.893%12.6 d
27ReplenishmentP2P492383+10918,71015,465+21%48.975%25.4 d
28Sales and operations planningP2P558434+12418,50916,072+15%42.678%32.9 d
29Campaign briefingA2L1,5501,432+11816,57422,724-27%11.693%7.3 d
30Metric governanceD&A395411-1616,91216,843+0%41.192%43.1 d
31Forecast deskP2P527445+8216,03715,303+5%36.074%14.6 d
32Data qualityD&A952777+17515,09915,518-3%19.485%12.5 d
33Obligation managementLGL775545+23011,5359,323+24%21.279%8.4 d
34Cash and collectionsO2C1,1771,105+7211,69614,570-20%10.694%6.3 d
35Matter managementLGL350233+1177,1586,051+18%30.766%8.5 d
36Quality controlM2D437370+675,7465,225+10%15.596%11.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

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

LGLObligation management11,535 standing against a normal of 9,323 · +24%
H2RPayroll operations143,865 standing against a normal of 117,622 · +22%
C2LFormulation60,577 standing against a normal of 49,913 · +21%
P2PReplenishment18,710 standing against a normal of 15,465 · +21%
R2RClose management21,569 standing against a normal of 18,133 · +19%
LGLMatter management7,158 standing against a normal of 6,051 · +18%
AIOModel routing72,111 standing against a normal of 60,986 · +18%
ITSService requests69,168 standing against a normal of 58,969 · +17%
AIOPrompt and policy37,391 standing against a normal of 32,241 · +16%
M2DMove and deliver108,316 standing against a normal of 93,667 · +16%
P2PSales and operations planning18,509 standing against a normal of 16,072 · +15%
ITSChange and access71,625 standing against a normal of 62,322 · +15%

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

The commitment on the day
33,284 of 41,693 items served cleared inside commitment — 79.8%.

8,409 items cleared outside their commitment. They are spread across 36 queues, and the deepest single contributor is Invoice processing with 1,128. 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.