Operate · the run state
Every queue, one day, one canvas
This is the operation as it stood at the close of Tue, Jul 28. 36 queues across 12 towers, ranked not by how large they are but by how fast they are changing — a small queue that is growing binds the operation sooner than a large one that is draining. Unlike the ledger beside it, nothing on this page is sampled: these are full population arrival and service counts for every queue, every 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. Depth on its own does not.
Of the 36 queues on this canvas, this one is ranked first because releasing it frees the most work: it holds 14.5% of everything standing, and it is taking on 438 more items a day than it clears, so the share is rising. At the day service rate of 10,276 items, and only if nothing else arrived, what is already standing in it is 6.1 days of work. Its oldest item has been waiting 5.9 d, and 2,459 of the 10,276 items it did serve cleared outside commitment.
The name recorded against most of the work in this queue in the sampled ledger week is Tomas Havel. That is who this constraint belongs to.
Live observability
The blockage map
Every queue in the operation, grouped by tower. Width is how much work is standing in it; color is whether what it served on the day cleared inside commitment.
All queues at the close of the day
36 queues · 430,229 items standing · deepest is 62,355
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 430,229 on the tile above. A queue opens the series with work already in it, so standing depth is not arrivals minus service.
Actions
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. A queue can rank above a deeper one purely because it is growing.
Every queue, ranked by what releasing it frees
5 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 | 10,714 | 10,276 | +438 | 62,355 | 53,870 | +16% | 6.1 | 76% | 5.9 d |
| 2 | Order desk | O2C | 7,370 | 9,646 | -2,276 | 46,898 | 52,606 | -11% | 4.9 | 62% | 4.9 d |
| 3 | Buying desk | S2P | 8,183 | 9,217 | -1,034 | 35,715 | 42,690 | -16% | 3.9 | 76% | 3.9 d |
| 4 | Postings desk | R2R | 6,808 | 7,722 | -914 | 32,614 | 36,289 | -10% | 4.2 | 68% | 3.0 d |
| 5 | Incident desk | ITS | 4,021 | 4,237 | -216 | 26,785 | 18,850 | +42% | 6.3 | 63% | 4.1 d |
| 6 | Agent run desk | AIO | 3,978 | 4,818 | -840 | 25,800 | 26,948 | -4% | 5.4 | 77% | 3.4 d |
| 7 | Model routing | AIO | 3,410 | 4,169 | -759 | 19,858 | 19,451 | +2% | 4.8 | 76% | 3.6 d |
| 8 | Make and release | M2D | 4,270 | 5,510 | -1,240 | 19,723 | 16,759 | +18% | 3.6 | 88% | 2.1 d |
| 9 | Move and deliver | M2D | 7,015 | 6,799 | +216 | 17,643 | 11,423 | +54% | 2.6 | 68% | 42.0 h |
| 10 | Artwork studio | C2L | 2,738 | 3,423 | -685 | 15,766 | 18,453 | -15% | 4.6 | 73% | 5.7 d |
| 11 | Payroll operations | H2R | 7,311 | 9,006 | -1,695 | 15,686 | 22,589 | -31% | 1.7 | 62% | 2.2 d |
| 12 | Change and access | ITS | 4,647 | 4,574 | +73 | 14,737 | 11,737 | +26% | 3.2 | 86% | 3.5 d |
| 13 | Time and claims | H2R | 7,263 | 9,190 | -1,927 | 13,074 | 10,771 | +21% | 1.4 | 85% | 2.0 d |
| 14 | Cash and collections | O2C | 2,298 | 3,014 | -716 | 10,105 | 11,287 | -10% | 3.4 | 69% | 3.0 d |
| 15 | Prompt and policy | AIO | 2,778 | 2,651 | +127 | 9,103 | 10,528 | -14% | 3.4 | 75% | 47.0 h |
| 16 | Formulation | C2L | 3,532 | 4,359 | -827 | 9,539 | 14,457 | -34% | 2.2 | 85% | 41.6 h |
| 17 | Reconciliation | R2R | 4,782 | 5,307 | -525 | 9,167 | 11,868 | -23% | 1.7 | 86% | 2.1 d |
| 18 | Media operations | A2L | 1,493 | 1,975 | -482 | 8,703 | 7,063 | +23% | 4.4 | 87% | 5.0 d |
| 19 | Trade promotion | A2L | 2,314 | 2,189 | +125 | 4,518 | 4,575 | -1% | 2.1 | 88% | 2.7 d |
| 20 | Billing and credit | O2C | 7,274 | 8,372 | -1,098 | 5,018 | 7,366 | -32% | 0.6 | 62% | 8.7 h |
| 21 | Sales and operations planning | P2P | 1,205 | 1,299 | -94 | 4,899 | 3,863 | +27% | 3.8 | 85% | 2.7 d |
| 22 | Metric governance | D&A | 1,149 | 1,431 | -282 | 4,897 | 4,248 | +15% | 3.4 | 64% | 4.4 d |
| 23 | Close management | R2R | 2,324 | 2,623 | -299 | 4,086 | 3,158 | +29% | 1.6 | 89% | 24.1 h |
| 24 | Quality control | M2D | 958 | 1,329 | -371 | 3,447 | 4,879 | -29% | 2.6 | 69% | 3.2 d |
| 25 | Service requests | ITS | 4,223 | 4,775 | -552 | 2,853 | 10,162 | -72% | 0.6 | 67% | 20.8 h |
| 26 | Report certification | D&A | 1,391 | 2,096 | -705 | 2,721 | 6,581 | -59% | 1.3 | 96% | 45.1 h |
| 27 | Replenishment | P2P | 1,335 | 1,794 | -459 | 1,916 | 4,604 | -58% | 1.1 | 82% | 26.7 h |
| 28 | Launch gates | C2L | 1,472 | 1,645 | -173 | 1,831 | 4,920 | -63% | 1.1 | 69% | 26.4 h |
| 29 | Employee lifecycle | H2R | 3,710 | 4,171 | -461 | 502 | 2,971 | -83% | 0.1 | 76% | 16.2 h |
| 30 | Matter management | LGL | 904 | 992 | -88 | 270 | 742 | -64% | 0.3 | 76% | 12.5 h |
| 31 | Data quality | D&A | 2,153 | 2,153 | 0 | 0 | 244 | -100% | 0.0 | 66% | 0 min |
| 32 | Supplier operations | S2P | 4,315 | 4,315 | 0 | 0 | 7,931 | -100% | 0.0 | 91% | 0 min |
| 33 | Forecast desk | P2P | 1,236 | 1,254 | -18 | 0 | 124 | -100% | 0.0 | 70% | 0 min |
| 34 | Contract desk | LGL | 3,654 | 3,654 | 0 | 0 | 1,456 | -100% | 0.0 | 66% | 0 min |
| 35 | Obligation management | LGL | 1,405 | 1,405 | 0 | 0 | 1,851 | -100% | 0.0 | 82% | 0 min |
| 36 | Campaign briefing | A2L | 3,775 | 3,775 | 0 | 0 | 216 | -100% | 0.0 | 81% | 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
10 queues are more than ten percent above their own 27 day mean
39,227 items cleared outside their commitment. They are spread across 36 queues, and the deepest single contributor is Order desk with 3,655. 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. The counts below rank by change rather than by size, which is why a small queue can appear here and a large stable one does not.
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. This is the work this page can set in motion, and the bound it runs into.
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. It cannot add a person, move a shift, re-route a queue or throttle an arrival. Those are decisions taken outside this platform, and the series behind this page is modeled telemetry, not a live feed.
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
81.7% of what was served on the day cleared inside commitment, with 342,817 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. Measured on the day on screen, 43,628 items were served across 36 queues and 35,629 of them cleared inside their commitment — 81.7%. 25 queues grew, 10 drained and 1 held level, leaving 342,817 items standing at close. 8 of them are running more than ten percent above their own 27 day normal, which is the figure a stock view hides entirely. The mechanism the position calls for is present here and it produces a named constraint every day. What it does not have is a connection: this series was generated, and nothing on this page is reading a live queue.
This page animates a modeled series. The 63 days between Mon, Jun 15 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. Every brand, site, customer, supplier, item and document behind this page was generated from a fixed random seed, and no figure is drawn from any real company accounts, filings or systems. What is real is the shape: a monolithic consumer goods group with one ledger and one shared services organization, and a document mix and volume that matches the estate this platform already publishes.
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.