The catalogue Procurement & Source-to-PayCategory StrategyAnalytical

Service PR1C

Category Performance Read

Runs analytical. Starts when the cycle calendar fires. It runs 47 times a week across 4 stations. One of those stations stops for a person and 3 are done by an agent, none of them on the shared spine.

Runs a week

49 in flight right now.

Stations

1 person · 3 agent · 0 spine

Agent share of steps

75%

Autonomy on this service is set at 42% against a ceiling of 68%.

Decisions a person makes

Held by VP Category Management.

Touchless

50%

Share of runs that complete without anybody opening them.

Timetable against actual

214.7h

Actual 248.2h, 33.5h over the timetable.

Operations

The lane diagram

Read it left to right. more

Person1 station and 58% of the dwellAgent3 stations and 42% of the dwellShared spine0 stations and 0% of the dwell1 crossing between lanes

Human

decides

Agent

does the work

GBS

shared spine

System

attributed by rule

Group ERP — Financials

Source-to-Pay Suite

Treasury and Cash Management

Group ERP — Financials

Click any station to see who does it, what it costs in time, the rule that gates it and the system attributed to it.

Operations

Every station in order

The same stations as a list, with the dwell the estate records against each one and the system a station of that shape would touch.

#	Station	Lane	Who	Layer	Dwell	Target	In flight	System
1	Aggregate spend	Agent	Market Structure Agent	workflow	13h 31m	24h 25m	21	Group ERP — Financials
2	Score suppliers	Agent	Supply Base Mapping Agent	workflow	14h 20m	26h 10m	1	Source-to-Pay Suite
3	Draft readout	Agent	Demand Profile Agent	workflow	4h 42m	5h 48m	25	Treasury and Cash Management
4	Leader review Held for a named human when the unit exceeds the category plan decision envelope, when confidence falls below the floor, or when a policy clause is engaged.	Human	VP Category Management	policy	44h 43m	105h 53m	2	Group ERP — Financials

Operations

Run it

Change the volume, move the autonomy line, release a gate, and watch what happens to the hours in each lane and to the time it takes one run to get through. more

Move something

Demand100%

47 a week is what the estate records. more

Decisions handed to agents0 of 0

This service has at most one gate, so there is nothing to hand over without removing the last human decision.

People on the gates61 people

Each one is assumed to have 2,100 productive minutes a week, which is 35 hours.

Agent speed100%

100% is the dwell the estate records today. more

Person time a week

2,101.7h

47 items at 2,683 minutes of decision each.

Agent time a week

1,529.9h

1,953 minutes an item, which does not compete for a person.

Gate load

98%

Inside capacity, with 33.3h of headroom.

Stations without a person

75%

1 gate left on 4 stations.

Where an item spends its time

58% waiting on a person

42% in the agent lane

An item now takes 4,636 minutes of worked time end to end against 4,636 in the recorded estate, a change of +0%. This is worked time, not calendar time: nothing here models a queue or a weekend.

What this model is, on Category Performance Read

The simulation is arithmetic on the estate, not a queueing model. more

How it runs

Run it again, going wrong

The same unit and the same stations, broken the way the estate already records breaking. more

4 stations, walked twice

Once clean, once with the categories the estate counts

This is the same unit on the same stations, breaking. more

No break below was chosen. more

One play head, two tracks, the same scale. The clean run stops when it runs out of stations; the other one keeps going.

As written

4 stations, nothing waiting, nothing sent back

0 min of 3.2 days

now Aggregate spend · Market Structure Agent · 14 hrs

As the ledger has it

the same stations, plus 3 categories the estate already counts

0 min of 3.4 days

now Aggregate spend · Market Structure Agent · 14 hrs

personagentshared spinework the break addsnobody working it

What breaks, and where it is counted

No break below was chosen. more

What the two runs say together

3 counted categories land on this procedure. more

What this run cannot claim

These breaks are shown together on one unit so the shape of a bad day fits on one screen. more

Two clocks run. Worked time is the sum of the time the work is actually being done … more

Live observability

Systems this service would touch

Attributed by rule from the function's system list. more

3 systems attributed

0 of 3 returning records

The system register

Group ERP — Financials

SAP S/4HANA · ledger · bidirectional · critical

modeled

2 of 4 stations attributed here · would write back

Source-to-Pay Suite

SAP Ariba · procurement · bidirectional · critical

modeled

1 of 4 stations attributed here · would write back

Treasury and Cash Management

Kyriba · banking · bidirectional · critical

modeled

1 of 4 stations attributed here · would write back

System attribution is a rule, not a reading. more

Who runs it

Orchestration and accountability

Orchestrated by: Category Strategy Orchestrator
That orchestrator’s remit: Owns category plan work end to end inside Procurement & Source-to-Pay. Runs 3 lines across 18 stations, drains the repeatable share into no shared tower, and holds 3 human gates.
Accountable person: VP Category Management
Sub-function: Category Strategy
Shared spine tower: Not on the shared spine
Hand-over points: None — this service stays inside its function

Other services in this sub-function

2 alongside this one

Category Strategy RefreshPR1A Make-Buy-Partner PositionPR1B

What this page is and is not

This is a catalogue of the modeled estate. more