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 Thu, Jul 30. 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
Thu, Jul 30
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
Order desk in Order-to-Cash — 173,528 items standing and draining by 1,335 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 not growing, so the ranking is driven by the standing depth alone. At the day service rate of 8,162 items, and only if nothing else arrived, what is already standing in it is 21.3 days of work; work does keep arriving, and at the rate it is actually falling it takes 130 days to empty. Its oldest item has been waiting 15.0 d, and 1,815 of the 8,162 items it did serve cleared outside commitment.

The name recorded against most of the work in this queue in the sampled ledger week is Chidi Obi. That is who this constraint belongs to.

173,528
Standing
9.9%
Share of all standing work
6,827
Arrived on the day
8,162
Served on the day
-11%
Against its own normal
15.0 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,750,705 items standing · deepest is 173,528

■ 90%+ inside commitment■ 75 to 90%■ under 75%
S2PSource-to-Pay324,693 standing · 18.5% of the operation
Invoice processing
165,480-52512.0 d
Buying desk
128,175+33917.7 d
Supplier operations
31,038-1,6825.8 d
H2RHire-to-Retire250,634 standing · 14.3% of the operation
Payroll operations
158,183+98721.2 d
Time and claims
92,451-1,2593.2 d
Employee lifecycle
000 min
ITSIT Service249,080 standing · 14.2% of the operation
Incident desk
121,025-30423.2 d
Service requests
64,964+37911.5 d
Change and access
63,091-54513.5 d
M2DMake-to-Deliver220,162 standing · 12.6% of the operation
Make and release
112,080-84018.5 d
Move and deliver
108,053-1,9195.0 d
Quality control
29-3213.3 h
AIOAI Operations189,379 standing · 10.8% of the operation
Agent run desk
81,061-36220.1 d
Model routing
78,967-64217.4 d
Prompt and policy
29,351-8005.4 d
O2COrder-to-Cash173,528 standing · 9.9% of the operation
Order desk
173,528-1,33515.0 d
Cash and collections
000 min
Billing and credit
000 min
C2LConcept-to-Launch139,425 standing · 8.0% of the operation
Artwork studio
70,503+12914.6 d
Formulation
56,907-95517.2 d
Launch gates
12,015-6103.0 d
R2RRecord-to-Report97,203 standing · 5.6% of the operation
Postings desk
96,362-1,3547.5 d
Close management
841-28813.0 h
Reconciliation
000 min
P2PPlan-to-Perform40,925 standing · 2.3% of the operation
Sales and operations planning
16,302-2179.9 d
Replenishment
13,190-3717.9 d
Forecast desk
11,433-4246.8 d
A2LAwareness-to-Lead31,583 standing · 1.8% of the operation
Media operations
31,583-3526.5 d
Campaign briefing
000 min
Trade promotion
000 min
D&AData and Analytics27,001 standing · 1.5% of the operation
Metric governance
16,132-3877.2 d
Report certification
10,869-286.3 d
Data quality
000 min
LGLLegal Operations7,092 standing · 0.4% of the operation
Contract desk
5,047-50939.6 h
Matter management
2,045-24143.1 h
Obligation management
000 min

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,750,705 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

4 queues are taking on more than they clear

#QueueTowerArrivedServedNetStandingNormalvs normalDays of workInsideOldest
1Order deskO2C6,8278,162-1,335173,528194,093-11%21.378%15.0 d
2Invoice processingS2P10,23810,763-525165,480190,600-13%15.479%12.0 d
3Payroll operationsH2R7,9897,002+987158,183162,707-3%22.687%21.2 d
4Buying deskS2P8,1817,842+339128,175135,527-5%16.391%17.7 d
5Incident deskITS4,8075,111-304121,025130,212-7%23.793%23.2 d
6Make and releaseM2D5,1956,035-840112,080125,643-11%18.678%18.5 d
7Move and deliverM2D6,2728,191-1,919108,053133,980-19%13.296%5.0 d
8Postings deskR2R6,1337,487-1,35496,362100,658-4%12.975%7.5 d
9Time and claimsH2R8,4639,722-1,25992,451108,992-15%9.576%3.2 d
10Agent run deskAIO4,0504,412-36281,06187,736-8%18.469%20.1 d
11Model routingAIO3,6634,305-64278,96785,866-8%18.390%17.4 d
12Artwork studioC2L3,1353,006+12970,50377,625-9%23.566%14.6 d
13Service requestsITS4,7704,391+37964,96466,032-2%14.879%11.5 d
14Change and accessITS3,9974,542-54563,09178,569-20%13.975%13.5 d
15FormulationC2L3,5254,480-95556,90761,886-8%12.765%17.2 d
16Media operationsA2L1,6031,955-35231,58332,624-3%16.271%6.5 d
17Supplier operationsS2P3,9605,642-1,68231,03846,914-34%5.575%5.8 d
18Prompt and policyAIO2,7143,514-80029,35133,797-13%8.469%5.4 d
19Sales and operations planningP2P1,2371,454-21716,30220,526-21%11.281%9.9 d
20Metric governanceD&A1,2241,611-38716,13220,925-23%10.096%7.2 d
21ReplenishmentP2P1,2231,594-37113,19016,187-19%8.379%7.9 d
22Launch gatesC2L1,4782,088-61012,01516,084-25%5.873%3.0 d
23Forecast deskP2P1,2971,721-42411,43315,185-25%6.690%6.8 d
24Report certificationD&A1,6401,668-2810,86914,246-24%6.586%6.3 d
25Contract deskLGL3,7814,290-5095,04715,168-67%1.285%39.6 h
26Matter managementLGL8201,061-2412,0455,285-61%1.996%43.1 h
27Close managementR2R2,2392,527-2888417,393-89%0.379%13.0 h
28Quality controlM2D9891,021-322921+35%0.096%13.3 h
29Cash and collectionsO2C2,3432,343001,180-100%0.068%0 min
30ReconciliationR2R4,9004,90000316-100%0.096%0 min
31Campaign briefingA2L3,9803,9800030-100%0.076%0 min
32Employee lifecycleH2R3,7693,76900418-100%0.088%0 min
33Trade promotionA2L2,0122,012002,223-100%0.091%0 min
34Data qualityD&A2,2852,2850059-100%0.078%0 min
35Billing and creditO2C7,3507,3500010,118-100%0.096%0 min
36Obligation managementLGL1,8011,8010034-100%0.086%0 min

"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 control29 standing against a normal of 21 · +35%
The commitment on the day
126,180 of 154,037 items served cleared inside commitment — 81.9%.

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