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 15. 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 15
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 — 195,841 items standing and draining by 2,423 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,601 items, and only if nothing else arrived, what is already standing in it is 20.4 days of work; work does keep arriving, and at the rate it is actually falling it takes 81 days to empty. Its oldest item has been waiting 25.8 d, and 2,720 of the 9,601 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.

195,841
Standing
9.7%
Share of all standing work
7,178
Arrived on the day
9,601
Served on the day
-8%
Against its own normal
25.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,023,586 items standing · deepest is 195,841

■ 90%+ inside commitment■ 75 to 90%■ under 75%
S2PSource-to-Pay374,805 standing · 18.5% of the operation
Invoice processing
192,102-2,26610.1 d
Buying desk
134,327-1,7357.2 d
Supplier operations
48,376-1,6446.7 d
ITSIT Service277,096 standing · 13.7% of the operation
Incident desk
130,698-1,41220.2 d
Change and access
79,793-2,5608.5 d
Service requests
66,605-4128.7 d
H2RHire-to-Retire276,497 standing · 13.7% of the operation
Payroll operations
163,060+9619.6 d
Time and claims
111,770-2,0199.2 d
Employee lifecycle
1,667+41517.9 h
M2DMake-to-Deliver266,511 standing · 13.2% of the operation
Move and deliver
138,030-1,40616.1 d
Make and release
128,481-57818.5 d
Quality control
000 min
O2COrder-to-Cash211,007 standing · 10.4% of the operation
Order desk
195,841-2,42325.8 d
Billing and credit
13,888-2,4132.0 d
Cash and collections
1,278-14512.4 h
AIOAI Operations209,754 standing · 10.4% of the operation
Model routing
87,957-27425.0 d
Agent run desk
87,319-1,16221.5 d
Prompt and policy
34,478-20114.8 d
C2LConcept-to-Launch156,378 standing · 7.7% of the operation
Artwork studio
77,838-36113.2 d
Formulation
62,514+3574.3 d
Launch gates
16,026-3973.6 d
R2RRecord-to-Report108,705 standing · 5.4% of the operation
Postings desk
101,166+84713.3 d
Close management
7,539-4982.1 d
Reconciliation
000 min
P2PPlan-to-Perform52,692 standing · 2.6% of the operation
Sales and operations planning
21,169-4278.0 d
Replenishment
16,084-29510.8 d
Forecast desk
15,439-50711.1 d
D&AData and Analytics35,469 standing · 1.8% of the operation
Metric governance
21,203-65411.8 d
Report certification
14,266-2197.0 d
Data quality
000 min
A2LAwareness-to-Lead33,113 standing · 1.6% of the operation
Media operations
32,476-1318.4 d
Trade promotion
637-1,03621.1 h
Campaign briefing
000 min
LGLLegal Operations21,559 standing · 1.1% of the operation
Contract desk
15,855-1,19443.2 h
Matter management
5,704-3195.7 d
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 2,023,586 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 deskO2C7,1789,601-2,423195,841213,081-8%20.472%25.8 d
2Invoice processingS2P10,74713,013-2,266192,102218,225-12%14.890%10.1 d
3Payroll operationsH2R7,6977,601+96163,060171,838-5%21.586%19.6 d
4Move and deliverM2D6,8738,279-1,406138,030142,526-3%16.777%16.1 d
5Buying deskS2P7,9209,655-1,735134,327150,964-11%13.975%7.2 d
6Incident deskITS4,0855,497-1,412130,698141,351-8%23.867%20.2 d
7Make and releaseM2D4,9805,558-578128,481132,173-3%23.186%18.5 d
8Time and claimsH2R8,07910,098-2,019111,770113,593-2%11.180%9.2 d
9Postings deskR2R7,2066,359+847101,166109,000-7%15.984%13.3 d
10Model routingAIO3,4713,745-27487,95785,749+3%23.591%25.0 d
11Agent run deskAIO4,2575,419-1,16287,31997,821-11%16.197%21.5 d
12Change and accessITS3,8276,387-2,56079,79387,588-9%12.568%8.5 d
13Artwork studioC2L3,1793,540-36177,83886,181-10%22.077%13.2 d
14Service requestsITS3,8724,284-41266,60567,471-1%15.584%8.7 d
15FormulationC2L3,7083,351+35762,51462,191+1%18.778%4.3 d
16Supplier operationsS2P4,8406,484-1,64448,37657,095-15%7.590%6.7 d
17Prompt and policyAIO2,5372,738-20134,47836,053-4%12.690%14.8 d
18Media operationsA2L1,9121,925-1332,47634,578-6%16.972%18.4 d
19Metric governanceD&A1,2551,909-65421,20324,571-14%11.180%11.8 d
20Sales and operations planningP2P1,3581,785-42721,16922,590-6%11.971%8.0 d
21ReplenishmentP2P1,1791,474-29516,08420,060-20%10.980%10.8 d
22Launch gatesC2L1,8762,273-39716,02619,630-18%7.189%3.6 d
23Contract deskLGL4,0845,278-1,19415,85526,225-40%3.076%43.2 h
24Forecast deskP2P1,2641,771-50715,43918,059-15%8.784%11.1 d
25Report certificationD&A1,7521,971-21914,26618,693-24%7.296%7.0 d
26Billing and creditO2C6,0738,486-2,41313,88815,188-9%1.666%2.0 d
27Close managementR2R2,7263,224-4987,53914,043-46%2.396%2.1 d
28Matter managementLGL8321,151-3195,7047,169-20%5.067%5.7 d
29Employee lifecycleH2R4,0493,634+4151,667515+223%0.584%17.9 h
30Cash and collectionsO2C2,7292,874-1451,2781,172+9%0.465%12.4 h
31Trade promotionA2L1,9693,005-1,0366377,772-92%0.266%21.1 h
32Quality controlM2D88488400647-100%0.071%0 min
33Obligation managementLGL1,5931,59300370-100%0.091%0 min
34ReconciliationR2R4,4564,456003,059-100%0.090%0 min
35Campaign briefingA2L3,6033,6030061-100%0.083%0 min
36Data qualityD&A2,2322,2320098-100%0.073%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

H2REmployee lifecycle1,667 standing against a normal of 515 · +223%
The commitment on the day
132,765 of 165,137 items served cleared inside commitment — 80.4%.

32,372 items cleared outside their commitment. They are spread across 36 queues, and the deepest single contributor is Billing and credit with 2,882. 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.