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 Sun, Aug 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
Sun, Aug 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
Buying desk in Source-to-Pay — 5,605 items standing and growing by 740 a day.

Of the 36 queues on this canvas, this one is ranked first because releasing it frees the most work: it holds 7.0% of everything standing, and it is taking on 740 more items a day than it clears, so the share is rising. At the day service rate of 1,833 items, and only if nothing else arrived, what is already standing in it is 3.1 days of work. Its oldest item has been waiting 32.5 h, and 209 of the 1,833 items it did serve cleared outside commitment.

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

5,605
Standing
7.0%
Share of all standing work
2,573
Arrived on the day
1,833
Served on the day
No prior days
Against its own normal
32.5 h
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 · 79,873 items standing · deepest is 5,605

■ 90%+ inside commitment■ 75 to 90%■ under 75%
S2PSource-to-Pay11,436 standing · 14.3% of the operation
Buying desk
5,605+74032.5 h
Invoice processing
4,734+2742.7 h
Supplier operations
1,097-38925.3 h
O2COrder-to-Cash10,843 standing · 13.6% of the operation
Order desk
5,288+13321.0 h
Billing and credit
3,832+3182.1 d
Cash and collections
1,723+1602.0 d
H2RHire-to-Retire10,445 standing · 13.1% of the operation
Time and claims
5,097+1452.3 d
Payroll operations
3,968+58811.1 h
Employee lifecycle
1,380+29231.6 h
AIOAI Operations7,907 standing · 9.9% of the operation
Agent run desk
3,284+69127.4 h
Model routing
2,444+4592.0 d
Prompt and policy
2,179+862.6 d
ITSIT Service7,308 standing · 9.1% of the operation
Service requests
3,033-92.2 d
Change and access
2,502+46047.8 h
Incident desk
1,773+41529.5 h
R2RRecord-to-Report6,318 standing · 7.9% of the operation
Reconciliation
3,090+992.3 d
Close management
1,818-242.1 d
Postings desk
1,410-48917.0 h
C2LConcept-to-Launch5,793 standing · 7.3% of the operation
Formulation
2,787+19733.8 h
Artwork studio
2,361+22243.0 h
Launch gates
645+662.2 d
A2LAwareness-to-Lead5,107 standing · 6.4% of the operation
Campaign briefing
3,367+4612.3 d
Trade promotion
1,168+15735.6 h
Media operations
572-16120.8 h
M2DMake-to-Deliver4,951 standing · 6.2% of the operation
Make and release
3,170-28041.3 h
Move and deliver
1,394-72629.0 h
Quality control
387-10236.7 h
LGLLegal Operations4,710 standing · 5.9% of the operation
Contract desk
2,848+20246.7 h
Obligation management
1,384+5543.4 h
Matter management
478-992.3 d
D&AData and Analytics3,226 standing · 4.0% of the operation
Data quality
1,409+42832.4 h
Report certification
1,177+26043.7 h
Metric governance
640-122.1 d
P2PPlan-to-Perform1,829 standing · 2.3% of the operation
Sales and operations planning
806+20743.5 h
Forecast desk
555+2230.7 h
Replenishment
468+1915.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 79,873 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

26 queues are taking on more than they clear

#QueueTowerArrivedServedNetStandingNormalvs normalDays of workInsideOldest
1Buying deskS2P2,5731,833+7405,6050—3.189%32.5 h
2Payroll operationsH2R2,6662,078+5883,9680—1.990%11.1 h
3Agent run deskAIO1,7641,073+6913,2840—3.185%27.4 h
4Order deskO2C2,1131,980+1335,2880—2.795%21.0 h
5Time and claimsH2R3,2613,116+1455,0970—1.687%2.3 d
6Campaign briefingA2L1,6221,161+4613,3670—2.982%2.3 d
7Billing and creditO2C2,0121,694+3183,8320—2.374%2.1 d
8Invoice processingS2P3,0313,004+274,7340—1.678%42.7 h
9Change and accessITS1,8111,351+4602,5020—1.990%47.8 h
10Model routingAIO1,267808+4592,4440—3.074%2.0 d
11Contract deskLGL1,3051,103+2022,8480—2.687%46.7 h
12Incident deskITS1,7011,286+4151,7730—1.472%29.5 h
13FormulationC2L906709+1972,7870—3.992%33.8 h
14ReconciliationR2R1,6171,518+993,0900—2.073%2.3 d
15Data qualityD&A952524+4281,4090—2.771%32.4 h
16Artwork studioC2L905683+2222,3610—3.575%43.0 h
17Make and releaseM2D1,7662,046-2803,1700—1.586%41.3 h
18Service requestsITS1,5431,552-93,0330—2.081%2.2 d
19Employee lifecycleH2R1,4711,179+2921,3800—1.278%31.6 h
20Prompt and policyAIO979893+862,1790—2.463%2.6 d
21Cash and collectionsO2C716556+1601,7230—3.185%2.0 d
22Report certificationD&A591331+2601,1770—3.673%43.7 h
23Trade promotionA2L898741+1571,1680—1.668%35.6 h
24Sales and operations planningP2P528321+2078060—2.587%43.5 h
25Close managementR2R876900-241,8180—2.081%2.1 d
26Obligation managementLGL655600+551,3840—2.371%43.4 h
27Postings deskR2R1,9242,413-4891,4100—0.678%17.0 h
28Move and deliverM2D1,7552,481-7261,3940—0.672%29.0 h
29Supplier operationsS2P1,0811,470-3891,0970—0.778%25.3 h
30Launch gatesC2L409343+666450—1.969%2.2 d
31Forecast deskP2P501479+225550—1.281%30.7 h
32Metric governanceD&A410422-126400—1.589%2.1 d
33Media operationsA2L522683-1615720—0.890%20.8 h
34ReplenishmentP2P453434+194680—1.180%15.1 h
35Matter managementLGL217316-994780—1.592%2.3 d
36Quality controlM2D255357-1023870—1.163%36.7 h

"Normal" is the mean standing depth for that same queue over the 0 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

No queue is more than ten percent above its own 27 day mean

Every queue on this day is running at or below its own 27 day mean depth. That is a statement about variation, not about health: 79,873 items are still standing and 19.1% of what was served cleared outside commitment.

The commitment on the day
34,350 of 42,438 items served cleared inside commitment — 80.9%.

8,088 items cleared outside their commitment. They are spread across 36 queues, and the deepest single contributor is Move and deliver with 684. 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.