The catalogue Supply ChainSales & Operations PlanningAnalytical

Service SC3B

Scenario Stress Test

Runs analytical. Starts when a leader asks the question. It runs 15 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

55 in flight right now.

Stations

1 person · 3 agent · 0 spine

Agent share of steps

75%

Autonomy on this service is set at 43% against a ceiling of 72%.

Decisions a person makes

Held by VP Integrated Business Planning.

Touchless

55%

Share of runs that complete without anybody opening them.

Timetable against actual

158.6h

Actual 174.7h, 16.1h over the timetable.

Operations

The lane diagram

Read it left to right. more

Person1 station and 46% of the dwellAgent3 stations and 54% 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

Enterprise Data Warehouse

Group ERP — Materials and Inventory

Supply and Demand Planning

Group ERP — Materials and Inventory

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	Define scenario	Agent	Scenario Modeling Agent	workflow	2h 31m	5h 43m	16	Enterprise Data Warehouse
2	Model impact	Agent	Gap Analysis Agent	workflow	10h 9m	15h 26m	2	Group ERP — Materials and Inventory
3	Draft findings	Agent	Financial Reconciliation Agent	workflow	11h 38m	20h 9m	37	Supply and Demand Planning
4	Leader review Held for a named human when the unit exceeds the planning cycle decision envelope, when confidence falls below the floor, or when a policy clause is engaged.	Human	VP Integrated Business Planning	policy	20h 34m	42h 28m	0	Group ERP — Materials and Inventory

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%

15 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 gates9 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

308.5h

15 items at 1,234 minutes of decision each.

Agent time a week

364.5h

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

Gate load

98%

Inside capacity, with 6.5h of headroom.

Stations without a person

75%

1 gate left on 4 stations.

Where an item spends its time

46% waiting on a person

54% in the agent lane

An item now takes 2,692 minutes of worked time end to end against 2,692 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 Scenario Stress Test

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 45 hrs

now Define scenario · Scenario Modeling Agent · 2.5 hrs

As the ledger has it

the same stations, plus 3 categories the estate already counts

0 min of 2.1 days

now Define scenario · Scenario Modeling Agent · 2.5 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 — Materials and Inventory

SAP S/4HANA MM · supply · bidirectional · high

modeled

2 of 4 stations attributed here · would write back

Enterprise Data Warehouse

Snowflake · analytics · inbound · critical

modeled

1 of 4 stations attributed here · read only

Supply and Demand Planning

Kinaxis RapidResponse · supply · bidirectional · high

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: Integrated Planning Orchestrator
That orchestrator’s remit: Owns planning cycle work end to end inside Supply Chain. Runs 3 lines across 17 stations, drains the repeatable share into the P2P tower, and holds 4 human gates.
Accountable person: VP Integrated Business Planning
Sub-function: Sales & Operations Planning
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

Monthly Planning CycleSC3A Planning Doctrine PositionSC3C

What this page is and is not

This is a catalogue of the modeled estate. more