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 Sat, May 16. 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
Sat, May 16
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,604 items standing and growing by 743 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 743 more items a day than it clears, so the share is rising. At the day service rate of 2,570 items, and only if nothing else arrived, what is already standing in it is 90.1 days of work. Its oldest item has been waiting 50.8 d, and 618 of the 2,570 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,604
Standing
8.7%
Share of all standing work
3,313
Arrived on the day
2,570
Served on the day
+1%
Against its own normal
50.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,670,435 items standing · deepest is 231,604

■ 90%+ inside commitment■ 75 to 90%■ under 75%
S2PSource-to-Pay463,793 standing · 17.4% of the operation
Invoice processing
231,604+74350.8 d
Buying desk
167,694+86838.5 d
Supplier operations
64,495-74831.1 d
H2RHire-to-Retire386,611 standing · 14.5% of the operation
Payroll operations
203,123+35460.8 d
Time and claims
150,345+43644.0 d
Employee lifecycle
33,143-17524.8 d
ITSIT Service335,410 standing · 12.6% of the operation
Incident desk
138,104-30241.3 d
Change and access
101,589+39418.9 d
Service requests
95,717-18857.8 d
M2DMake-to-Deliver316,165 standing · 11.8% of the operation
Move and deliver
163,610+78742.9 d
Make and release
144,794+82431.2 d
Quality control
7,761+10210.0 d
O2COrder-to-Cash277,260 standing · 10.4% of the operation
Order desk
206,677+1,04325.0 d
Billing and credit
59,953+5410.4 d
Cash and collections
10,630-29010.3 d
AIOAI Operations252,908 standing · 9.5% of the operation
Agent run desk
110,648+11076.9 d
Model routing
95,480+19252.3 d
Prompt and policy
46,780-34548.6 d
C2LConcept-to-Launch196,474 standing · 7.4% of the operation
Artwork studio
89,152+28445.2 d
Formulation
81,466+58652.0 d
Launch gates
25,856+6338.3 d
R2RRecord-to-Report165,208 standing · 6.2% of the operation
Postings desk
125,611-4457.3 d
Reconciliation
19,984-757.9 d
Close management
19,613-1413.5 d
A2LAwareness-to-Lead73,958 standing · 2.8% of the operation
Media operations
43,268-4922.2 d
Trade promotion
21,281-11127.7 d
Campaign briefing
9,409-6558.0 d
P2PPlan-to-Perform73,608 standing · 2.8% of the operation
Sales and operations planning
28,057+9234.9 d
Replenishment
25,346-9666.5 d
Forecast desk
20,205-9844.2 d
LGLLegal Operations67,844 standing · 2.5% of the operation
Contract desk
43,936+56121.7 d
Obligation management
13,898-21419.9 d
Matter management
10,010-831.2 d
D&AData and Analytics61,196 standing · 2.3% of the operation
Report certification
26,725-7340.3 d
Metric governance
24,987+9421.6 d
Data quality
9,484+1333.4 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,670,435 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

19 queues are taking on more than they clear

#QueueTowerArrivedServedNetStandingNormalvs normalDays of workInsideOldest
1Invoice processingS2P3,3132,570+743231,604230,190+1%90.176%50.8 d
2Order deskO2C2,7121,669+1,043206,677203,323+2%123.897%25.0 d
3Payroll operationsH2R2,4242,070+354203,123197,553+3%98.185%60.8 d
4Buying deskS2P2,8021,934+868167,694179,782-7%86.777%38.5 d
5Move and deliverM2D2,6191,832+787163,610165,300-1%89.378%42.9 d
6Time and claimsH2R3,2232,787+436150,345167,458-10%53.975%44.0 d
7Make and releaseM2D1,9821,158+824144,794139,182+4%125.076%31.2 d
8Incident deskITS1,1661,468-302138,104139,603-1%94.174%41.3 d
9Postings deskR2R2,0412,085-44125,611136,141-8%60.295%57.3 d
10Agent run deskAIO1,4121,302+110110,648104,618+6%85.063%76.9 d
11Change and accessITS1,4961,102+394101,58996,863+5%92.289%18.9 d
12Model routingAIO1,110918+19295,48095,651-0%104.065%52.3 d
13Service requestsITS1,2951,483-18895,71796,274-1%64.575%57.8 d
14Artwork studioC2L919635+28489,15286,535+3%140.496%45.2 d
15FormulationC2L1,470884+58681,46682,768-2%92.288%52.0 d
16Supplier operationsS2P1,2371,985-74864,49572,473-11%32.589%31.1 d
17Billing and creditO2C1,7631,709+5459,95363,568-6%35.195%10.4 d
18Prompt and policyAIO8481,193-34546,78048,222-3%39.286%48.6 d
19Contract deskLGL1,5801,019+56143,93645,489-3%43.163%21.7 d
20Media operationsA2L561610-4943,26842,117+3%70.970%22.2 d
21Employee lifecycleH2R1,0971,272-17533,14338,071-13%26.167%24.8 d
22Sales and operations planningP2P466374+9228,05726,369+6%75.093%34.9 d
23Report certificationD&A554627-7326,72528,792-7%42.679%40.3 d
24Launch gatesC2L600537+6325,85626,720-3%48.196%38.3 d
25Metric governanceD&A397303+9424,98725,725-3%82.576%21.6 d
26ReplenishmentP2P358454-9625,34623,901+6%55.882%66.5 d
27Trade promotionA2L565676-11121,28122,869-7%31.565%27.7 d
28Forecast deskP2P361459-9820,20521,911-8%44.093%44.2 d
29ReconciliationR2R1,3431,418-7519,98427,259-27%14.187%7.9 d
30Close managementR2R927941-1419,61324,615-20%20.872%13.5 d
31Obligation managementLGL448662-21413,89812,628+10%21.076%19.9 d
32Cash and collectionsO2C8821,172-29010,63016,464-35%9.177%10.3 d
33Data qualityD&A964831+1339,48415,003-37%11.488%3.4 d
34Matter managementLGL289297-810,01010,927-8%33.768%31.2 d
35Campaign briefingA2L1,0381,693-6559,40914,576-35%5.685%8.0 d
36Quality controlM2D395293+1027,7616,467+20%26.588%10.0 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

M2DQuality control7,761 standing against a normal of 6,467 · +20%
LGLObligation management13,898 standing against a normal of 12,628 · +10%
The commitment on the day
34,315 of 42,422 items served cleared inside commitment — 80.9%.

8,107 items cleared outside their commitment. They are spread across 36 queues, and the deepest single contributor is Time and claims with 686. 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.