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, Jul 27. 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, Jul 27
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 — 176,827 items standing and draining by 1,729 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 not growing, so the ranking is driven by the standing depth alone. At the day service rate of 9,668 items, and only if nothing else arrived, what is already standing in it is 18.3 days of work; work does keep arriving, and at the rate it is actually falling it takes 102 days to empty. Its oldest item has been waiting 22.5 d, and 3,550 of the 9,668 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.

176,827
Standing
9.8%
Share of all standing work
7,939
Arrived on the day
9,668
Served on the day
-11%
Against its own normal
22.5 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,806,664 items standing · deepest is 176,827

■ 90%+ inside commitment■ 75 to 90%■ under 75%
S2PSource-to-Pay333,379 standing · 18.5% of the operation
Invoice processing
169,297-3,53616.0 d
Buying desk
128,677-4895.8 d
Supplier operations
35,405-2,5189.3 d
H2RHire-to-Retire256,257 standing · 14.2% of the operation
Payroll operations
157,019+21610.2 d
Time and claims
99,238-2,2807.7 d
Employee lifecycle
0-4530 min
ITSIT Service253,388 standing · 14.0% of the operation
Incident desk
122,247+21821.2 d
Change and access
65,793-1,6669.9 d
Service requests
65,348-11613.6 d
M2DMake-to-Deliver231,804 standing · 12.8% of the operation
Move and deliver
117,559-3,0478.5 d
Make and release
114,209-1,60919.5 d
Quality control
36-3912.3 h
AIOAI Operations196,242 standing · 10.9% of the operation
Model routing
82,352-57314.6 d
Agent run desk
82,251-96021.2 d
Prompt and policy
31,639-6508.7 d
O2COrder-to-Cash176,827 standing · 9.8% of the operation
Order desk
176,827-1,72922.5 d
Cash and collections
0-1110 min
Billing and credit
0-3760 min
C2LConcept-to-Launch144,406 standing · 8.0% of the operation
Artwork studio
71,768-61722.7 d
Formulation
59,672-1,1495.7 d
Launch gates
12,966-2427.2 d
R2RRecord-to-Report100,609 standing · 5.6% of the operation
Postings desk
98,020-10114.9 d
Close management
2,589-32225.7 h
Reconciliation
000 min
P2PPlan-to-Perform43,882 standing · 2.4% of the operation
Sales and operations planning
17,312-5109.1 d
Replenishment
13,888-1623.3 d
Forecast desk
12,682-2985.8 d
A2LAwareness-to-Lead32,197 standing · 1.8% of the operation
Media operations
32,197-1958.8 d
Trade promotion
0-400 min
Campaign briefing
000 min
D&AData and Analytics28,209 standing · 1.6% of the operation
Metric governance
17,289-71613.7 d
Report certification
10,920-5084.4 d
Data quality
000 min
LGLLegal Operations9,464 standing · 0.5% of the operation
Contract desk
6,513-6862.3 d
Matter management
2,951-3332.3 d
Obligation management
0-1060 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,806,664 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

2 queues are taking on more than they clear

#QueueTowerArrivedServedNetStandingNormalvs normalDays of workInsideOldest
1Order deskO2C7,9399,668-1,729176,827198,431-11%18.363%22.5 d
2Invoice processingS2P8,57712,113-3,536169,297196,601-14%14.064%16.0 d
3Payroll operationsH2R6,9036,687+216157,019164,507-5%23.592%10.2 d
4Buying deskS2P7,6048,093-489128,677138,062-7%15.992%5.8 d
5Incident deskITS4,8574,639+218122,247132,592-8%26.471%21.2 d
6Move and deliverM2D6,4769,523-3,047117,559137,382-14%12.395%8.5 d
7Make and releaseM2D4,7916,400-1,609114,209127,902-11%17.865%19.5 d
8Time and claimsH2R8,29610,576-2,28099,238110,863-10%9.472%7.7 d
9Postings deskR2R6,8856,986-10198,020101,856-4%14.087%14.9 d
10Model routingAIO3,3803,953-57382,35286,371-5%20.882%14.6 d
11Agent run deskAIO3,8934,853-96082,25189,473-8%16.962%21.2 d
12Artwork studioC2L2,4723,089-61771,76879,373-10%23.271%22.7 d
13Change and accessITS4,0925,758-1,66665,79381,269-19%11.480%9.9 d
14Service requestsITS4,1324,248-11665,34866,267-1%15.470%13.6 d
15FormulationC2L3,1584,307-1,14959,67262,316-4%13.983%5.7 d
16Supplier operationsS2P3,8346,352-2,51835,40549,559-29%5.674%9.3 d
17Media operationsA2L1,7031,898-19532,19732,916-2%17.063%8.8 d
18Prompt and policyAIO3,0813,731-65031,63934,187-7%8.581%8.7 d
19Sales and operations planningP2P1,3181,828-51017,31221,202-18%9.580%9.1 d
20Metric governanceD&A1,1081,824-71617,28921,821-21%9.576%13.7 d
21ReplenishmentP2P1,2941,456-16213,88816,904-18%9.589%3.3 d
22Launch gatesC2L1,8292,071-24212,96616,952-24%6.367%7.2 d
23Forecast deskP2P1,2261,524-29812,68215,876-20%8.391%5.8 d
24Report certificationD&A1,4071,915-50810,92015,145-28%5.791%4.4 d
25Contract deskLGL3,2753,961-6866,51317,517-63%1.676%2.3 d
26Matter managementLGL8211,154-3332,9515,838-49%2.683%2.3 d
27Close managementR2R2,5092,831-3222,5898,865-71%0.968%25.7 h
28Quality controlM2D1,0441,083-393618+101%0.094%12.3 h
29Data qualityD&A1,9601,9600077-100%0.068%0 min
30ReconciliationR2R4,1794,17900709-100%0.087%0 min
31Cash and collectionsO2C2,4212,532-11101,320-100%0.087%0 min
32Billing and creditO2C7,1907,566-376011,557-100%0.095%0 min
33Obligation managementLGL1,7311,837-106034-100%0.071%0 min
34Trade promotionA2L2,2662,306-4003,131-100%0.092%0 min
35Campaign briefingA2L3,5323,5320030-100%0.095%0 min
36Employee lifecycleH2R3,8294,282-4530439-100%0.076%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 control36 standing against a normal of 18 · +101%
The commitment on the day
126,057 of 160,715 items served cleared inside commitment — 78.4%.

34,658 items cleared outside their commitment. They are spread across 36 queues, and the deepest single contributor is Invoice processing with 4,335. 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.