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 Tue, Feb 10. 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
Tue, Feb 10
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 — 156,394 items standing and growing by 2,311 a day.

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

156,394
Standing
7.8%
Share of all standing work
12,920
Arrived on the day
10,609
Served on the day
+4%
Against its own normal
8.3 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,010,393 items standing · deepest is 156,394

■ 90%+ inside commitment■ 75 to 90%■ under 75%
S2PSource-to-Pay341,018 standing · 17.0% of the operation
Invoice processing
156,394+2,3118.3 d
Buying desk
120,119+9574.9 d
Supplier operations
64,505+2293.7 d
H2RHire-to-Retire298,484 standing · 14.8% of the operation
Payroll operations
147,922+2,73312.8 d
Time and claims
122,035+6754.6 d
Employee lifecycle
28,527-4732.3 d
ITSIT Service236,264 standing · 11.8% of the operation
Incident desk
91,958+1,47311.5 d
Change and access
74,290+1,98110.6 d
Service requests
70,016+45611.0 d
M2DMake-to-Deliver220,141 standing · 11.0% of the operation
Move and deliver
112,812+2,5597.9 d
Make and release
101,216+1,70414.2 d
Quality control
6,113+3794.0 d
O2COrder-to-Cash215,512 standing · 10.7% of the operation
Order desk
151,349+1,22118.9 d
Billing and credit
53,056+1,3336.2 d
Cash and collections
11,107-4703.7 d
AIOAI Operations186,613 standing · 9.3% of the operation
Agent run desk
75,249+2,1267.4 d
Model routing
73,447+92914.6 d
Prompt and policy
37,917+2695.6 d
C2LConcept-to-Launch147,363 standing · 7.3% of the operation
Formulation
62,466+9578.9 d
Artwork studio
62,089+1,34915.2 d
Launch gates
22,808+2425.8 d
R2RRecord-to-Report146,326 standing · 7.3% of the operation
Postings desk
98,869+1,93012.5 d
Reconciliation
25,339-5244.6 d
Close management
22,118+1537.0 d
A2LAwareness-to-Lead62,380 standing · 3.1% of the operation
Media operations
28,353+4736.1 d
Trade promotion
18,450-502.2 d
Campaign briefing
15,577-6692.5 d
P2PPlan-to-Perform54,659 standing · 2.7% of the operation
Replenishment
19,581+44311.2 d
Sales and operations planning
19,410+5453.7 d
Forecast desk
15,668-1518.9 d
D&AData and Analytics52,015 standing · 2.6% of the operation
Report certification
19,862+3133.7 d
Metric governance
17,288+2566.8 d
Data quality
14,865+855.0 d
LGLLegal Operations49,618 standing · 2.5% of the operation
Contract desk
30,266+3204.1 d
Obligation management
12,058-465.4 d
Matter management
7,294-166.9 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,010,393 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

28 queues are taking on more than they clear

#QueueTowerArrivedServedNetStandingNormalvs normalDays of workInsideOldest
1Invoice processingS2P12,92010,609+2,311156,394151,101+4%14.796%8.3 d
2Payroll operationsH2R9,4766,743+2,733147,922121,168+22%21.976%12.8 d
3Order deskO2C7,9506,729+1,221151,349139,217+9%22.578%18.9 d
4Move and deliverM2D8,7816,222+2,559112,81295,260+18%18.186%7.9 d
5Time and claimsH2R11,00410,329+675122,035116,413+5%11.876%4.6 d
6Buying deskS2P9,0738,116+957120,119110,904+8%14.865%4.9 d
7Make and releaseM2D6,1984,494+1,704101,21686,808+17%22.593%14.2 d
8Postings deskR2R8,6266,696+1,93098,86988,083+12%14.874%12.5 d
9Incident deskITS5,8524,379+1,47391,95883,080+11%21.070%11.5 d
10Agent run deskAIO6,0103,884+2,12675,24963,835+18%19.472%7.4 d
11Change and accessITS5,8063,825+1,98174,29063,336+17%19.482%10.6 d
12Model routingAIO3,9803,051+92973,44762,511+17%24.187%14.6 d
13Service requestsITS5,5695,113+45670,01660,544+16%13.790%11.0 d
14Artwork studioC2L3,9012,552+1,34962,08953,950+15%24.368%15.2 d
15FormulationC2L4,7403,783+95762,46651,493+21%16.577%8.9 d
16Supplier operationsS2P6,1055,876+22964,50559,107+9%11.067%3.7 d
17Billing and creditO2C8,7517,418+1,33353,05647,830+11%7.271%6.2 d
18Prompt and policyAIO3,6833,414+26937,91732,845+15%11.181%5.6 d
19Contract deskLGL4,7284,408+32030,26629,981+1%6.987%4.1 d
20Media operationsA2L2,1521,679+47328,35325,008+13%16.970%6.1 d
21Employee lifecycleH2R4,5144,987-47328,52729,143-2%5.779%2.3 d
22ReconciliationR2R5,8066,330-52425,33927,543-8%4.078%4.6 d
23Launch gatesC2L2,2952,053+24222,80820,956+9%11.186%5.8 d
24Close managementR2R2,7692,616+15322,11818,601+19%8.575%7.0 d
25Sales and operations planningP2P1,7601,215+54519,41016,323+19%16.089%3.7 d
26ReplenishmentP2P1,7801,337+44319,58115,902+23%14.663%11.2 d
27Report certificationD&A1,8461,533+31319,86217,697+12%13.075%3.7 d
28Metric governanceD&A1,7831,527+25617,28816,852+3%11.371%6.8 d
29Trade promotionA2L2,9472,997-5018,45019,104-3%6.271%2.2 d
30Forecast deskP2P1,6741,825-15115,66815,460+1%8.675%8.9 d
31Campaign briefingA2L5,4546,123-66915,57722,063-29%2.576%2.5 d
32Data qualityD&A3,1723,087+8514,86515,619-5%4.874%5.0 d
33Obligation managementLGL1,8391,885-4612,0589,690+24%6.496%5.4 d
34Cash and collectionsO2C2,7473,217-47011,10714,243-22%3.594%3.7 d
35Quality controlM2D1,4091,030+3796,1135,266+16%5.992%4.0 d
36Matter managementLGL972988-167,2946,133+19%7.478%6.9 d

"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

21 queues are more than ten percent above their own 27 day mean

LGLObligation management12,058 standing against a normal of 9,690 · +24%
P2PReplenishment19,581 standing against a normal of 15,902 · +23%
H2RPayroll operations147,922 standing against a normal of 121,168 · +22%
C2LFormulation62,466 standing against a normal of 51,493 · +21%
LGLMatter management7,294 standing against a normal of 6,133 · +19%
P2PSales and operations planning19,410 standing against a normal of 16,323 · +19%
R2RClose management22,118 standing against a normal of 18,601 · +19%
M2DMove and deliver112,812 standing against a normal of 95,260 · +18%
AIOAgent run desk75,249 standing against a normal of 63,835 · +18%
AIOModel routing73,447 standing against a normal of 62,511 · +17%
ITSChange and access74,290 standing against a normal of 63,336 · +17%
M2DMake and release101,216 standing against a normal of 86,808 · +17%

The first 12 of 21 are shown, deepest departure from normal first.

The commitment on the day
119,837 of 152,070 items served cleared inside commitment — 78.8%.

32,233 items cleared outside their commitment. They are spread across 36 queues, and the deepest single contributor is Buying desk with 2,822. 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.