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, Mar 7. 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, Mar 7
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 — 217,344 items standing and growing by 804 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 taking on 804 more items a day than it clears, so the share is rising. At the day service rate of 2,718 items, and only if nothing else arrived, what is already standing in it is 80.0 days of work. Its oldest item has been waiting 62.0 d, and 702 of the 2,718 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.

217,344
Standing
8.6%
Share of all standing work
3,522
Arrived on the day
2,718
Served on the day
+19%
Against its own normal
62.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 · 2,519,218 items standing · deepest is 217,344

■ 90%+ inside commitment■ 75 to 90%■ under 75%
S2PSource-to-Pay438,535 standing · 17.4% of the operation
Invoice processing
217,344+80462.0 d
Buying desk
155,390+52435.3 d
Supplier operations
65,801+3222.3 d
H2RHire-to-Retire341,152 standing · 13.5% of the operation
Payroll operations
175,305+86033.1 d
Time and claims
137,334+1,43921.3 d
Employee lifecycle
28,513+49716.9 d
O2COrder-to-Cash293,782 standing · 11.7% of the operation
Order desk
205,037+1,09751.4 d
Billing and credit
74,571+60012.0 d
Cash and collections
14,174+945.9 d
ITSIT Service290,928 standing · 11.5% of the operation
Incident desk
121,091+67363.1 d
Change and access
88,726+80341.8 d
Service requests
81,111+25234.3 d
M2DMake-to-Deliver273,155 standing · 10.8% of the operation
Move and deliver
147,406+76846.6 d
Make and release
116,196+1,20122.1 d
Quality control
9,553+8323.3 d
AIOAI Operations228,481 standing · 9.1% of the operation
Agent run desk
102,821+97418.6 d
Model routing
83,702+26845.0 d
Prompt and policy
41,958+53618.2 d
R2RRecord-to-Report184,785 standing · 7.3% of the operation
Postings desk
126,262-949.1 d
Reconciliation
34,141+73818.9 d
Close management
24,382+1839.3 d
C2LConcept-to-Launch176,746 standing · 7.0% of the operation
Artwork studio
80,801+30630.8 d
Formulation
68,837+22842.7 d
Launch gates
27,108+15928.9 d
A2LAwareness-to-Lead88,505 standing · 3.5% of the operation
Media operations
39,006+27340.7 d
Trade promotion
25,986+15829.7 d
Campaign briefing
23,513+6657.4 d
LGLLegal Operations69,443 standing · 2.8% of the operation
Contract desk
44,903+52820.2 d
Obligation management
14,464+33414.6 d
Matter management
10,076+12313.0 d
P2PPlan-to-Perform67,913 standing · 2.7% of the operation
Replenishment
26,283+23647.4 d
Sales and operations planning
22,884+24722.8 d
Forecast desk
18,746+27134.2 d
D&AData and Analytics65,793 standing · 2.6% of the operation
Report certification
28,041-7238.6 d
Metric governance
22,913+136.1 d
Data quality
14,839+2416.1 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,519,218 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

34 queues are taking on more than they clear

#QueueTowerArrivedServedNetStandingNormalvs normalDays of workInsideOldest
1Invoice processingS2P3,5222,718+804217,344182,032+19%80.074%62.0 d
2Order deskO2C2,6791,582+1,097205,037174,071+18%129.683%51.4 d
3Payroll operationsH2R3,2002,340+860175,305163,642+7%74.988%33.1 d
4Buying deskS2P3,8303,306+524155,390140,187+11%47.087%35.3 d
5Move and deliverM2D3,0352,267+768147,406132,096+12%65.075%46.6 d
6Time and claimsH2R3,8732,434+1,439137,334126,334+9%56.496%21.3 d
7Postings deskR2R2,5502,559-9126,262114,075+11%49.386%49.1 d
8Incident deskITS1,7391,066+673121,091104,070+16%113.692%63.1 d
9Make and releaseM2D2,5351,334+1,201116,196110,382+5%87.171%22.1 d
10Agent run deskAIO1,965991+974102,82188,692+16%103.886%18.6 d
11Change and accessITS1,9571,154+80388,72683,530+6%76.971%41.8 d
12Model routingAIO1,124856+26883,70279,933+5%97.894%45.0 d
13Service requestsITS2,1421,890+25281,11176,328+6%42.978%34.3 d
14Artwork studioC2L1,3911,085+30680,80169,902+16%74.588%30.8 d
15Billing and creditO2C3,3352,735+60074,57166,608+12%27.364%12.0 d
16FormulationC2L1,7271,499+22868,83767,129+3%45.994%42.7 d
17Supplier operationsS2P1,4021,370+3265,80164,280+2%48.072%22.3 d
18Contract deskLGL1,5941,066+52844,90335,151+28%42.187%20.2 d
19Prompt and policyAIO1,322786+53641,95839,009+8%53.493%18.2 d
20Media operationsA2L724451+27339,00633,655+16%86.571%40.7 d
21ReconciliationR2R1,8131,075+73834,14126,410+29%31.889%18.9 d
22Employee lifecycleH2R1,7671,270+49728,51327,606+3%22.595%16.9 d
23Report certificationD&A512584-7228,04123,721+18%48.086%38.6 d
24Launch gatesC2L629470+15927,10823,629+15%57.768%28.9 d
25ReplenishmentP2P595359+23626,28322,688+16%73.295%47.4 d
26Campaign briefingA2L1,8431,178+66523,51316,529+42%20.096%7.4 d
27Trade promotionA2L753595+15825,98620,665+26%43.777%29.7 d
28Close managementR2R1,151968+18324,38223,501+4%25.284%9.3 d
29Sales and operations planningP2P685438+24722,88421,565+6%52.267%22.8 d
30Metric governanceD&A457456+122,91319,316+19%50.279%36.1 d
31Forecast deskP2P542271+27118,74616,146+16%69.288%34.2 d
32Obligation managementLGL849515+33414,46412,861+12%28.185%14.6 d
33Data qualityD&A970729+24114,83914,273+4%20.492%6.1 d
34Cash and collectionsO2C961867+9414,17410,399+36%16.377%5.9 d
35Matter managementLGL454331+12310,0768,813+14%30.463%13.0 d
36Quality controlM2D392309+839,5537,765+23%30.984%23.3 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

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

A2LCampaign briefing23,513 standing against a normal of 16,529 · +42%
O2CCash and collections14,174 standing against a normal of 10,399 · +36%
R2RReconciliation34,141 standing against a normal of 26,410 · +29%
LGLContract desk44,903 standing against a normal of 35,151 · +28%
A2LTrade promotion25,986 standing against a normal of 20,665 · +26%
M2DQuality control9,553 standing against a normal of 7,765 · +23%
S2PInvoice processing217,344 standing against a normal of 182,032 · +19%
D&AMetric governance22,913 standing against a normal of 19,316 · +19%
D&AReport certification28,041 standing against a normal of 23,721 · +18%
O2COrder desk205,037 standing against a normal of 174,071 · +18%
ITSIncident desk121,091 standing against a normal of 104,070 · +16%
P2PForecast desk18,746 standing against a normal of 16,146 · +16%

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

The commitment on the day
36,309 of 43,904 items served cleared inside commitment — 82.7%.

7,595 items cleared outside their commitment. They are spread across 36 queues, and the deepest single contributor is Billing and credit with 979. 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.