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, May 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
Fri, May 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
Invoice processing in Source-to-Pay — 230,861 items standing and growing by 1,863 a day.

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

230,861
Standing
8.7%
Share of all standing work
11,981
Arrived on the day
10,118
Served on the day
+0%
Against its own normal
15.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,666,200 items standing · deepest is 230,861

■ 90%+ inside commitment■ 75 to 90%■ under 75%
S2PSource-to-Pay462,930 standing · 17.4% of the operation
Invoice processing
230,861+1,86315.3 d
Buying desk
166,826-2,7717.4 d
Supplier operations
65,243-3565.0 d
H2RHire-to-Retire385,996 standing · 14.5% of the operation
Payroll operations
202,769-8839.4 d
Time and claims
149,909-3,78618.9 d
Employee lifecycle
33,318-1,5317.4 d
ITSIT Service335,506 standing · 12.6% of the operation
Incident desk
138,406+9758.6 d
Change and access
101,195+8336.6 d
Service requests
95,905+31218.5 d
M2DMake-to-Deliver314,452 standing · 11.8% of the operation
Move and deliver
162,823-1,78721.4 d
Make and release
143,970-1488.6 d
Quality control
7,659+872.9 d
O2COrder-to-Cash276,453 standing · 10.4% of the operation
Order desk
205,634-4979.5 d
Billing and credit
59,899-1,3907.2 d
Cash and collections
10,920-1692.2 d
AIOAI Operations252,951 standing · 9.5% of the operation
Agent run desk
110,538+82111.2 d
Model routing
95,288-59227.4 d
Prompt and policy
47,125-5294.8 d
C2LConcept-to-Launch195,541 standing · 7.3% of the operation
Artwork studio
88,868+63014.2 d
Formulation
80,880-3449.0 d
Launch gates
25,793-4367.0 d
R2RRecord-to-Report165,341 standing · 6.2% of the operation
Postings desk
125,655-94620.7 d
Reconciliation
20,059-1,1722.4 d
Close management
19,627-4573.3 d
A2LAwareness-to-Lead74,773 standing · 2.8% of the operation
Media operations
43,317+1187.1 d
Trade promotion
21,392-5208.2 d
Campaign briefing
10,064-20245.8 h
P2PPlan-to-Perform73,710 standing · 2.8% of the operation
Sales and operations planning
27,965+1857.3 d
Replenishment
25,442+12213.5 d
Forecast desk
20,303-31414.9 d
LGLLegal Operations67,505 standing · 2.5% of the operation
Contract desk
43,375-1,2527.0 d
Obligation management
14,112-1163.8 d
Matter management
10,018-3795.6 d
D&AData and Analytics61,042 standing · 2.3% of the operation
Report certification
26,798-56812.6 d
Metric governance
24,893-1209.8 d
Data quality
9,351-8984.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,666,200 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

10 queues are taking on more than they clear

#QueueTowerArrivedServedNetStandingNormalvs normalDays of workInsideOldest
1Invoice processingS2P11,98110,118+1,863230,861230,241+0%22.888%15.3 d
2Order deskO2C7,6658,162-497205,634203,278+1%25.264%9.5 d
3Payroll operationsH2R7,7238,606-883202,769196,725+3%23.677%9.4 d
4Buying deskS2P7,55010,321-2,771166,826180,215-7%16.271%7.4 d
5Move and deliverM2D6,5538,340-1,787162,823164,916-1%19.577%21.4 d
6Time and claimsH2R8,03111,817-3,786149,909168,240-11%12.783%18.9 d
7Make and releaseM2D4,8044,952-148143,970138,808+4%29.197%8.6 d
8Incident deskITS5,2544,279+975138,406139,638-1%32.382%8.6 d
9Postings deskR2R6,3687,314-946125,655136,758-8%17.296%20.7 d
10Agent run deskAIO4,9444,123+821110,538104,182+6%26.865%11.2 d
11Change and accessITS4,8774,044+833101,19596,705+5%25.078%6.6 d
12Service requestsITS5,0074,695+31295,90596,026-0%20.473%18.5 d
13Model routingAIO3,6174,209-59295,28895,483-0%22.687%27.4 d
14Artwork studioC2L3,2492,619+63088,86886,345+3%33.967%14.2 d
15FormulationC2L3,7334,077-34480,88082,672-2%19.887%9.0 d
16Supplier operationsS2P4,9935,349-35665,24372,949-11%12.266%5.0 d
17Billing and creditO2C6,5867,976-1,39059,89964,075-7%7.568%7.2 d
18Prompt and policyAIO2,9123,441-52947,12548,159-2%13.779%4.8 d
19Media operationsA2L2,0261,908+11843,31741,987+3%22.775%7.1 d
20Contract deskLGL3,8935,145-1,25243,37545,434-5%8.464%7.0 d
21Employee lifecycleH2R3,6985,229-1,53133,31838,156-13%6.479%7.4 d
22Sales and operations planningP2P1,4541,269+18527,96526,288+6%22.090%7.3 d
23Report certificationD&A1,5182,086-56826,79828,847-7%12.873%12.6 d
24ReplenishmentP2P1,4981,376+12225,44223,803+7%18.579%13.5 d
25Launch gatesC2L1,7102,146-43625,79326,710-3%12.075%7.0 d
26Metric governanceD&A1,3171,437-12024,89325,783-3%17.393%9.8 d
27Trade promotionA2L2,0592,579-52021,39222,848-6%8.389%8.2 d
28Forecast deskP2P1,3801,694-31420,30322,027-8%12.063%14.9 d
29ReconciliationR2R4,8376,009-1,17220,05927,861-28%3.375%2.4 d
30Close managementR2R2,4932,950-45719,62724,920-21%6.772%3.3 d
31Obligation managementLGL1,8401,956-11614,11212,493+13%7.271%3.8 d
32Cash and collectionsO2C2,9553,124-16910,92016,825-35%3.580%2.2 d
33Campaign briefingA2L4,2894,491-20210,06415,001-33%2.286%45.8 h
34Matter managementLGL8571,236-37910,01810,939-8%8.168%5.6 d
35Data qualityD&A2,2283,126-8989,35115,318-39%3.072%4.4 d
36Quality controlM2D1,072985+877,6596,397+20%7.886%2.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

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

M2DQuality control7,659 standing against a normal of 6,397 · +20%
LGLObligation management14,112 standing against a normal of 12,493 · +13%
The commitment on the day
126,585 of 163,188 items served cleared inside commitment — 77.6%.

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