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, Jan 19. 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, Jan 19
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,591 items standing and growing by 584 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 584 more items a day than it clears, so the share is rising. At the day service rate of 11,454 items, and only if nothing else arrived, what is already standing in it is 13.2 days of work. Its oldest item has been waiting 8.7 d, and 866 of the 11,454 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,591
Standing
8.7%
Share of all standing work
12,038
Arrived on the day
11,454
Served on the day
+7%
Against its own normal
8.7 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,738,009 items standing · deepest is 151,591

■ 90%+ inside commitment■ 75 to 90%■ under 75%
S2PSource-to-Pay318,997 standing · 18.4% of the operation
Invoice processing
151,591+5848.7 d
Buying desk
111,080+547.4 d
Supplier operations
56,326+1,0574.3 d
H2RHire-to-Retire250,429 standing · 14.4% of the operation
Time and claims
115,471+3,0248.3 d
Payroll operations
105,696+7324.1 d
Employee lifecycle
29,262+1,1795.7 d
O2COrder-to-Cash200,836 standing · 11.6% of the operation
Order desk
135,842+1068.3 d
Billing and credit
48,868+4143.8 d
Cash and collections
16,126-12243.4 h
ITSIT Service193,659 standing · 11.1% of the operation
Incident desk
80,325+1176.1 d
Change and access
59,388+2725.3 d
Service requests
53,946+6943.0 d
M2DMake-to-Deliver173,992 standing · 10.0% of the operation
Move and deliver
87,573-1,19311.5 d
Make and release
81,534+1,20012.3 d
Quality control
4,885-2534.9 d
AIOAI Operations146,043 standing · 8.4% of the operation
Agent run desk
59,789-998.2 d
Model routing
56,447+1,06212.1 d
Prompt and policy
29,807-5448.7 d
R2RRecord-to-Report130,291 standing · 7.5% of the operation
Postings desk
84,250-3879.6 d
Reconciliation
29,713+555.4 d
Close management
16,328-2594.8 d
C2LConcept-to-Launch116,073 standing · 6.7% of the operation
Artwork studio
50,919+3057.7 d
Formulation
45,273+1,3139.7 d
Launch gates
19,881+6148.7 d
A2LAwareness-to-Lead68,769 standing · 4.0% of the operation
Campaign briefing
25,003-9615.0 d
Media operations
23,989-24710.4 d
Trade promotion
19,777-396.6 d
D&AData and Analytics51,078 standing · 2.9% of the operation
Report certification
18,077+1047.1 d
Metric governance
17,368-739.7 d
Data quality
15,633+1924.5 d
P2PPlan-to-Perform44,474 standing · 2.6% of the operation
Sales and operations planning
15,275-1338.4 d
Forecast desk
15,168+1898.0 d
Replenishment
14,031+2185.9 d
LGLLegal Operations43,368 standing · 2.5% of the operation
Contract desk
29,290-826.8 d
Obligation management
8,261+6053.1 d
Matter management
5,817+643.2 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,738,009 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 processingS2P12,03811,454+584151,591142,262+7%13.292%8.7 d
2Order deskO2C9,5199,413+106135,842129,634+5%14.488%8.3 d
3Time and claimsH2R11,4538,429+3,024115,47187,152+32%13.786%8.3 d
4Buying deskS2P8,7968,742+54111,08099,387+12%12.790%7.4 d
5Payroll operationsH2R8,2137,481+732105,69687,917+20%14.177%4.1 d
6Move and deliverM2D7,3418,534-1,19387,57382,652+6%10.383%11.5 d
7Make and releaseM2D6,4685,268+1,20081,53475,710+8%15.594%12.3 d
8Postings deskR2R8,4588,845-38784,25078,027+8%9.581%9.6 d
9Incident deskITS5,2865,169+11780,32571,564+12%15.587%6.1 d
10Model routingAIO4,6493,587+1,06256,44750,074+13%15.777%12.1 d
11Supplier operationsS2P5,5334,476+1,05756,32642,212+33%12.666%4.3 d
12Change and accessITS5,5815,309+27259,38851,165+16%11.283%5.3 d
13Agent run deskAIO4,9585,057-9959,78958,416+2%11.881%8.2 d
14Service requestsITS5,3074,613+69453,94642,000+28%11.793%3.0 d
15Artwork studioC2L3,2622,957+30550,91947,847+6%17.286%7.7 d
16FormulationC2L4,7373,424+1,31345,27334,994+29%13.267%9.7 d
17Billing and creditO2C9,3248,910+41448,86838,088+28%5.574%3.8 d
18Employee lifecycleH2R4,9663,787+1,17929,26216,701+75%7.770%5.7 d
19ReconciliationR2R5,6715,616+5529,71323,443+27%5.387%5.4 d
20Prompt and policyAIO3,1123,656-54429,80727,025+10%8.296%8.7 d
21Contract deskLGL4,1144,196-8229,29021,434+37%7.063%6.8 d
22Campaign briefingA2L4,4225,383-96125,00317,715+41%4.678%5.0 d
23Media operationsA2L1,9352,182-24723,98923,134+4%11.078%10.4 d
24Launch gatesC2L2,2691,655+61419,88115,471+29%12.070%8.7 d
25Trade promotionA2L2,4372,476-3919,77714,754+34%8.082%6.6 d
26Report certificationD&A2,0871,983+10418,07715,601+16%9.193%7.1 d
27Metric governanceD&A1,6441,717-7317,36815,321+13%10.168%9.7 d
28Data qualityD&A2,9742,782+19215,6339,850+59%5.686%4.5 d
29Close managementR2R2,6452,904-25916,32815,065+8%5.688%4.8 d
30Cash and collectionsO2C2,7252,847-12216,12612,964+24%5.786%43.4 h
31Forecast deskP2P1,6171,428+18915,16811,837+28%10.694%8.0 d
32Sales and operations planningP2P1,4661,599-13315,27513,520+13%9.672%8.4 d
33ReplenishmentP2P1,6551,437+21814,03112,046+16%9.872%5.9 d
34Obligation managementLGL2,1701,565+6058,2615,374+54%5.381%3.1 d
35Matter managementLGL1,2091,145+645,8175,765+1%5.175%3.2 d
36Quality controlM2D1,0981,351-2534,8855,034-3%3.666%4.9 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

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

H2REmployee lifecycle29,262 standing against a normal of 16,701 · +75%
D&AData quality15,633 standing against a normal of 9,850 · +59%
LGLObligation management8,261 standing against a normal of 5,374 · +54%
A2LCampaign briefing25,003 standing against a normal of 17,715 · +41%
LGLContract desk29,290 standing against a normal of 21,434 · +37%
A2LTrade promotion19,777 standing against a normal of 14,754 · +34%
S2PSupplier operations56,326 standing against a normal of 42,212 · +33%
H2RTime and claims115,471 standing against a normal of 87,152 · +32%
C2LFormulation45,273 standing against a normal of 34,994 · +29%
C2LLaunch gates19,881 standing against a normal of 15,471 · +29%
ITSService requests53,946 standing against a normal of 42,000 · +28%
O2CBilling and credit48,868 standing against a normal of 38,088 · +28%

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

The commitment on the day
133,059 of 161,377 items served cleared inside commitment — 82.5%.

28,318 items cleared outside their commitment. They are spread across 36 queues, and the deepest single contributor is Billing and credit with 2,274. 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.