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, Dec 31. 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, Dec 31
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 — 139,705 items standing and growing by 3,507 a day.

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

139,705
Standing
9.9%
Share of all standing work
14,489
Arrived on the day
10,982
Served on the day
+38%
Against its own normal
3.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 · 1,409,989 items standing · deepest is 139,705

■ 90%+ inside commitment■ 75 to 90%■ under 75%
S2PSource-to-Pay272,795 standing · 19.3% of the operation
Invoice processing
139,705+3,5073.0 d
Buying desk
95,475+1,9806.1 d
Supplier operations
37,615+2,0865.6 d
O2COrder-to-Cash171,590 standing · 12.2% of the operation
Order desk
127,323+1,4437.2 d
Billing and credit
32,937+1,0033.3 d
Cash and collections
11,330+46039.0 h
H2RHire-to-Retire169,253 standing · 12.0% of the operation
Payroll operations
82,305-3983.7 d
Time and claims
75,488+2,6627.1 d
Employee lifecycle
11,460+1,9132.0 d
M2DMake-to-Deliver159,802 standing · 11.3% of the operation
Move and deliver
80,427-5248.5 d
Make and release
74,331+3015.0 d
Quality control
5,044-1764.6 d
ITSIT Service152,769 standing · 10.8% of the operation
Incident desk
67,967+1,28211.4 d
Change and access
46,770+1,1416.3 d
Service requests
38,032+1,9836.5 d
AIOAI Operations133,099 standing · 9.4% of the operation
Agent run desk
57,885+6026.9 d
Model routing
49,030+4356.5 d
Prompt and policy
26,184+3185.0 d
R2RRecord-to-Report109,468 standing · 7.8% of the operation
Postings desk
74,057+1,2546.1 d
Reconciliation
21,131+3742.3 d
Close management
14,280-1604.7 d
C2LConcept-to-Launch93,188 standing · 6.6% of the operation
Artwork studio
47,474+75510.0 d
Formulation
31,828+7216.7 d
Launch gates
13,886+2447.0 d
A2LAwareness-to-Lead48,016 standing · 3.4% of the operation
Media operations
22,919+4265.6 d
Trade promotion
12,552+5874.4 d
Campaign briefing
12,545+1,03232.6 h
D&AData and Analytics37,516 standing · 2.7% of the operation
Report certification
14,878+2536.1 d
Metric governance
14,664+3917.3 d
Data quality
7,974+81021.9 h
P2PPlan-to-Perform35,038 standing · 2.5% of the operation
Sales and operations planning
12,718+3742.5 d
Replenishment
11,522+37.3 d
Forecast desk
10,798+2247.9 d
LGLLegal Operations27,455 standing · 1.9% of the operation
Contract desk
17,550+4333.2 d
Matter management
5,726-406.0 d
Obligation management
4,179-2736.1 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 1,409,989 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

30 queues are taking on more than they clear

#QueueTowerArrivedServedNetStandingNormalvs normalDays of workInsideOldest
1Invoice processingS2P14,48910,982+3,507139,705101,519+38%12.771%3.0 d
2Order deskO2C10,6019,158+1,443127,323107,629+18%13.967%7.2 d
3Buying deskS2P10,3338,353+1,98095,47569,264+38%11.490%6.1 d
4Time and claimsH2R10,2967,634+2,66275,48844,451+70%9.974%7.1 d
5Payroll operationsH2R8,6409,038-39882,30573,543+12%9.174%3.7 d
6Move and deliverM2D8,0138,537-52480,42767,038+20%9.495%8.5 d
7Postings deskR2R8,2997,045+1,25474,05748,301+53%10.576%6.1 d
8Make and releaseM2D5,9915,690+30174,33157,188+30%13.165%5.0 d
9Incident deskITS6,3375,055+1,28267,96752,088+30%13.479%11.4 d
10Agent run deskAIO6,0425,440+60257,88551,673+12%10.674%6.9 d
11Change and accessITS5,5754,434+1,14146,77032,250+45%10.589%6.3 d
12Artwork studioC2L4,0893,334+75547,47440,890+16%14.270%10.0 d
13Model routingAIO4,2763,841+43549,03044,738+10%12.871%6.5 d
14Supplier operationsS2P6,0944,008+2,08637,61524,930+51%9.478%5.6 d
15Service requestsITS6,3894,406+1,98338,03229,579+29%8.667%6.5 d
16Billing and creditO2C8,0537,050+1,00332,93715,962+106%4.764%3.3 d
17FormulationC2L4,9044,183+72131,82827,164+17%7.666%6.7 d
18Prompt and policyAIO3,4823,164+31826,18417,449+50%8.375%5.0 d
19Media operationsA2L2,5782,152+42622,91918,616+23%10.772%5.6 d
20ReconciliationR2R5,5385,164+37421,1316,771+212%4.166%2.3 d
21Employee lifecycleH2R5,3503,437+1,91311,4602,542+351%3.391%2.0 d
22Contract deskLGL4,6374,204+43317,55012,609+39%4.273%3.2 d
23Campaign briefingA2L4,8153,783+1,03212,5453,061+310%3.388%32.6 h
24Metric governanceD&A1,7191,328+39114,66410,229+43%11.066%7.3 d
25Report certificationD&A2,0731,820+25314,8789,618+55%8.271%6.1 d
26Trade promotionA2L2,9312,344+58712,5528,438+49%5.488%4.4 d
27Launch gatesC2L2,0471,803+24413,88612,395+12%7.796%7.0 d
28Sales and operations planningP2P1,8851,511+37412,7188,367+52%8.477%2.5 d
29Close managementR2R3,0613,221-16014,28011,618+23%4.468%4.7 d
30Cash and collectionsO2C2,8832,423+46011,3304,404+157%4.775%39.0 h
31Data qualityD&A3,2842,474+8107,9742,776+187%3.273%21.9 h
32Forecast deskP2P1,4801,256+22410,7987,109+52%8.678%7.9 d
33ReplenishmentP2P1,7851,782+311,52210,485+10%6.591%7.3 d
34Matter managementLGL1,0211,061-405,7264,231+35%5.477%6.0 d
35Quality controlM2D1,1611,337-1765,0444,311+17%3.883%4.6 d
36Obligation managementLGL1,9041,931-274,1793,770+11%2.286%36.1 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

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

H2REmployee lifecycle11,460 standing against a normal of 2,542 · +351%
A2LCampaign briefing12,545 standing against a normal of 3,061 · +310%
R2RReconciliation21,131 standing against a normal of 6,771 · +212%
D&AData quality7,974 standing against a normal of 2,776 · +187%
O2CCash and collections11,330 standing against a normal of 4,404 · +157%
O2CBilling and credit32,937 standing against a normal of 15,962 · +106%
H2RTime and claims75,488 standing against a normal of 44,451 · +70%
D&AReport certification14,878 standing against a normal of 9,618 · +55%
R2RPostings desk74,057 standing against a normal of 48,301 · +53%
P2PSales and operations planning12,718 standing against a normal of 8,367 · +52%
P2PForecast desk10,798 standing against a normal of 7,109 · +52%
S2PSupplier operations37,615 standing against a normal of 24,930 · +51%

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

The commitment on the day
117,266 of 154,383 items served cleared inside commitment — 76.0%.

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