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 Fri, Apr 17. 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
Fri, Apr 17
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 — 232,142 items standing and draining by 34 a day.

Of the 36 queues on this canvas, this one is ranked first because releasing it frees the most work: it holds 8.6% of everything standing, and it is not growing, so the ranking is driven by the standing depth alone. At the day service rate of 11,923 items, and only if nothing else arrived, what is already standing in it is 19.5 days of work; work does keep arriving, and at the rate it is actually falling it takes 6,828 days to empty. Its oldest item has been waiting 6.5 d, and 1,715 of the 11,923 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.

232,142
Standing
8.6%
Share of all standing work
11,889
Arrived on the day
11,923
Served on the day
-3%
Against its own normal
6.5 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,701,475 items standing · deepest is 232,142

■ 90%+ inside commitment■ 75 to 90%■ under 75%
S2PSource-to-Pay487,194 standing · 18.0% of the operation
Invoice processing
232,142-346.5 d
Buying desk
177,414+1,8468.1 d
Supplier operations
77,638-5207.4 d
H2RHire-to-Retire385,855 standing · 14.3% of the operation
Payroll operations
179,491+1,4419.1 d
Time and claims
171,183+1,00414.0 d
Employee lifecycle
35,181-1396.9 d
ITSIT Service325,225 standing · 12.0% of the operation
Incident desk
139,590+276.9 d
Change and access
96,940-888.6 d
Service requests
88,695-15711.0 d
O2COrder-to-Cash296,998 standing · 11.0% of the operation
Order desk
203,914-1,84325.9 d
Billing and credit
72,246-2,9105.8 d
Cash and collections
20,838-438.0 d
M2DMake-to-Deliver291,673 standing · 10.8% of the operation
Move and deliver
152,053+67914.7 d
Make and release
133,863-1,29310.1 d
Quality control
5,757+273.8 d
AIOAI Operations234,196 standing · 8.7% of the operation
Agent run desk
98,842-61113.5 d
Model routing
89,818+2607.1 d
Prompt and policy
45,536+33511.9 d
R2RRecord-to-Report205,619 standing · 7.6% of the operation
Postings desk
141,573+1,74912.0 d
Reconciliation
35,981-1,1614.0 d
Close management
28,065+3063.0 d
C2LConcept-to-Launch186,940 standing · 6.9% of the operation
Artwork studio
83,234-48027.1 d
Formulation
78,395+7718.6 d
Launch gates
25,311-129.9 d
A2LAwareness-to-Lead81,305 standing · 3.0% of the operation
Media operations
39,478+3436.3 d
Campaign briefing
21,194-7242.1 d
Trade promotion
20,633-129.0 d
D&AData and Analytics72,786 standing · 2.7% of the operation
Report certification
28,349+30714.9 d
Metric governance
26,382-18117.0 d
Data quality
18,055-2365.0 d
P2PPlan-to-Perform71,931 standing · 2.7% of the operation
Sales and operations planning
25,759+5210.1 d
Forecast desk
23,462+2065.3 d
Replenishment
22,710-1228.9 d
LGLLegal Operations61,753 standing · 2.3% of the operation
Contract desk
41,281+1587.7 d
Matter management
10,278+638.0 d
Obligation management
10,194-545.4 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,701,475 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

17 queues are taking on more than they clear

#QueueTowerArrivedServedNetStandingNormalvs normalDays of workInsideOldest
1Invoice processingS2P11,88911,923-34232,142239,500-3%19.586%6.5 d
2Order deskO2C7,7529,595-1,843203,914212,346-4%21.369%25.9 d
3Payroll operationsH2R8,8647,423+1,441179,491171,474+5%24.269%9.1 d
4Buying deskS2P10,1348,288+1,846177,414161,954+10%21.481%8.1 d
5Time and claimsH2R10,3219,317+1,004171,183160,450+7%18.473%14.0 d
6Move and deliverM2D7,7027,023+679152,053142,423+7%21.790%14.7 d
7Postings deskR2R8,1466,397+1,749141,573130,452+9%22.181%12.0 d
8Incident deskITS5,4475,420+27139,590137,833+1%25.885%6.9 d
9Make and releaseM2D5,1566,449-1,293133,863132,535+1%20.880%10.1 d
10Agent run deskAIO4,5275,138-61198,842102,918-4%19.288%13.5 d
11Change and accessITS5,5185,606-8896,94097,127-0%17.375%8.6 d
12Model routingAIO3,5083,248+26089,81885,853+5%27.792%7.1 d
13Service requestsITS4,5394,696-15788,69584,286+5%18.971%11.0 d
14Artwork studioC2L3,1613,641-48083,23484,466-1%22.966%27.1 d
15FormulationC2L4,0433,272+77178,39571,494+10%24.089%8.6 d
16Supplier operationsS2P4,5025,022-52077,63876,090+2%15.576%7.4 d
17Billing and creditO2C7,09210,002-2,91072,24674,932-4%7.284%5.8 d
18Prompt and policyAIO3,4613,126+33545,53646,333-2%14.693%11.9 d
19Contract deskLGL3,9103,752+15841,28143,538-5%11.080%7.7 d
20Media operationsA2L2,2571,914+34339,47840,234-2%20.669%6.3 d
21ReconciliationR2R5,7256,886-1,16135,98144,214-19%5.292%4.0 d
22Employee lifecycleH2R3,9134,052-13935,18131,134+13%8.776%6.9 d
23Report certificationD&A1,8391,532+30728,34926,666+6%18.588%14.9 d
24Close managementR2R3,1902,884+30628,06525,742+9%9.780%3.0 d
25Metric governanceD&A1,3701,551-18126,38226,480-0%17.075%17.0 d
26Sales and operations planningP2P1,6461,594+5225,75926,245-2%16.266%10.1 d
27Launch gatesC2L2,0472,059-1225,31127,207-7%12.378%9.9 d
28Forecast deskP2P1,6411,435+20623,46222,958+2%16.372%5.3 d
29ReplenishmentP2P1,4371,559-12222,71024,882-9%14.680%8.9 d
30Campaign briefingA2L5,1205,844-72421,19427,741-24%3.666%2.1 d
31Cash and collectionsO2C2,9252,968-4320,83820,818+0%7.073%8.0 d
32Trade promotionA2L2,2732,285-1220,63322,003-6%9.089%9.0 d
33Data qualityD&A2,6452,881-23618,05518,063-0%6.386%5.0 d
34Matter managementLGL996933+6310,2789,511+8%11.083%8.0 d
35Obligation managementLGL1,9592,013-5410,19411,594-12%5.190%5.4 d
36Quality controlM2D1,3161,289+275,7577,350-22%4.588%3.8 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

1 queue is more than ten percent above their own 27 day mean

H2REmployee lifecycle35,181 standing against a normal of 31,134 · +13%
The commitment on the day
129,915 of 163,017 items served cleared inside commitment — 79.7%.

33,102 items cleared outside their commitment. They are spread across 36 queues, and the deepest single contributor is Order desk with 3,012. 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.