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, Jul 18. 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, Jul 18
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 — 191,815 items standing and growing by 225 a day.

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

191,815
Standing
9.8%
Share of all standing work
2,819
Arrived on the day
2,594
Served on the day
-9%
Against its own normal
23.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,963,278 items standing · deepest is 191,815

■ 90%+ inside commitment■ 75 to 90%■ under 75%
S2PSource-to-Pay361,801 standing · 18.4% of the operation
Invoice processing
184,581-46644.2 d
Buying desk
131,470+2958.8 d
Supplier operations
45,750-35613.8 d
ITSIT Service270,669 standing · 13.8% of the operation
Incident desk
128,835+22644.7 d
Change and access
75,913-31242.7 d
Service requests
65,921+26745.9 d
H2RHire-to-Retire270,195 standing · 13.8% of the operation
Payroll operations
162,134+48730.9 d
Time and claims
107,747-20233.5 d
Employee lifecycle
314+12817.9 h
M2DMake-to-Deliver258,201 standing · 13.2% of the operation
Move and deliver
132,928+16471.0 d
Make and release
125,273+12132.2 d
Quality control
000 min
AIOAI Operations206,518 standing · 10.5% of the operation
Model routing
87,000-31297.4 d
Agent run desk
85,291-46070.1 d
Prompt and policy
34,227-2428.3 d
O2COrder-to-Cash203,617 standing · 10.4% of the operation
Order desk
191,815+22523.0 d
Billing and credit
11,119+7993.1 d
Cash and collections
683+2517.6 h
C2LConcept-to-Launch152,851 standing · 7.8% of the operation
Artwork studio
75,628-6757.5 d
Formulation
62,012-7357.3 d
Launch gates
15,211+1727.0 d
R2RRecord-to-Report104,835 standing · 5.3% of the operation
Postings desk
99,198+68519.9 d
Close management
5,637-614.7 d
Reconciliation
000 min
P2PPlan-to-Perform49,981 standing · 2.5% of the operation
Sales and operations planning
20,183-2415.7 d
Replenishment
15,393-413.2 d
Forecast desk
14,405-9916.7 d
D&AData and Analytics33,635 standing · 1.7% of the operation
Metric governance
20,351-25618.2 d
Report certification
13,284-10022.9 d
Data quality
000 min
A2LAwareness-to-Lead32,295 standing · 1.6% of the operation
Media operations
32,078+435.4 d
Trade promotion
217+2175.6 h
Campaign briefing
000 min
LGLLegal Operations18,680 standing · 1.0% of the operation
Contract desk
13,707-4888.9 d
Matter management
4,971-315.6 d
Obligation management
2+210.3 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,963,278 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

15 queues are taking on more than they clear

#QueueTowerArrivedServedNetStandingNormalvs normalDays of workInsideOldest
1Order deskO2C2,8192,594+225191,815210,128-9%73.965%23.0 d
2Invoice processingS2P3,1733,639-466184,581213,259-13%50.792%44.2 d
3Payroll operationsH2R2,6692,182+487162,134169,949-5%74.386%30.9 d
4Move and deliverM2D1,9701,806+164132,928142,258-7%73.695%71.0 d
5Buying deskS2P2,3352,306+29131,470147,641-11%57.079%58.8 d
6Incident deskITS1,7391,513+226128,835139,657-8%85.273%44.7 d
7Make and releaseM2D1,5381,417+121125,273131,970-5%88.494%32.2 d
8Time and claimsH2R2,5212,723-202107,747113,454-5%39.695%33.5 d
9Postings deskR2R2,1341,449+68599,198107,033-7%68.587%19.9 d
10Model routingAIO9341,246-31287,00086,275+1%69.879%97.4 d
11Agent run deskAIO1,1251,585-46085,29195,752-11%53.882%70.1 d
12Change and accessITS1,5961,908-31275,91386,670-12%39.889%42.7 d
13Artwork studioC2L724791-6775,62884,662-11%95.669%57.5 d
14Service requestsITS1,194927+26765,92167,132-2%71.192%45.9 d
15FormulationC2L906979-7362,01262,344-1%63.394%57.3 d
16Supplier operationsS2P1,3491,705-35645,75055,680-18%26.879%13.8 d
17Prompt and policyAIO956980-2434,22735,436-3%34.973%28.3 d
18Media operationsA2L480476+432,07834,124-6%67.496%35.4 d
19Metric governanceD&A341597-25620,35124,034-15%34.187%18.2 d
20Sales and operations planningP2P467491-2420,18322,419-10%41.166%15.7 d
21ReplenishmentP2P331335-415,39319,278-20%45.992%13.2 d
22Launch gatesC2L459442+1715,21119,121-20%34.471%27.0 d
23Billing and creditO2C2,6031,804+79911,11914,446-23%6.293%3.1 d
24Forecast deskP2P462561-9914,40517,601-18%25.792%16.7 d
25Contract deskLGL9781,466-48813,70724,325-44%9.374%8.9 d
26Report certificationD&A486586-10013,28417,863-26%22.796%22.9 d
27Close managementR2R778839-615,63712,928-56%6.764%4.7 d
28Matter managementLGL360391-314,9716,950-28%12.796%5.6 d
29Trade promotionA2L800583+2172176,563-97%0.493%5.6 h
30Employee lifecycleH2R1,3131,185+128314496-37%0.396%17.9 h
31Cash and collectionsO2C812787+256831,290-47%0.978%17.6 h
32Obligation managementLGL424422+22164-99%0.089%10.3 h
33Campaign briefingA2L1,0391,0390057-100%0.076%0 min
34Quality controlM2D34534500357-100%0.070%0 min
35ReconciliationR2R1,5311,531002,202-100%0.080%0 min
36Data qualityD&A5675670086-100%0.075%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

No queue is more than ten percent above its own 27 day mean

Every queue on this day is running at or below its own 27 day mean depth. That is a statement about variation, not about health: 1,963,278 items are still standing and 16.0% of what was served cleared outside commitment.

The commitment on the day
37,130 of 44,197 items served cleared inside commitment — 84.0%.

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