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, Jan 18. 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, Jan 18
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 — 151,007 items standing and growing by 557 a day.

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

151,007
Standing
8.7%
Share of all standing work
3,359
Arrived on the day
2,802
Served on the day
+7%
Against its own normal
25.3 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,728,247 items standing · deepest is 151,007

■ 90%+ inside commitment■ 75 to 90%■ under 75%
S2PSource-to-Pay317,302 standing · 18.4% of the operation
Invoice processing
151,007+55725.3 d
Buying desk
111,026+1,09714.1 d
Supplier operations
55,269+33924.8 d
H2RHire-to-Retire245,494 standing · 14.2% of the operation
Time and claims
112,447+55115.7 d
Payroll operations
104,964+42023.9 d
Employee lifecycle
28,083+7797.8 d
O2COrder-to-Cash200,438 standing · 11.6% of the operation
Order desk
135,736+14038.5 d
Billing and credit
48,454+7855.2 d
Cash and collections
16,248+1627.6 d
ITSIT Service192,576 standing · 11.1% of the operation
Incident desk
80,208+15323.2 d
Change and access
59,116-25547.1 d
Service requests
53,252+60527.1 d
M2DMake-to-Deliver174,238 standing · 10.1% of the operation
Move and deliver
88,766-9138.1 d
Make and release
80,334-26353.9 d
Quality control
5,138+369.0 d
AIOAI Operations145,624 standing · 8.4% of the operation
Agent run desk
59,888+30636.1 d
Model routing
55,385+8144.8 d
Prompt and policy
30,351+41513.7 d
R2RRecord-to-Report130,882 standing · 7.6% of the operation
Postings desk
84,637+48518.6 d
Reconciliation
29,658-4049.0 d
Close management
16,587+13816.8 d
C2LConcept-to-Launch113,841 standing · 6.6% of the operation
Artwork studio
50,614+19026.4 d
Formulation
43,960+56321.0 d
Launch gates
19,267+19526.3 d
A2LAwareness-to-Lead70,016 standing · 4.1% of the operation
Campaign briefing
25,964+3884.1 d
Media operations
24,236+12622.5 d
Trade promotion
19,816+4836.9 d
D&AData and Analytics50,855 standing · 2.9% of the operation
Report certification
17,973+30422.1 d
Metric governance
17,441+9023.8 d
Data quality
15,441+2719.8 d
P2PPlan-to-Perform44,200 standing · 2.6% of the operation
Sales and operations planning
15,408+18027.3 d
Forecast desk
14,979+19519.3 d
Replenishment
13,813+10717.2 d
LGLLegal Operations42,781 standing · 2.5% of the operation
Contract desk
29,372-4210.9 d
Obligation management
7,656+1174.5 d
Matter management
5,753-3317.7 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,728,247 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

30 queues are taking on more than they clear

#QueueTowerArrivedServedNetStandingNormalvs normalDays of workInsideOldest
1Invoice processingS2P3,3592,802+557151,007140,938+7%53.984%25.3 d
2Order deskO2C2,3862,246+140135,736128,928+5%60.479%38.5 d
3Buying deskS2P3,8222,725+1,097111,02698,204+13%40.767%14.1 d
4Time and claimsH2R3,6473,096+551112,44784,781+33%36.391%15.7 d
5Payroll operationsH2R2,8622,442+420104,96486,830+21%43.078%23.9 d
6Move and deliverM2D2,0052,096-9188,76682,085+8%42.493%38.1 d
7Postings deskR2R2,8612,376+48584,63776,950+10%35.686%18.6 d
8Incident deskITS1,8661,713+15380,20870,732+13%46.863%23.2 d
9Make and releaseM2D1,4761,739-26380,33475,132+7%46.279%53.9 d
10Agent run deskAIO1,4091,103+30659,88858,183+3%54.371%36.1 d
11Change and accessITS1,3371,592-25559,11650,274+18%37.186%47.1 d
12Supplier operationsS2P1,7191,380+33955,26941,135+34%40.074%24.8 d
13Service requestsITS1,504899+60553,25241,158+29%59.273%27.1 d
14Model routingAIO1,2061,125+8155,38549,770+11%49.278%44.8 d
15Billing and creditO2C2,9342,149+78548,45436,876+31%22.570%5.2 d
16Artwork studioC2L902712+19050,61447,596+6%71.176%26.4 d
17FormulationC2L1,6501,087+56343,96034,383+28%40.464%21.0 d
18Prompt and policyAIO1,4651,050+41530,35126,649+14%28.990%13.7 d
19Employee lifecycleH2R1,614835+77928,08315,760+78%33.688%7.8 d
20ReconciliationR2R1,6642,068-40429,65822,645+31%14.378%9.0 d
21Contract deskLGL1,4121,454-4229,37220,742+42%20.263%10.9 d
22Campaign briefingA2L1,8671,479+38825,96416,887+54%17.666%4.1 d
23Media operationsA2L610484+12624,23622,985+5%50.165%22.5 d
24Trade promotionA2L1,024541+48319,81614,322+38%36.669%6.9 d
25Launch gatesC2L627432+19519,26715,231+26%44.663%26.3 d
26Report certificationD&A749445+30417,97315,335+17%40.465%22.1 d
27Metric governanceD&A528438+9017,44115,106+15%39.884%23.8 d
28Close managementR2R1,045907+13816,58714,941+11%18.391%16.8 d
29Cash and collectionsO2C991829+16216,24812,603+29%19.696%7.6 d
30Data qualityD&A1,127856+27115,4419,379+65%18.080%9.8 d
31Sales and operations planningP2P512332+18015,40813,302+16%46.483%27.3 d
32Forecast deskP2P625430+19514,97911,561+30%34.883%19.3 d
33ReplenishmentP2P519412+10713,81311,929+16%33.588%17.2 d
34Obligation managementLGL624507+1177,6565,191+47%15.192%4.5 d
35Matter managementLGL316349-335,7535,728+0%16.595%17.7 d
36Quality controlM2D376340+365,1385,019+2%15.194%9.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

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

H2REmployee lifecycle28,083 standing against a normal of 15,760 · +78%
D&AData quality15,441 standing against a normal of 9,379 · +65%
A2LCampaign briefing25,964 standing against a normal of 16,887 · +54%
LGLObligation management7,656 standing against a normal of 5,191 · +47%
LGLContract desk29,372 standing against a normal of 20,742 · +42%
A2LTrade promotion19,816 standing against a normal of 14,322 · +38%
S2PSupplier operations55,269 standing against a normal of 41,135 · +34%
H2RTime and claims112,447 standing against a normal of 84,781 · +33%
O2CBilling and credit48,454 standing against a normal of 36,876 · +31%
R2RReconciliation29,658 standing against a normal of 22,645 · +31%
P2PForecast desk14,979 standing against a normal of 11,561 · +30%
ITSService requests53,252 standing against a normal of 41,158 · +29%

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

The commitment on the day
35,814 of 45,470 items served cleared inside commitment — 78.8%.

9,656 items cleared outside their commitment. They are spread across 36 queues, and the deepest single contributor is Buying desk with 893. 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.