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 Sat, Jan 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
Sat, Jan 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 — 150,861 items standing and growing by 221 a day.

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

150,861
Standing
8.2%
Share of all standing work
3,449
Arrived on the day
3,228
Served on the day
+0%
Against its own normal
26.1 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,840,476 items standing · deepest is 150,861

■ 90%+ inside commitment■ 75 to 90%■ under 75%
S2PSource-to-Pay319,530 standing · 17.4% of the operation
Invoice processing
150,861+22126.1 d
Buying desk
107,708+14237.4 d
Supplier operations
60,961+69720.6 d
H2RHire-to-Retire276,960 standing · 15.0% of the operation
Payroll operations
127,778+1,59513.7 d
Time and claims
118,550-19710.9 d
Employee lifecycle
30,632-17823.5 d
ITSIT Service212,082 standing · 11.5% of the operation
Incident desk
83,183-37540.8 d
Change and access
65,222+43233.6 d
Service requests
63,677-4839.7 d
O2COrder-to-Cash198,884 standing · 10.8% of the operation
Order desk
139,495+30113.1 d
Billing and credit
45,453+10215.1 d
Cash and collections
13,936+2955.6 d
M2DMake-to-Deliver189,239 standing · 10.3% of the operation
Move and deliver
95,419+12718.0 d
Make and release
88,459+28359.4 d
Quality control
5,361+2427.7 d
AIOAI Operations165,168 standing · 9.0% of the operation
Model routing
66,101+63228.6 d
Agent run desk
64,176-5838.3 d
Prompt and policy
34,891+81425.1 d
R2RRecord-to-Report136,064 standing · 7.4% of the operation
Postings desk
90,022+30728.5 d
Reconciliation
26,303-10810.2 d
Close management
19,739+3888.7 d
C2LConcept-to-Launch131,460 standing · 7.1% of the operation
Artwork studio
54,913+28832.1 d
Formulation
54,558+4728.0 d
Launch gates
21,989+14211.4 d
A2LAwareness-to-Lead64,296 standing · 3.5% of the operation
Media operations
25,148+11436.9 d
Campaign briefing
20,204-48910.9 d
Trade promotion
18,944+16721.7 d
D&AData and Analytics50,115 standing · 2.7% of the operation
Report certification
16,972-1017.4 d
Metric governance
16,808+22516.3 d
Data quality
16,335+8621.4 d
P2PPlan-to-Perform48,947 standing · 2.7% of the operation
Sales and operations planning
16,599+16219.9 d
Replenishment
16,408+8343.6 d
Forecast desk
15,940+10332.4 d
LGLLegal Operations47,731 standing · 2.6% of the operation
Contract desk
31,106-6523.2 d
Obligation management
10,465+26111.1 d
Matter management
6,160+638.5 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 1,840,476 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

27 queues are taking on more than they clear

#QueueTowerArrivedServedNetStandingNormalvs normalDays of workInsideOldest
1Invoice processingS2P3,4493,228+221150,861150,806+0%46.778%26.1 d
2Order deskO2C2,8482,547+301139,495134,948+3%54.889%13.1 d
3Payroll operationsH2R3,6392,044+1,595127,778103,876+23%62.570%13.7 d
4Time and claimsH2R3,2343,431-197118,550109,109+9%34.665%10.9 d
5Buying deskS2P2,2512,109+142107,708107,869-0%51.177%37.4 d
6Move and deliverM2D2,3342,207+12795,41988,455+8%43.293%18.0 d
7Postings deskR2R2,2691,962+30790,02285,174+6%45.980%28.5 d
8Make and releaseM2D1,4841,201+28388,45981,002+9%73.785%59.4 d
9Incident deskITS1,3171,692-37583,18378,829+6%49.288%40.8 d
10Model routingAIO1,614982+63266,10155,379+19%67.368%28.6 d
11Change and accessITS2,0071,575+43265,22258,684+11%41.475%33.6 d
12Supplier operationsS2P2,1611,464+69760,96152,934+15%41.662%20.6 d
13Agent run deskAIO1,2541,312-5864,17660,770+6%48.962%38.3 d
14Service requestsITS1,2951,343-4863,67752,323+22%47.481%39.7 d
15Artwork studioC2L983695+28854,91350,560+9%79.075%32.1 d
16FormulationC2L993946+4754,55843,871+24%57.772%28.0 d
17Billing and creditO2C3,0232,921+10245,45346,117-1%15.695%15.1 d
18Prompt and policyAIO1,426612+81434,89130,173+16%57.082%25.1 d
19Contract deskLGL1,3181,383-6531,10627,968+11%22.563%23.2 d
20Employee lifecycleH2R1,0841,262-17830,63225,997+18%24.380%23.5 d
21ReconciliationR2R2,0392,147-10826,30327,942-6%12.395%10.2 d
22Media operationsA2L692578+11425,14824,069+4%43.568%36.9 d
23Launch gatesC2L735593+14221,98918,810+17%37.196%11.4 d
24Close managementR2R1,097709+38819,73916,530+19%27.876%8.7 d
25Campaign briefingA2L1,3391,828-48920,20423,672-15%11.183%10.9 d
26Trade promotionA2L906739+16718,94418,411+3%25.671%21.7 d
27Metric governanceD&A559334+22516,80816,685+1%50.393%16.3 d
28Sales and operations planningP2P654492+16216,59915,139+10%33.783%19.9 d
29Report certificationD&A501511-1016,97217,154-1%33.264%17.4 d
30ReplenishmentP2P382299+8316,40813,918+18%54.963%43.6 d
31Data qualityD&A792706+8616,33514,217+15%23.184%21.4 d
32Forecast deskP2P498395+10315,94014,277+12%40.493%32.4 d
33Cash and collectionsO2C1,167872+29513,93615,207-8%16.097%5.6 d
34Obligation managementLGL723462+26110,4657,901+32%22.766%11.1 d
35Quality controlM2D498256+2425,3615,087+5%20.991%7.7 d
36Matter managementLGL358295+636,1605,854+5%20.980%8.5 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

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

LGLObligation management10,465 standing against a normal of 7,901 · +32%
C2LFormulation54,558 standing against a normal of 43,871 · +24%
H2RPayroll operations127,778 standing against a normal of 103,876 · +23%
ITSService requests63,677 standing against a normal of 52,323 · +22%
R2RClose management19,739 standing against a normal of 16,530 · +19%
AIOModel routing66,101 standing against a normal of 55,379 · +19%
P2PReplenishment16,408 standing against a normal of 13,918 · +18%
H2REmployee lifecycle30,632 standing against a normal of 25,997 · +18%
C2LLaunch gates21,989 standing against a normal of 18,810 · +17%
AIOPrompt and policy34,891 standing against a normal of 30,173 · +16%
S2PSupplier operations60,961 standing against a normal of 52,934 · +15%
D&AData quality16,335 standing against a normal of 14,217 · +15%

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

The commitment on the day
36,635 of 46,132 items served cleared inside commitment — 79.4%.

9,497 items cleared outside their commitment. They are spread across 36 queues, and the deepest single contributor is Time and claims with 1,190. 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.