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, May 22. 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, May 22
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 — 231,129 items standing and growing by 1,134 a day.

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

231,129
Standing
8.9%
Share of all standing work
11,105
Arrived on the day
9,971
Served on the day
+1%
Against its own normal
7.8 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,593,065 items standing · deepest is 231,129

■ 90%+ inside commitment■ 75 to 90%■ under 75%
S2PSource-to-Pay456,501 standing · 17.6% of the operation
Invoice processing
231,129+1,1347.8 d
Buying desk
163,788-97816.3 d
Supplier operations
61,584-4476.7 d
H2RHire-to-Retire370,599 standing · 14.3% of the operation
Payroll operations
204,236+51511.7 d
Time and claims
138,588-77412.1 d
Employee lifecycle
27,775-5505.4 d
ITSIT Service331,250 standing · 12.8% of the operation
Incident desk
139,318+10724.6 d
Change and access
101,053-47414.6 d
Service requests
90,879-75712.9 d
M2DMake-to-Deliver305,497 standing · 11.8% of the operation
Move and deliver
153,841-1,11617.8 d
Make and release
143,970+1916.8 d
Quality control
7,686-597.3 d
O2COrder-to-Cash278,008 standing · 10.7% of the operation
Order desk
210,219+6278.4 d
Billing and credit
60,941-1,0507.8 d
Cash and collections
6,848-70325.2 h
AIOAI Operations246,881 standing · 9.5% of the operation
Agent run desk
112,563-1387.2 d
Model routing
90,330-1,16922.2 d
Prompt and policy
43,988-42915.9 d
C2LConcept-to-Launch191,668 standing · 7.4% of the operation
Artwork studio
89,971-16833.8 d
Formulation
78,120-54411.2 d
Launch gates
23,577-5489.6 d
R2RRecord-to-Report157,455 standing · 6.1% of the operation
Postings desk
122,343-71019.2 d
Close management
18,345-6355.6 d
Reconciliation
16,767-7023.3 d
P2PPlan-to-Perform73,351 standing · 2.8% of the operation
Sales and operations planning
27,619-26517.2 d
Replenishment
25,962-866.4 d
Forecast desk
19,770-2005.3 d
A2LAwareness-to-Lead66,170 standing · 2.6% of the operation
Media operations
42,925-1046.9 d
Trade promotion
17,666-9175.2 d
Campaign briefing
5,579-71233.6 h
LGLLegal Operations60,366 standing · 2.3% of the operation
Contract desk
38,385-1,6513.1 d
Obligation management
12,698-2635.1 d
Matter management
9,283-10110.0 d
D&AData and Analytics55,319 standing · 2.1% of the operation
Metric governance
24,787+7616.9 d
Report certification
24,310-3804.3 d
Data quality
6,222-30530.2 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 2,593,065 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

6 queues are taking on more than they clear

#QueueTowerArrivedServedNetStandingNormalvs normalDays of workInsideOldest
1Invoice processingS2P11,1059,971+1,134231,129229,821+1%23.275%7.8 d
2Order deskO2C7,4516,824+627210,219204,636+3%30.893%8.4 d
3Payroll operationsH2R8,5097,994+515204,236201,642+1%25.588%11.7 d
4Buying deskS2P8,3889,366-978163,788176,521-7%17.577%16.3 d
5Move and deliverM2D7,4608,576-1,116153,841165,778-7%17.966%17.8 d
6Make and releaseM2D5,6105,591+19143,970141,338+2%25.865%16.8 d
7Incident deskITS4,7484,641+107139,318139,249+0%30.065%24.6 d
8Time and claimsH2R9,36010,134-774138,588161,402-14%13.774%12.1 d
9Postings deskR2R6,0636,773-710122,343132,184-7%18.186%19.2 d
10Agent run deskAIO4,2574,395-138112,563107,154+5%25.690%7.2 d
11Change and accessITS4,4014,875-474101,05398,231+3%20.776%14.6 d
12Service requestsITS4,5065,263-75790,87996,585-6%17.363%12.9 d
13Model routingAIO3,3144,483-1,16990,33095,854-6%20.174%22.2 d
14Artwork studioC2L2,7902,958-16889,97187,602+3%30.466%33.8 d
15FormulationC2L3,9134,457-54478,12082,875-6%17.578%11.2 d
16Supplier operationsS2P4,9145,361-44761,58469,481-11%11.572%6.7 d
17Billing and creditO2C6,5017,551-1,05060,94161,550-1%8.194%7.8 d
18Prompt and policyAIO2,7993,228-42943,98848,070-8%13.684%15.9 d
19Media operationsA2L1,8001,904-10442,92542,647+1%22.596%6.9 d
20Contract deskLGL3,7335,384-1,65138,38545,328-15%7.180%3.1 d
21Employee lifecycleH2R4,0454,595-55027,77536,853-25%6.086%5.4 d
22Sales and operations planningP2P1,3301,595-26527,61926,840+3%17.386%17.2 d
23ReplenishmentP2P1,2731,359-8625,96224,525+6%19.194%6.4 d
24Metric governanceD&A1,4131,337+7624,78725,427-3%18.568%16.9 d
25Report certificationD&A1,8472,227-38024,31028,175-14%10.980%4.3 d
26Launch gatesC2L1,6662,214-54823,57726,603-11%10.677%9.6 d
27Forecast deskP2P1,3581,558-20019,77021,294-7%12.779%5.3 d
28Close managementR2R2,4593,094-63518,34522,942-20%5.962%5.6 d
29Trade promotionA2L2,2223,139-91717,66622,526-22%5.672%5.2 d
30ReconciliationR2R4,6365,338-70216,76724,287-31%3.171%3.3 d
31Obligation managementLGL1,6151,878-26312,69813,299-5%6.885%5.1 d
32Matter managementLGL9861,087-1019,28310,703-13%8.577%10.0 d
33Quality controlM2D1,1411,200-597,6866,942+11%6.480%7.3 d
34Cash and collectionsO2C2,6733,376-7036,84814,205-52%2.065%25.2 h
35Data qualityD&A2,5662,871-3056,22212,878-52%2.263%30.2 h
36Campaign briefingA2L4,2935,005-7125,57912,226-54%1.192%33.6 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

1 queue is more than ten percent above their own 27 day mean

M2DQuality control7,686 standing against a normal of 6,942 · +11%
The commitment on the day
125,523 of 161,602 items served cleared inside commitment — 77.7%.

36,079 items cleared outside their commitment. They are spread across 36 queues, and the deepest single contributor is Move and deliver with 2,915. 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.