Operate · the run state

Every queue, one day, one canvas

This is the operation as it stood at the close of Mon, Jun 15. 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.

The documents behind it

Day on screen

Mon, Jun 15

Mon, Jun 1563 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. Depth on its own does not.

Items standing

76,492

Across 36 queues at the close of the day

Arrived

164,135

New work that reached a queue on the day

Served

164,206

131,627 of them cleared inside commitment

Net change

-71

The operation ended the day shallower than it started

Queues growing

16 of 36

20 draining · 0 level

Oldest item waiting

32.3 h

The single longest wait anywhere in the operation

The binding constraint on this day

Invoice processing in Source-to-Pay — 6,998 items standing and growing by 1,044 a day.

Of the 36 queues on this canvas, this one is ranked first because releasing it frees the most work: it holds 9.1% of everything standing, and it is taking on 1,044 more items a day than it clears, so the share is rising. At the day service rate of 11,750 items, and only if nothing else arrived, what is already standing in it is 0.6 days of work. Its oldest item has been waiting 15.9 h, and 1,173 of the 11,750 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.

6,998

Standing

9.1%

Share of all standing work

12,794

Arrived on the day

11,750

Served on the day

No prior days

Against its own normal

15.9 h

Oldest item

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 · 76,492 items standing · deepest is 6,998

■ 90%+ inside commitment■ 75 to 90%■ under 75%

S2PSource-to-Pay16,612 standing · 21.7% of the operation

Invoice processing

6,998+1,04415.9 h

Buying desk

6,212-18119.5 h

Supplier operations

3,402+1,09924.2 h

O2COrder-to-Cash9,882 standing · 12.9% of the operation

Order desk

4,716+1,42716.0 h

Billing and credit

3,631-1,61316.1 h

Cash and collections

1,535-29320.9 h

H2RHire-to-Retire8,693 standing · 11.4% of the operation

Payroll operations

4,254+1,25426.1 h

Time and claims

2,339-1,18721.2 h

Employee lifecycle

2,100-2958.6 h

AIOAI Operations7,249 standing · 9.5% of the operation

Agent run desk

3,560+8232.3 h

Model routing

2,043-23122.2 h

Prompt and policy

1,646+57121.8 h

ITSIT Service6,864 standing · 9.0% of the operation

Change and access

3,177+55321.0 h

Service requests

2,300+49516.1 h

Incident desk

1,387-77314.8 h

M2DMake-to-Deliver5,753 standing · 7.5% of the operation

Move and deliver

3,350-26018.4 h

Make and release

1,674-57614.2 h

Quality control

729+1810.7 h

C2LConcept-to-Launch5,630 standing · 7.4% of the operation

Formulation

2,161-3212.9 h

Artwork studio

2,099+58610.6 h

Launch gates

1,370+1628.8 h

R2RRecord-to-Report5,497 standing · 7.2% of the operation

Postings desk

2,144+1247.2 h

Reconciliation

1,870-16916.3 h

Close management

1,483-2822.7 h

A2LAwareness-to-Lead3,243 standing · 4.2% of the operation

Trade promotion

1,628+11025.1 h

Campaign briefing

839-1,01914.9 h

Media operations

776+1296.7 h

P2PPlan-to-Perform2,548 standing · 3.3% of the operation

Forecast desk

897-1915.4 h

Replenishment

877-7415.8 h

Sales and operations planning

774-1918.2 h

D&AData and Analytics2,340 standing · 3.1% of the operation

Data quality

849-23821.1 h

Report certification

781+23011.8 h

Metric governance

710+3512.2 h

LGLLegal Operations2,181 standing · 2.9% of the operation

Obligation management

959-34513.8 h

Contract desk

819-4586.1 h

Matter management

403-345.8 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 76,492 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

16 queues are taking on more than they clear

#	Queue	Tower	Arrived	Served	Net	Standing	vs normal	Days of work	Inside	Oldest
1	Invoice processing	S2P	12,794	11,750	+1,044	6,998	—	0.6	90%	15.9 h
2	Order desk	O2C	8,491	7,064	+1,427	4,716	—	0.7	71%	16.0 h
3	Payroll operations	H2R	8,466	7,212	+1,254	4,254	—	0.6	83%	26.1 h
4	Supplier operations	S2P	5,366	4,267	+1,099	3,402	—	0.8	76%	24.2 h
5	Buying desk	S2P	9,248	9,429	-181	6,212	—	0.7	66%	19.5 h
6	Change and access	ITS	4,991	4,438	+553	3,177	—	0.7	75%	21.0 h
7	Artwork studio	C2L	3,724	3,138	+586	2,099	—	0.7	62%	10.6 h
8	Service requests	ITS	4,906	4,411	+495	2,300	—	0.5	95%	16.1 h
9	Prompt and policy	AIO	3,747	3,176	+571	1,646	—	0.5	75%	21.8 h
10	Agent run desk	AIO	4,950	4,868	+82	3,560	—	0.7	63%	32.3 h
11	Billing and credit	O2C	7,149	8,762	-1,613	3,631	—	0.4	87%	16.1 h
12	Move and deliver	M2D	8,492	8,752	-260	3,350	—	0.4	77%	18.4 h
13	Postings desk	R2R	7,973	7,849	+124	2,144	—	0.3	86%	7.2 h
14	Time and claims	H2R	9,848	11,035	-1,187	2,339	—	0.2	85%	21.2 h
15	Trade promotion	A2L	2,640	2,530	+110	1,628	—	0.6	85%	25.1 h
16	Formulation	C2L	3,626	3,658	-32	2,161	—	0.6	65%	12.9 h
17	Employee lifecycle	H2R	4,444	4,739	-295	2,100	—	0.4	67%	8.6 h
18	Model routing	AIO	3,940	4,171	-231	2,043	—	0.5	76%	22.2 h
19	Report certification	D&A	1,942	1,712	+230	781	—	0.5	85%	11.8 h
20	Reconciliation	R2R	5,953	6,122	-169	1,870	—	0.3	88%	16.3 h
21	Make and release	M2D	6,194	6,770	-576	1,674	—	0.2	79%	14.2 h
22	Cash and collections	O2C	2,888	3,181	-293	1,535	—	0.5	93%	20.9 h
23	Close management	R2R	3,160	3,188	-28	1,483	—	0.5	82%	22.7 h
24	Launch gates	C2L	1,869	1,853	+16	1,370	—	0.7	87%	28.8 h
25	Media operations	A2L	2,105	1,976	+129	776	—	0.4	94%	6.7 h
26	Incident desk	ITS	4,884	5,657	-773	1,387	—	0.2	77%	14.8 h
27	Obligation management	LGL	1,682	2,027	-345	959	—	0.5	94%	13.8 h
28	Forecast desk	P2P	1,399	1,418	-19	897	—	0.6	96%	15.4 h
29	Metric governance	D&A	1,590	1,555	+35	710	—	0.5	72%	12.2 h
30	Replenishment	P2P	1,387	1,461	-74	877	—	0.6	89%	15.8 h
31	Data quality	D&A	2,352	2,590	-238	849	—	0.3	92%	21.1 h
32	Campaign briefing	A2L	4,456	5,475	-1,019	839	—	0.2	91%	14.9 h
33	Contract desk	LGL	4,036	4,494	-458	819	—	0.2	63%	6.1 h
34	Quality control	M2D	1,115	1,097	+18	729	—	0.7	92%	10.7 h
35	Sales and operations planning	P2P	1,362	1,381	-19	774	—	0.6	63%	18.2 h
36	Matter management	LGL	966	1,000	-34	403	—	0.4	88%	5.8 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: 76,492 items are still standing and 19.8% of what was served cleared outside commitment.

The commitment on the day

131,627 of 164,206 items served cleared inside commitment — 80.2%.

32,579 items cleared outside their commitment. They are spread across 36 queues, and the deepest single contributor is Buying desk with 3,169. 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

Queues on the canvas

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. 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

Growing2569%

Draining1028%

Level13%

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.

What this page is, and what it is not

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.