Operate · the run state
Every queue, one day, one canvas
This is the operation as it stood at the close of Thu, Aug 13. 36 queues across 12 towers, ranked not by how large they are but by how fast they are changing … more
Health
What the day did to the operation
Arrival against service is the only pair that tells you whether tomorrow is worse than today. more
Of the 36 queues on this canvas, this one is ranked first because releasing it frees the most work: it holds 9.8% of everything standing, and it is taking on 1,660 more items a day than it clears, so the share is rising. At the day service rate of 9,403 items, and only if nothing else arrived, what is already standing in it is 17.0 days of work. Its oldest item has been waiting 16.0 d, and 1,239 of the 9,403 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.
Detail on the record
The blockage map
Every queue in the operation, grouped by tower. more
All queues at the close of the day
36 queues · 1,630,306 items standing · deepest is 167,044
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,630,306 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. more
Every queue, ranked by what releasing it frees
8 queues are taking on more than they clear
| # | Queue | Tower | Arrived | Served | Net | Standing | Normal | vs normal | Days of work | Inside | Oldest |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | Invoice processing | S2P | 11,063 | 9,403 | +1,660 | 159,808 | 168,301 | -5% | 17.0 | 87% | 16.0 d |
| 2 | Order desk | O2C | 7,942 | 8,438 | -496 | 167,044 | 176,462 | -5% | 19.8 | 63% | 18.0 d |
| 3 | Payroll operations | H2R | 7,110 | 7,595 | -485 | 160,598 | 158,513 | +1% | 21.1 | 77% | 15.1 d |
| 4 | Incident desk | ITS | 4,265 | 3,830 | +435 | 125,091 | 123,154 | +2% | 32.7 | 64% | 7.6 d |
| 5 | Buying desk | S2P | 8,461 | 9,180 | -719 | 120,116 | 127,789 | -6% | 13.1 | 87% | 14.1 d |
| 6 | Make and release | M2D | 5,301 | 4,853 | +448 | 114,945 | 115,263 | -0% | 23.7 | 71% | 20.4 d |
| 7 | Agent run desk | AIO | 4,781 | 4,084 | +697 | 84,806 | 83,155 | +2% | 20.8 | 84% | 14.9 d |
| 8 | Move and deliver | M2D | 6,383 | 7,619 | -1,236 | 86,187 | 110,994 | -22% | 11.3 | 63% | 5.9 d |
| 9 | Postings desk | R2R | 6,670 | 9,054 | -2,384 | 85,547 | 95,492 | -10% | 9.4 | 90% | 9.8 d |
| 10 | Artwork studio | C2L | 2,681 | 3,018 | -337 | 72,578 | 72,476 | +0% | 24.0 | 86% | 17.6 d |
| 11 | Model routing | AIO | 3,808 | 4,570 | -762 | 70,073 | 79,394 | -12% | 15.3 | 63% | 9.2 d |
| 12 | Time and claims | H2R | 8,120 | 12,739 | -4,619 | 67,911 | 91,812 | -26% | 5.3 | 92% | 8.6 d |
| 13 | Change and access | ITS | 4,258 | 4,045 | +213 | 64,855 | 66,550 | -3% | 16.0 | 79% | 12.7 d |
| 14 | Service requests | ITS | 4,398 | 4,930 | -532 | 58,900 | 63,867 | -8% | 11.9 | 79% | 5.3 d |
| 15 | Formulation | C2L | 3,233 | 4,260 | -1,027 | 47,689 | 56,569 | -16% | 11.2 | 76% | 9.1 d |
| 16 | Media operations | A2L | 2,019 | 2,224 | -205 | 29,783 | 31,425 | -5% | 13.4 | 71% | 7.0 d |
| 17 | Prompt and policy | AIO | 2,918 | 3,538 | -620 | 20,795 | 28,814 | -28% | 5.9 | 88% | 6.8 d |
| 18 | Supplier operations | S2P | 4,633 | 5,378 | -745 | 16,295 | 31,396 | -48% | 3.0 | 77% | 2.7 d |
| 19 | Sales and operations planning | P2P | 1,320 | 1,426 | -106 | 15,606 | 17,083 | -9% | 10.9 | 89% | 5.8 d |
| 20 | Replenishment | P2P | 1,543 | 1,246 | +297 | 13,219 | 13,768 | -4% | 10.6 | 87% | 7.1 d |
| 21 | Metric governance | D&A | 1,450 | 1,369 | +81 | 14,285 | 16,757 | -15% | 10.4 | 82% | 8.3 d |
| 22 | Launch gates | C2L | 1,637 | 1,653 | -16 | 12,272 | 12,880 | -5% | 7.4 | 90% | 6.3 d |
| 23 | Forecast desk | P2P | 1,403 | 1,495 | -92 | 9,009 | 11,763 | -23% | 6.0 | 62% | 3.8 d |
| 24 | Report certification | D&A | 1,566 | 1,971 | -405 | 8,452 | 10,811 | -22% | 4.3 | 78% | 5.6 d |
| 25 | Contract desk | LGL | 4,504 | 5,047 | -543 | 2,720 | 7,155 | -62% | 0.5 | 85% | 12.3 h |
| 26 | Campaign briefing | A2L | 4,718 | 4,498 | +220 | 220 | 34 | +539% | 0.0 | 81% | 4.7 h |
| 27 | Close management | R2R | 2,374 | 2,396 | -22 | 954 | 1,975 | -52% | 0.4 | 63% | 11.2 h |
| 28 | Matter management | LGL | 1,000 | 1,018 | -18 | 548 | 2,458 | -78% | 0.5 | 63% | 27.4 h |
| 29 | Employee lifecycle | H2R | 3,653 | 3,653 | 0 | 0 | 87 | -100% | 0.0 | 72% | 0 min |
| 30 | Reconciliation | R2R | 4,520 | 4,520 | 0 | 0 | 0 | — | 0.0 | 88% | 0 min |
| 31 | Quality control | M2D | 1,086 | 1,086 | 0 | 0 | 29 | -100% | 0.0 | 74% | 0 min |
| 32 | Billing and credit | O2C | 7,021 | 7,021 | 0 | 0 | 2,126 | -100% | 0.0 | 78% | 0 min |
| 33 | Trade promotion | A2L | 2,260 | 2,260 | 0 | 0 | 45 | -100% | 0.0 | 90% | 0 min |
| 34 | Data quality | D&A | 2,542 | 2,542 | 0 | 0 | 7 | -100% | 0.0 | 82% | 0 min |
| 35 | Obligation management | LGL | 1,649 | 1,649 | 0 | 0 | 18 | -100% | 0.0 | 62% | 0 min |
| 36 | Cash and collections | O2C | 2,945 | 2,945 | 0 | 0 | 128 | -100% | 0.0 | 72% | 0 min |
"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
32,851 items cleared outside their commitment. They are spread across 36 queues, and the deepest single contributor is Order desk with 3,157. Commitment here is measured against what was served on the day; items still standing have not yet been judged against it.
Actions
What is waiting on a person
A queue is worth acting on when it is growing, not when it is large. more
Recover a queue missing its commitment
Some of what was served on the day cleared outside the service level for that queue.
Add service to a growing queue
More arrived than was served on the day on screen, so the queue is deeper tonight than this morning.
Break up a queue holding over three days of work
At the day service rate, clearing what is already in it takes more than three days.
Escalate an item older than 72 hours
The oldest item in the queue has been waiting three days or more.
Explain a queue running above its own normal
Depth is more than ten percent above the mean of the prior 27 days for that same queue.
Operations
What this desk is allowed to start
A surface that only reports is not operable. more
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. more
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
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. more
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. more
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.