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 Fri, Feb 20. 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
Fri, Feb 20
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 — 179,436 items standing and growing by 1,883 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 1,883 more items a day than it clears, so the share is rising. At the day service rate of 10,854 items, and only if nothing else arrived, what is already standing in it is 16.5 days of work. Its oldest item has been waiting 6.4 d, and 1,489 of the 10,854 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.

179,436
Standing
8.0%
Share of all standing work
12,737
Arrived on the day
10,854
Served on the day
+15%
Against its own normal
6.4 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,242,262 items standing · deepest is 179,436

■ 90%+ inside commitment■ 75 to 90%■ under 75%
S2PSource-to-Pay384,623 standing · 17.2% of the operation
Invoice processing
179,436+1,8836.4 d
Buying desk
141,951+1,53712.0 d
Supplier operations
63,236+3043.1 d
H2RHire-to-Retire317,935 standing · 14.2% of the operation
Payroll operations
167,908+1,63412.5 d
Time and claims
123,537+7006.7 d
Employee lifecycle
26,490+854.1 d
ITSIT Service266,036 standing · 11.9% of the operation
Incident desk
103,500+1,30621.8 d
Change and access
85,526+29113.3 d
Service requests
77,010+1,22611.1 d
M2DMake-to-Deliver253,039 standing · 11.3% of the operation
Move and deliver
132,679+1,9988.4 d
Make and release
112,784+75714.2 d
Quality control
7,576+1734.0 d
O2COrder-to-Cash247,493 standing · 11.0% of the operation
Order desk
171,151+2,99912.5 d
Billing and credit
68,612+8343.7 d
Cash and collections
7,730-54428.4 h
AIOAI Operations210,698 standing · 9.4% of the operation
Agent run desk
90,312+2,1205.2 d
Model routing
81,244+609.4 d
Prompt and policy
39,142-1969.8 d
R2RRecord-to-Report164,484 standing · 7.3% of the operation
Postings desk
116,979+2,3228.4 d
Reconciliation
24,032-113.4 d
Close management
23,473+1992.4 d
C2LConcept-to-Launch161,021 standing · 7.2% of the operation
Artwork studio
69,871+80311.7 d
Formulation
68,268-22416.3 d
Launch gates
22,882+4283.0 d
A2LAwareness-to-Lead66,890 standing · 3.0% of the operation
Media operations
33,586+55510.3 d
Trade promotion
19,316+3285.6 d
Campaign briefing
13,988-41646.1 h
P2PPlan-to-Perform59,906 standing · 2.7% of the operation
Replenishment
22,520+3739.5 d
Sales and operations planning
21,792+21711.7 d
Forecast desk
15,594+178.3 d
LGLLegal Operations55,499 standing · 2.5% of the operation
Contract desk
33,720+8732.6 d
Obligation management
12,767+2216.5 d
Matter management
9,012+3588.3 d
D&AData and Analytics54,638 standing · 2.4% of the operation
Report certification
23,241+49110.8 d
Metric governance
18,459+195.2 d
Data quality
12,938-5873.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,242,262 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 processingS2P12,73710,854+1,883179,436156,530+15%16.586%6.4 d
2Order deskO2C10,1807,181+2,999171,151147,775+16%23.886%12.5 d
3Payroll operationsH2R9,4897,855+1,634167,908139,724+20%21.478%12.5 d
4Buying deskS2P9,4167,879+1,537141,951118,393+20%18.063%12.0 d
5Move and deliverM2D8,0496,051+1,998132,679107,500+23%21.970%8.4 d
6Postings deskR2R9,0756,753+2,322116,97996,332+21%17.383%8.4 d
7Time and claimsH2R11,33310,633+700123,537119,215+4%11.681%6.7 d
8Make and releaseM2D6,1875,430+757112,78496,514+17%20.884%14.2 d
9Incident deskITS5,2093,903+1,306103,50088,821+17%26.576%21.8 d
10Agent run deskAIO6,2614,141+2,12090,31271,529+26%21.873%5.2 d
11Change and accessITS5,1194,828+29185,52670,843+21%17.796%13.3 d
12Service requestsITS6,0394,813+1,22677,01067,522+14%16.069%11.1 d
13Model routingAIO3,9943,934+6081,24470,297+16%20.788%9.4 d
14Artwork studioC2L3,2642,461+80369,87159,374+18%28.471%11.7 d
15Billing and creditO2C8,1587,324+83468,61252,405+31%9.479%3.7 d
16FormulationC2L3,9424,166-22468,26859,093+16%16.482%16.3 d
17Supplier operationsS2P6,1825,878+30463,23662,244+2%10.871%3.1 d
18Prompt and policyAIO3,6923,888-19639,14236,242+8%10.169%9.8 d
19Contract deskLGL5,3254,452+87333,72030,613+10%7.682%2.6 d
20Media operationsA2L2,4001,845+55533,58627,415+23%18.269%10.3 d
21Employee lifecycleH2R5,3605,275+8526,49028,802-8%5.068%4.1 d
22Report certificationD&A2,0961,605+49123,24118,917+23%14.577%10.8 d
23Launch gatesC2L2,4332,005+42822,88222,139+3%11.463%3.0 d
24Close managementR2R3,5263,327+19923,47320,824+13%7.169%2.4 d
25ReplenishmentP2P1,7931,420+37322,52018,461+22%15.989%9.5 d
26ReconciliationR2R6,5326,543-1124,03225,688-6%3.795%3.4 d
27Sales and operations planningP2P1,6531,436+21721,79218,368+19%15.273%11.7 d
28Trade promotionA2L2,7312,403+32819,31618,720+3%8.088%5.6 d
29Metric governanceD&A1,5461,527+1918,45917,122+8%12.163%5.2 d
30Forecast deskP2P1,6861,669+1715,59415,762-1%9.391%8.3 d
31Campaign briefingA2L5,3155,731-41613,98818,325-24%2.489%46.1 h
32Obligation managementLGL2,3262,105+22112,76711,216+14%6.164%6.5 d
33Data qualityD&A2,8303,417-58712,93815,213-15%3.872%3.9 d
34Matter managementLGL1,255897+3589,0126,924+30%10.094%8.3 d
35Quality controlM2D1,2391,066+1737,5765,930+28%7.165%4.0 d
36Cash and collectionsO2C3,1273,671-5447,73012,018-36%2.164%28.4 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

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

O2CBilling and credit68,612 standing against a normal of 52,405 · +31%
LGLMatter management9,012 standing against a normal of 6,924 · +30%
M2DQuality control7,576 standing against a normal of 5,930 · +28%
AIOAgent run desk90,312 standing against a normal of 71,529 · +26%
M2DMove and deliver132,679 standing against a normal of 107,500 · +23%
D&AReport certification23,241 standing against a normal of 18,917 · +23%
A2LMedia operations33,586 standing against a normal of 27,415 · +23%
P2PReplenishment22,520 standing against a normal of 18,461 · +22%
R2RPostings desk116,979 standing against a normal of 96,332 · +21%
ITSChange and access85,526 standing against a normal of 70,843 · +21%
H2RPayroll operations167,908 standing against a normal of 139,724 · +20%
S2PBuying desk141,951 standing against a normal of 118,393 · +20%

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

The commitment on the day
124,149 of 158,366 items served cleared inside commitment — 78.4%.

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