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, May 20. 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, May 20
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
Invoice processing in Source-to-Pay — 231,229 items standing and growing by 107 a day.

Of the 36 queues on this canvas, this one is ranked first because releasing it frees the most work: it holds 8.8% of everything standing, and it is taking on 107 more items a day than it clears, so the share is rising. At the day service rate of 10,373 items, and only if nothing else arrived, what is already standing in it is 22.3 days of work. Its oldest item has been waiting 16.1 d, and 3,360 of the 10,373 items it did serve cleared outside commitment.

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

231,229
Standing
8.8%
Share of all standing work
10,480
Arrived on the day
10,373
Served on the day
+1%
Against its own normal
16.1 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,629,648 items standing · deepest is 231,229

■ 90%+ inside commitment■ 75 to 90%■ under 75%
S2PSource-to-Pay460,096 standing · 17.5% of the operation
Invoice processing
231,229+10716.1 d
Buying desk
165,824-7877.4 d
Supplier operations
63,043+1404.9 d
H2RHire-to-Retire376,322 standing · 14.3% of the operation
Payroll operations
204,138-1,30528.9 d
Time and claims
142,129-2,05013.9 d
Employee lifecycle
30,055-1,8407.3 d
ITSIT Service333,509 standing · 12.7% of the operation
Incident desk
139,265+36020.3 d
Change and access
101,498-8913.9 d
Service requests
92,746-1,27420.1 d
M2DMake-to-Deliver309,953 standing · 11.8% of the operation
Move and deliver
157,509-2,15316.8 d
Make and release
144,564+3287.6 d
Quality control
7,880+1205.5 d
O2COrder-to-Cash279,873 standing · 10.6% of the operation
Order desk
209,573-9012.6 d
Billing and credit
61,509+6958.3 d
Cash and collections
8,791-6012.3 d
AIOAI Operations249,677 standing · 9.5% of the operation
Agent run desk
112,138-36625.7 d
Model routing
92,779-1,0218.8 d
Prompt and policy
44,760-30810.4 d
C2LConcept-to-Launch194,258 standing · 7.4% of the operation
Artwork studio
90,188+68626.8 d
Formulation
79,458-1,0358.1 d
Launch gates
24,612-8079.3 d
R2RRecord-to-Report161,039 standing · 6.1% of the operation
Postings desk
123,477-4607.7 d
Close management
19,095-2284.7 d
Reconciliation
18,467-1,3353.9 d
P2PPlan-to-Perform73,736 standing · 2.8% of the operation
Sales and operations planning
27,765-2517.5 d
Replenishment
25,866+2307.9 d
Forecast desk
20,105-25111.4 d
A2LAwareness-to-Lead69,712 standing · 2.7% of the operation
Media operations
43,321+12615.5 d
Trade promotion
19,228-6677.8 d
Campaign briefing
7,163-98835.2 h
LGLLegal Operations63,852 standing · 2.4% of the operation
Contract desk
40,922-7036.1 d
Obligation management
13,380-2024.1 d
Matter management
9,550-16711.0 d
D&AData and Analytics57,621 standing · 2.2% of the operation
Report certification
25,406-37712.5 d
Metric governance
24,921-1319.3 d
Data quality
7,294-1,0462.1 d

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,629,648 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

9 queues are taking on more than they clear

#QueueTowerArrivedServedNetStandingNormalvs normalDays of workInsideOldest
1Invoice processingS2P10,48010,373+107231,229229,862+1%22.368%16.1 d
2Order deskO2C7,8987,988-90209,573203,996+3%26.269%12.6 d
3Payroll operationsH2R7,0788,383-1,305204,138200,612+2%24.468%28.9 d
4Buying deskS2P8,8899,676-787165,824177,919-7%17.178%7.4 d
5Move and deliverM2D6,8759,028-2,153157,509166,170-5%17.493%16.8 d
6Make and releaseM2D5,2884,960+328144,564140,717+3%29.192%7.6 d
7Time and claimsH2R9,18611,236-2,050142,129163,904-13%12.674%13.9 d
8Incident deskITS4,8644,504+360139,265139,358-0%30.965%20.3 d
9Postings deskR2R6,8507,310-460123,477133,494-8%16.976%7.7 d
10Agent run deskAIO4,0414,407-366112,138106,323+5%25.475%25.7 d
11Change and accessITS5,0015,090-89101,49897,709+4%19.995%13.9 d
12Artwork studioC2L3,3202,634+68690,18887,224+3%34.266%26.8 d
13Model routingAIO3,4444,465-1,02192,77996,014-3%20.867%8.8 d
14Service requestsITS4,0125,286-1,27492,74696,808-4%17.592%20.1 d
15FormulationC2L3,2934,328-1,03579,45883,047-4%18.465%8.1 d
16Billing and creditO2C8,0117,316+69561,50961,947-1%8.487%8.3 d
17Supplier operationsS2P5,0844,944+14063,04370,457-11%12.863%4.9 d
18Prompt and policyAIO3,0513,359-30844,76048,245-7%13.382%10.4 d
19Media operationsA2L2,0241,898+12643,32142,505+2%22.876%15.5 d
20Contract deskLGL4,0124,715-70340,92245,589-10%8.766%6.1 d
21Employee lifecycleH2R3,6645,504-1,84030,05537,478-20%5.571%7.3 d
22Sales and operations planningP2P1,3351,360-2527,76526,668+4%20.475%17.5 d
23ReplenishmentP2P1,4831,253+23025,86624,307+6%20.666%7.9 d
24Report certificationD&A1,6512,028-37725,40628,483-11%12.577%12.5 d
25Metric governanceD&A1,3491,480-13124,92125,531-2%16.876%9.3 d
26Launch gatesC2L1,5802,387-80724,61226,725-8%10.390%9.3 d
27Forecast deskP2P1,2021,453-25120,10521,474-6%13.870%11.4 d
28Trade promotionA2L2,3593,026-66719,22822,769-16%6.471%7.8 d
29Close managementR2R2,4422,670-22819,09523,494-19%7.280%4.7 d
30ReconciliationR2R4,4135,748-1,33518,46725,185-27%3.278%3.9 d
31Obligation managementLGL1,8662,068-20213,38013,108+2%6.578%4.1 d
32Matter managementLGL9651,132-1679,55010,816-12%8.491%11.0 d
33Cash and collectionsO2C2,8883,489-6018,79115,030-42%2.585%2.3 d
34Quality controlM2D1,1791,059+1207,8806,774+16%7.464%5.5 d
35Data qualityD&A2,0793,125-1,0467,29413,636-47%2.395%2.1 d
36Campaign briefingA2L4,3415,329-9887,16312,977-45%1.373%35.2 h

"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 control7,880 standing against a normal of 6,774 · +16%
The commitment on the day
126,312 of 165,011 items served cleared inside commitment — 76.5%.

38,699 items cleared outside their commitment. They are spread across 36 queues, and the deepest single contributor is Invoice processing with 3,360. 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.