Service PR1B
Make-Buy-Partner Position
Runs judgment. Starts when a leadership team frames the question. It runs 4 times a week across 6 stations. One of those stations stops for a person and 5 are done by an agent, none of them on the shared spine.
Runs a week
4
86 in flight right now.
Stations
6
1 person · 5 agent · 0 spine
Agent share of steps
83%
Autonomy on this service is set at 42% against a ceiling of 68%.
Decisions a person makes
1
Held by VP Category Management.
Touchless
37%
Share of runs that complete without anybody opening them.
Timetable against actual
197.5h
Actual 178.3h, 19.2h under the timetable.
Operations
The lane diagram
Read it left to right. more
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 | Frame | Agent | Market Structure Agent | strategy | 39h 23m | 55h 45m | 1 | Group ERP — Financials |
| 2 | Gather evidence | Agent | Supply Base Mapping Agent | strategy | 34h 26m | 56h 59m | 9 | Group ERP — Financials |
| 3 | Model options | Agent | Demand Profile Agent | strategy | 40h 28m | 92h 21m | 42 | Group ERP — Financials |
| 4 | Draft position | Agent | Should-cost Modeling Agent | strategy | 69h 35m | 91h 30m | 16 | Group ERP — Financials |
| 5 | Challenge | Agent | Category Strategy Agent | strategy | 66h 24m | 95h 1m | 15 | Group ERP — Financials |
| 6 | Ratify 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 | 20h 47m | 38h 47m | 3 | 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
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
6 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
6 stations, nothing waiting, nothing sent back
0 min of 11.3 days
now Frame · Market Structure Agent · 39 hrs
As the ledger has it
the same stations, plus 3 categories the estate already counts
0 min of 11.5 days
now Frame · Market Structure Agent · 39 hrs
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
1 systems attributed
0 of 1 returning records
Group ERP — Financials
SAP S/4HANA · ledger · bidirectional · critical
6 of 6 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
What this page is and is not
This is a catalogue of the modeled estate. more