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, Apr 5. 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, Apr 5
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 — 242,910 items standing and growing by 490 a day.

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

242,910
Standing
9.1%
Share of all standing work
3,222
Arrived on the day
2,732
Served on the day
+2%
Against its own normal
71.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 · 2,680,543 items standing · deepest is 242,910

■ 90%+ inside commitment■ 75 to 90%■ under 75%
S2PSource-to-Pay481,889 standing · 18.0% of the operation
Invoice processing
242,910+49071.7 d
Buying desk
162,437+1,06249.3 d
Supplier operations
76,542-3162.0 d
H2RHire-to-Retire363,148 standing · 13.5% of the operation
Payroll operations
170,183+47335.9 d
Time and claims
162,131+63444.8 d
Employee lifecycle
30,834+30814.6 d
ITSIT Service323,017 standing · 12.1% of the operation
Incident desk
139,817+24470.0 d
Change and access
99,743+47565.2 d
Service requests
83,457+64444.0 d
O2COrder-to-Cash312,711 standing · 11.7% of the operation
Order desk
212,785+3840.3 d
Billing and credit
77,926+11312.9 d
Cash and collections
22,000+54811.7 d
M2DMake-to-Deliver282,205 standing · 10.5% of the operation
Move and deliver
139,939+94143.4 d
Make and release
135,177+94048.1 d
Quality control
7,089+3213.9 d
AIOAI Operations234,136 standing · 8.7% of the operation
Agent run desk
102,404+19539.5 d
Model routing
85,488+27936.7 d
Prompt and policy
46,244+27019.6 d
R2RRecord-to-Report203,013 standing · 7.6% of the operation
Postings desk
130,423+1,08826.6 d
Reconciliation
46,570+74517.8 d
Close management
26,020+55318.7 d
C2LConcept-to-Launch182,089 standing · 6.8% of the operation
Artwork studio
84,279+25755.4 d
Formulation
71,095+7966.2 d
Launch gates
26,715-19421.9 d
A2LAwareness-to-Lead89,458 standing · 3.3% of the operation
Media operations
40,347+7624.8 d
Campaign briefing
28,151+3699.5 d
Trade promotion
20,960+1417.8 d
P2PPlan-to-Perform74,578 standing · 2.8% of the operation
Sales and operations planning
26,692+8856.7 d
Replenishment
24,315-2743.9 d
Forecast desk
23,571-6114.8 d
D&AData and Analytics71,461 standing · 2.7% of the operation
Metric governance
27,076+24430.9 d
Report certification
25,814-8016.2 d
Data quality
18,571+227.4 d
LGLLegal Operations62,838 standing · 2.3% of the operation
Contract desk
41,890+50511.2 d
Obligation management
11,469+9014.0 d
Matter management
9,479+7615.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 2,680,543 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

31 queues are taking on more than they clear

#QueueTowerArrivedServedNetStandingNormalvs normalDays of workInsideOldest
1Invoice processingS2P3,2222,732+490242,910238,511+2%88.980%71.7 d
2Order deskO2C2,8452,807+38212,785214,837-1%75.866%40.3 d
3Payroll operationsH2R2,5222,049+473170,183172,489-1%83.164%35.9 d
4Buying deskS2P2,8691,807+1,062162,437155,781+4%89.972%49.3 d
5Time and claimsH2R3,1042,470+634162,131149,883+8%65.673%44.8 d
6Move and deliverM2D2,3821,441+941139,939143,687-3%97.178%43.4 d
7Incident deskITS1,5091,265+244139,817133,268+5%110.565%70.0 d
8Make and releaseM2D2,2501,310+940135,177125,788+7%103.292%48.1 d
9Postings deskR2R2,9101,822+1,088130,423126,355+3%71.672%26.6 d
10Agent run deskAIO1,8671,672+195102,404105,087-3%61.272%39.5 d
11Change and accessITS1,5611,086+47599,74393,203+7%91.896%65.2 d
12Model routingAIO1,4891,210+27985,48884,265+1%70.783%36.7 d
13Service requestsITS1,9441,300+64483,45782,252+1%64.286%44.0 d
14Artwork studioC2L1,2661,009+25784,27984,300-0%83.566%55.4 d
15Billing and creditO2C1,8531,740+11377,92673,076+7%44.884%12.9 d
16Supplier operationsS2P1,3341,365-3176,54272,540+6%56.191%62.0 d
17FormulationC2L1,0911,012+7971,09568,895+3%70.397%66.2 d
18ReconciliationR2R1,9861,241+74546,57043,360+7%37.582%17.8 d
19Prompt and policyAIO1,3281,058+27046,24446,348-0%43.763%19.6 d
20Contract deskLGL1,6161,111+50541,89046,447-10%37.795%11.2 d
21Media operationsA2L700624+7640,34740,609-1%64.767%24.8 d
22Employee lifecycleH2R1,174866+30830,83429,674+4%35.688%14.6 d
23Campaign briefingA2L1,5171,148+36928,15128,572-1%24.585%9.5 d
24Close managementR2R1,079526+55326,02024,569+6%49.566%18.7 d
25Metric governanceD&A595351+24427,07625,526+6%77.190%30.9 d
26Sales and operations planningP2P462374+8826,69224,983+7%71.475%56.7 d
27Launch gatesC2L558752-19426,71528,418-6%35.587%21.9 d
28Report certificationD&A434514-8025,81427,027-4%50.291%16.2 d
29Cash and collectionsO2C1,174626+54822,00019,099+15%35.186%11.7 d
30ReplenishmentP2P442469-2724,31526,568-8%51.896%43.9 d
31Forecast deskP2P423484-6123,57121,626+9%48.795%14.8 d
32Trade promotionA2L820679+14120,96024,869-16%30.977%7.8 d
33Data qualityD&A845823+2218,57116,544+12%22.682%7.4 d
34Obligation managementLGL592502+9011,46912,941-11%22.884%14.0 d
35Matter managementLGL306230+769,4799,511-0%41.276%15.5 d
36Quality controlM2D349317+327,0898,916-20%22.492%13.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

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

O2CCash and collections22,000 standing against a normal of 19,099 · +15%
D&AData quality18,571 standing against a normal of 16,544 · +12%
The commitment on the day
32,105 of 40,792 items served cleared inside commitment — 78.7%.

8,687 items cleared outside their commitment. They are spread across 36 queues, and the deepest single contributor is Order desk with 958. 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.