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, Nov 10. 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, Nov 10
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 — 46,835 items standing and growing by 2,087 a day.

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

46,835
Standing
8.0%
Share of all standing work
9,755
Arrived on the day
7,668
Served on the day
+38%
Against its own normal
3.5 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 · 586,877 items standing · deepest is 51,186

■ 90%+ inside commitment■ 75 to 90%■ under 75%
S2PSource-to-Pay112,210 standing · 19.1% of the operation
Buying desk
51,186+1,1096.1 d
Invoice processing
38,457+1,0393.9 d
Supplier operations
22,567+5055.2 d
H2RHire-to-Retire86,620 standing · 14.8% of the operation
Payroll operations
43,907+1,9022.9 d
Time and claims
33,330-1,42542.0 h
Employee lifecycle
9,383+6542.3 d
O2COrder-to-Cash64,056 standing · 10.9% of the operation
Order desk
46,835+2,0873.5 d
Billing and credit
17,070+1,69034.0 h
Cash and collections
151+15117.5 h
ITSIT Service63,506 standing · 10.8% of the operation
Incident desk
24,623+1,0543.1 d
Service requests
21,899+7093.9 d
Change and access
16,984+6062.4 d
M2DMake-to-Deliver58,341 standing · 9.9% of the operation
Make and release
33,141+1,0526.1 d
Move and deliver
24,156+1,6422.1 d
Quality control
1,044+13915.8 h
AIOAI Operations55,520 standing · 9.5% of the operation
Agent run desk
24,415+8342.8 d
Model routing
20,814+9595.8 d
Prompt and policy
10,291+40440.4 h
C2LConcept-to-Launch40,631 standing · 6.9% of the operation
Formulation
18,152+2842.9 d
Artwork studio
17,284+7444.1 d
Launch gates
5,195+3102.8 d
R2RRecord-to-Report40,290 standing · 6.9% of the operation
Postings desk
35,627+1,6322.4 d
Close management
2,824-12415.6 h
Reconciliation
1,839+2629.7 h
D&AData and Analytics19,076 standing · 3.3% of the operation
Data quality
7,550-513.8 d
Report certification
6,152+183.7 d
Metric governance
5,374+1733.3 d
A2LAwareness-to-Lead18,962 standing · 3.2% of the operation
Media operations
7,441+3632.9 d
Campaign briefing
7,435+37035.2 h
Trade promotion
4,086+48041.8 h
P2PPlan-to-Perform16,461 standing · 2.8% of the operation
Sales and operations planning
5,645+37637.3 h
Forecast desk
5,480+2541.7 h
Replenishment
5,336+25140.8 h
LGLLegal Operations11,204 standing · 1.9% of the operation
Obligation management
5,868+53.1 d
Contract desk
4,527+1,07831.6 h
Matter management
809-13432.5 h

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 586,877 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

32 queues are taking on more than they clear

#QueueTowerArrivedServedNetStandingNormalvs normalDays of workInsideOldest
1Order deskO2C9,7557,668+2,08746,83534,040+38%6.194%3.5 d
2Buying deskS2P9,1978,088+1,10951,18629,264+75%6.370%6.1 d
3Payroll operationsH2R8,9147,012+1,90243,90725,635+71%6.374%2.9 d
4Postings deskR2R7,7206,088+1,63235,62718,079+97%5.975%2.4 d
5Invoice processingS2P12,53311,494+1,03938,45735,773+8%3.382%3.9 d
6Make and releaseM2D6,2985,246+1,05233,14117,486+90%6.368%6.1 d
7Time and claimsH2R9,33510,760-1,42533,33026,199+27%3.164%42.0 h
8Move and deliverM2D8,9387,296+1,64224,15620,278+19%3.383%2.1 d
9Incident deskITS5,7904,736+1,05424,62323,319+6%5.295%3.1 d
10Agent run deskAIO4,7353,901+83424,41519,396+26%6.390%2.8 d
11Model routingAIO4,0473,088+95920,81413,679+52%6.769%5.8 d
12Billing and creditO2C8,4546,764+1,69017,0704,953+245%2.592%34.0 h
13Service requestsITS4,6813,972+70921,89911,051+98%5.583%3.9 d
14Supplier operationsS2P5,3814,876+50522,56711,436+97%4.664%5.2 d
15Artwork studioC2L3,2252,481+74417,28410,553+64%7.070%4.1 d
16Change and accessITS4,5943,988+60616,98410,092+68%4.395%2.4 d
17FormulationC2L3,7703,486+28418,1529,861+84%5.293%2.9 d
18Employee lifecycleH2R5,0044,350+6549,3835,544+69%2.277%2.3 d
19Prompt and policyAIO3,4263,022+40410,2916,065+70%3.473%40.4 h
20Contract deskLGL4,8123,734+1,0784,5271,013+347%1.287%31.6 h
21Campaign briefingA2L4,9784,608+3707,4354,453+67%1.687%35.2 h
22Media operationsA2L2,2321,869+3637,4416,673+12%4.075%2.9 d
23Data qualityD&A2,6502,701-517,5505,119+47%2.879%3.8 d
24Sales and operations planningP2P1,7371,361+3765,6452,753+105%4.177%37.3 h
25Launch gatesC2L2,1291,819+3105,1954,054+28%2.971%2.8 d
26ReplenishmentP2P1,4031,152+2515,3361,917+178%4.684%40.8 h
27Trade promotionA2L2,7172,237+4804,0861,310+212%1.895%41.8 h
28Report certificationD&A1,7481,730+186,1523,652+68%3.673%3.7 d
29Metric governanceD&A1,7581,585+1735,3744,659+15%3.487%3.3 d
30Obligation managementLGL1,8301,825+55,8682,784+111%3.292%3.1 d
31Forecast deskP2P1,5961,571+255,4803,904+40%3.575%41.7 h
32ReconciliationR2R5,9695,707+2621,8391,238+49%0.395%9.7 h
33Close managementR2R2,8222,946-1242,8242,379+19%1.070%15.6 h
34Quality controlM2D1,3361,197+1391,044249+320%0.971%15.8 h
35Cash and collectionsO2C3,2473,096+151151127+19%0.064%17.5 h
36Matter managementLGL1,0651,199-1348091,266-36%0.784%32.5 h

"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

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

LGLContract desk4,527 standing against a normal of 1,013 · +347%
M2DQuality control1,044 standing against a normal of 249 · +320%
O2CBilling and credit17,070 standing against a normal of 4,953 · +245%
A2LTrade promotion4,086 standing against a normal of 1,310 · +212%
P2PReplenishment5,336 standing against a normal of 1,917 · +178%
LGLObligation management5,868 standing against a normal of 2,784 · +111%
P2PSales and operations planning5,645 standing against a normal of 2,753 · +105%
ITSService requests21,899 standing against a normal of 11,051 · +98%
S2PSupplier operations22,567 standing against a normal of 11,436 · +97%
R2RPostings desk35,627 standing against a normal of 18,079 · +97%
M2DMake and release33,141 standing against a normal of 17,486 · +90%
C2LFormulation18,152 standing against a normal of 9,861 · +84%

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

The commitment on the day
118,618 of 148,653 items served cleared inside commitment — 79.8%.

30,035 items cleared outside their commitment. They are spread across 36 queues, and the deepest single contributor is Time and claims with 3,827. 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.