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, Dec 29. 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, Dec 29
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 — 133,048 items standing and growing by 3,350 a day.

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

133,048
Standing
9.9%
Share of all standing work
13,233
Arrived on the day
9,883
Served on the day
+38%
Against its own normal
6.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,344,052 items standing · deepest is 133,048

■ 90%+ inside commitment■ 75 to 90%■ under 75%
S2PSource-to-Pay257,748 standing · 19.2% of the operation
Invoice processing
133,048+3,3506.7 d
Buying desk
89,866+1,3846.7 d
Supplier operations
34,834+2,2342.0 d
O2COrder-to-Cash164,290 standing · 12.2% of the operation
Order desk
124,841+1,4525.4 d
Billing and credit
29,478+7173.1 d
Cash and collections
9,971+6372.3 d
H2RHire-to-Retire158,751 standing · 11.8% of the operation
Payroll operations
81,589+2,1126.6 d
Time and claims
69,105+4,4896.1 d
Employee lifecycle
8,057+67941.6 h
M2DMake-to-Deliver157,310 standing · 11.7% of the operation
Move and deliver
79,022+1,3178.9 d
Make and release
73,155+1,46110.1 d
Quality control
5,133+3084.4 d
ITSIT Service145,868 standing · 10.9% of the operation
Incident desk
65,921+1,1185.2 d
Change and access
44,098+1,3434.2 d
Service requests
35,849+1,3084.7 d
AIOAI Operations129,128 standing · 9.6% of the operation
Agent run desk
56,687+1,0044.5 d
Model routing
47,857-2718.3 d
Prompt and policy
24,584+7816.7 d
R2RRecord-to-Report103,378 standing · 7.7% of the operation
Postings desk
70,411+2,8543.7 d
Reconciliation
18,689+1,8902.3 d
Close management
14,278-5104.9 d
C2LConcept-to-Launch90,197 standing · 6.7% of the operation
Artwork studio
46,259+4054.4 d
Formulation
30,391+1,0936.8 d
Launch gates
13,547-1095.6 d
A2LAwareness-to-Lead43,360 standing · 3.2% of the operation
Media operations
22,376+5011.5 d
Trade promotion
10,963+30135.8 h
Campaign briefing
10,021+94346.5 h
D&AData and Analytics34,274 standing · 2.6% of the operation
Report certification
14,019+4985.3 d
Metric governance
13,934+4413.9 d
Data quality
6,321+8402.3 d
P2PPlan-to-Perform33,361 standing · 2.5% of the operation
Sales and operations planning
11,880+1305.3 d
Replenishment
11,262+2636.4 d
Forecast desk
10,219+2973.7 d
LGLLegal Operations26,387 standing · 2.0% of the operation
Contract desk
16,560+1,67134.1 h
Matter management
5,734+2302.7 d
Obligation management
4,093+48320.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 1,344,052 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

33 queues are taking on more than they clear

#QueueTowerArrivedServedNetStandingNormalvs normalDays of workInsideOldest
1Invoice processingS2P13,2339,883+3,350133,04896,374+38%13.572%6.7 d
2Order deskO2C10,7809,328+1,452124,841104,415+20%13.482%5.4 d
3Buying deskS2P10,1108,726+1,38489,86666,088+36%10.380%6.7 d
4Payroll operationsH2R10,3998,287+2,11281,58972,359+13%9.889%6.6 d
5Time and claimsH2R12,3837,894+4,48969,10541,286+67%8.895%6.1 d
6Move and deliverM2D9,2587,941+1,31779,02264,607+22%10.096%8.9 d
7Postings deskR2R8,8045,950+2,85470,41145,589+54%11.872%3.7 d
8Make and releaseM2D6,2464,785+1,46173,15554,729+34%15.397%10.1 d
9Incident deskITS5,2644,146+1,11865,92149,779+32%15.971%5.2 d
10Agent run deskAIO6,0395,035+1,00456,68750,669+12%11.365%4.5 d
11Change and accessITS6,0404,697+1,34344,09830,815+43%9.490%4.2 d
12Artwork studioC2L4,0283,623+40546,25939,851+16%12.862%4.4 d
13Model routingAIO4,2554,526-27147,85744,010+9%10.669%8.3 d
14Supplier operationsS2P6,3984,164+2,23434,83424,132+44%8.494%2.0 d
15Service requestsITS6,3074,999+1,30835,84928,972+24%7.264%4.7 d
16FormulationC2L4,8793,786+1,09330,39126,871+13%8.093%6.8 d
17Billing and creditO2C7,9017,184+71729,47814,588+102%4.174%3.1 d
18Prompt and policyAIO3,9263,145+78124,58416,576+48%7.888%6.7 d
19ReconciliationR2R6,9915,101+1,89018,6895,310+252%3.769%2.3 d
20Contract deskLGL5,3753,704+1,67116,56012,399+34%4.571%34.1 h
21Media operationsA2L2,0812,031+5022,37617,900+25%11.078%11.5 d
22Report certificationD&A2,1551,657+49814,0198,984+56%8.594%5.3 d
23Metric governanceD&A1,7621,321+44113,9349,685+44%10.569%3.9 d
24Campaign briefingA2L4,8283,885+94310,0212,263+343%2.676%46.5 h
25Close managementR2R2,8433,353-51014,27811,170+28%4.389%4.9 d
26Launch gatesC2L1,9962,105-10913,54712,131+12%6.473%5.6 d
27Cash and collectionsO2C3,2892,652+6379,9713,687+170%3.884%2.3 d
28ReplenishmentP2P1,9171,654+26311,26210,350+9%6.874%6.4 d
29Sales and operations planningP2P1,6061,476+13011,8807,991+49%8.074%5.3 d
30Trade promotionA2L2,6112,310+30110,9638,274+33%4.764%35.8 h
31Forecast deskP2P1,5501,253+29710,2196,724+52%8.296%3.7 d
32Employee lifecycleH2R4,5433,864+6798,0571,988+305%2.179%41.6 h
33Data qualityD&A3,1922,352+8406,3212,522+151%2.781%2.3 d
34Matter managementLGL1,2301,000+2305,7343,992+44%5.794%2.7 d
35Quality controlM2D1,4481,140+3085,1334,159+23%4.578%4.4 d
36Obligation managementLGL2,3741,891+4834,0933,894+5%2.291%20.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

A2LCampaign briefing10,021 standing against a normal of 2,263 · +343%
H2REmployee lifecycle8,057 standing against a normal of 1,988 · +305%
R2RReconciliation18,689 standing against a normal of 5,310 · +252%
O2CCash and collections9,971 standing against a normal of 3,687 · +170%
D&AData quality6,321 standing against a normal of 2,522 · +151%
O2CBilling and credit29,478 standing against a normal of 14,588 · +102%
H2RTime and claims69,105 standing against a normal of 41,286 · +67%
D&AReport certification14,019 standing against a normal of 8,984 · +56%
R2RPostings desk70,411 standing against a normal of 45,589 · +54%
P2PForecast desk10,219 standing against a normal of 6,724 · +52%
P2PSales and operations planning11,880 standing against a normal of 7,991 · +49%
AIOPrompt and policy24,584 standing against a normal of 16,576 · +48%

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

The commitment on the day
120,991 of 150,848 items served cleared inside commitment — 80.2%.

29,857 items cleared outside their commitment. They are spread across 36 queues, and the deepest single contributor is Invoice processing with 2,799. 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.