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 Wed, Jul 8. 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
Wed, Jul 8
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 — 207,038 items standing and draining by 1,263 a day.

Of the 36 queues on this canvas, this one is ranked first because releasing it frees the most work: it holds 9.7% 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,906 items, and only if nothing else arrived, what is already standing in it is 20.9 days of work; work does keep arriving, and at the rate it is actually falling it takes 164 days to empty. Its oldest item has been waiting 8.0 d, and 763 of the 9,906 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.

207,038
Standing
9.7%
Share of all standing work
8,643
Arrived on the day
9,906
Served on the day
-5%
Against its own normal
8.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 · 2,139,840 items standing · deepest is 207,038

■ 90%+ inside commitment■ 75 to 90%■ under 75%
S2PSource-to-Pay402,265 standing · 18.8% of the operation
Invoice processing
205,187-4,16512.2 d
Buying desk
142,135-1,35314.5 d
Supplier operations
54,943-1,4178.1 d
ITSIT Service291,152 standing · 13.6% of the operation
Incident desk
136,613-94516.6 d
Change and access
88,427-98914.4 d
Service requests
66,112-4615.1 d
H2RHire-to-Retire282,662 standing · 13.2% of the operation
Payroll operations
166,372-1,27014.6 d
Time and claims
116,290+1393.7 d
Employee lifecycle
000 min
M2DMake-to-Deliver278,701 standing · 13.0% of the operation
Move and deliver
145,121+75417.5 d
Make and release
133,580+35415.9 d
Quality control
000 min
O2COrder-to-Cash225,903 standing · 10.6% of the operation
Order desk
207,038-1,2638.0 d
Billing and credit
16,350+1,1052.6 d
Cash and collections
2,515+15213.7 h
AIOAI Operations213,788 standing · 10.0% of the operation
Agent run desk
91,733-1,60313.0 d
Model routing
87,127-4717.5 d
Prompt and policy
34,928-1612.3 d
C2LConcept-to-Launch165,033 standing · 7.7% of the operation
Artwork studio
82,936-99019.7 d
Formulation
63,138-28215.0 d
Launch gates
18,959-2803.8 d
R2RRecord-to-Report114,334 standing · 5.3% of the operation
Postings desk
102,231-1,1364.2 d
Close management
12,103-56541.2 h
Reconciliation
0-4310 min
P2PPlan-to-Perform58,318 standing · 2.7% of the operation
Sales and operations planning
22,786-2024.5 d
Replenishment
18,333-52214.8 d
Forecast desk
17,199-2484.3 d
D&AData and Analytics40,886 standing · 1.9% of the operation
Metric governance
23,421-5878.7 d
Report certification
17,465-1545.8 d
Data quality
000 min
A2LAwareness-to-Lead38,281 standing · 1.8% of the operation
Media operations
33,165-39113.9 d
Trade promotion
5,116-84223.8 h
Campaign briefing
000 min
LGLLegal Operations28,517 standing · 1.3% of the operation
Contract desk
21,577-1,7542.2 d
Matter management
6,876-1397.0 d
Obligation management
64+642.6 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,139,840 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
1Order deskO2C8,6439,906-1,263207,038217,639-5%20.992%8.0 d
2Invoice processingS2P9,13013,295-4,165205,187227,594-10%15.468%12.2 d
3Payroll operationsH2R7,4818,751-1,270166,372176,660-6%19.085%14.6 d
4Move and deliverM2D7,8617,107+754145,121140,952+3%20.475%17.5 d
5Buying deskS2P9,04310,396-1,353142,135157,323-10%13.770%14.5 d
6Incident deskITS4,5835,528-945136,613144,351-5%24.794%16.6 d
7Make and releaseM2D5,6295,275+354133,580131,533+2%25.375%15.9 d
8Time and claimsH2R9,4499,310+139116,290112,496+3%12.586%3.7 d
9Postings deskR2R6,3197,455-1,136102,231113,938-10%13.792%4.2 d
10Agent run deskAIO4,0385,641-1,60391,733102,126-10%16.362%13.0 d
11Change and accessITS4,8035,792-98988,42787,748+1%15.369%14.4 d
12Model routingAIO3,6853,732-4787,12784,250+3%23.388%17.5 d
13Artwork studioC2L3,1804,170-99082,93688,724-7%19.980%19.7 d
14Service requestsITS3,9884,449-46166,11268,789-4%14.970%5.1 d
15FormulationC2L3,3053,587-28263,13861,965+2%17.692%15.0 d
16Supplier operationsS2P4,1315,548-1,41754,94358,797-7%9.962%8.1 d
17Prompt and policyAIO2,8212,837-1634,92837,990-8%12.393%12.3 d
18Media operationsA2L1,6122,003-39133,16535,798-7%16.687%13.9 d
19Metric governanceD&A1,2521,839-58723,42125,332-8%12.779%8.7 d
20Sales and operations planningP2P1,5131,715-20222,78622,618+1%13.372%4.5 d
21Billing and creditO2C7,8506,745+1,10516,35017,756-8%2.489%2.6 d
22Contract deskLGL3,4705,224-1,75421,57729,575-27%4.186%2.2 d
23Launch gatesC2L1,7021,982-28018,95920,226-6%9.683%3.8 d
24ReplenishmentP2P1,2501,772-52218,33321,682-15%10.372%14.8 d
25Report certificationD&A1,8221,976-15417,46520,231-14%8.888%5.8 d
26Forecast deskP2P1,2651,513-24817,19918,704-8%11.479%4.3 d
27Close managementR2R2,6083,173-56512,10315,931-24%3.873%41.2 h
28Matter managementLGL9851,124-1396,8767,377-7%6.196%7.0 d
29Trade promotionA2L2,2503,092-8425,1169,878-48%1.764%23.8 h
30Cash and collectionsO2C2,8572,705+1522,515575+337%0.966%13.7 h
31Obligation managementLGL1,8831,819+64641,428-96%0.094%2.6 h
32ReconciliationR2R4,9025,333-43105,391-100%0.075%0 min
33Campaign briefingA2L4,4944,4940056-100%0.093%0 min
34Quality controlM2D1,1631,163001,648-100%0.096%0 min
35Data qualityD&A2,3202,32000125-100%0.086%0 min
36Employee lifecycleH2R3,6333,633001,626-100%0.064%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

O2CCash and collections2,515 standing against a normal of 575 · +337%
The commitment on the day
132,132 of 166,404 items served cleared inside commitment — 79.4%.

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