The catalogue Supply ChainOrder PromisingTransactional

Service SC9B

Promise Breach Response

Runs transactional. Starts when a request lands in the queue. It runs 2,954 times a week across 5 stations. One of those stations stops for a person and 4 are done by an agent, 2 of them on the shared spine.

Runs a week

2,954

72 in flight right now.

Stations

1 person · 2 agent · 2 spine

Agent share of steps

80%

Autonomy on this service is set at 87% against a ceiling of 90%.

Decisions a person makes

Held by Director, Order Promising.

Touchless

90%

Share of runs that complete without anybody opening them.

Timetable against actual

18.9h

Actual 22.0h, 3.1h over the timetable.

Operations

The lane diagram

Read it left to right. more

Person1 station and 27% of the dwellAgent2 stations and 42% of the dwellShared spine2 stations and 30% of the dwell3 crossings between lanes

Human

decides

Agent

does the work

GBS

shared spine

System

attributed by rule

Group ERP — Materials and Inventory

Enterprise Data Warehouse

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	Detect slip	GBS	Available-to-Promise Agent	gbs	30m	1h 9m	0	Group ERP — Materials and Inventory
2	Assess customer impact	Agent	Capable-to-Promise Agent	workflow	1h 55m	2h 46m	35	Enterprise Data Warehouse
3	Draft communication	Agent	Substitution Agent	workflow	43m	1h 10m	0	Group ERP — Materials and Inventory
4	Owner approve Held for a named human when the unit exceeds the promise decision envelope, when confidence falls below the floor, or when a policy clause is engaged.	Human	Director, Order Promising	policy	1h 41m	3h 46m	3	Group ERP — Materials and Inventory
5	Notify Hands over at customer-service	GBS	Available-to-Promise Agent	gbs	1h 23m	2h 15m	34	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%

2,954 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 gates143 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

4,972.6h

2,954 items at 101 minutes of decision each.

Agent time a week

13,342.2h

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

Gate load

99%

Inside capacity, with 32.4h of headroom.

Stations without a person

80%

1 gate left on 5 stations.

Where an item spends its time

27% waiting on a person

73% in the agent lane

An item now takes 372 minutes of worked time end to end against 372 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 Promise Breach Response

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

5 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

5 stations, nothing waiting, nothing sent back

0 min of 6.2 hrs

now Detect slip · Available-to-Promise Agent · 30 min

As the ledger has it

the same stations, plus 4 categories the estate already counts

0 min of 20 hrs

now Detect slip · Available-to-Promise Agent · 30 min

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

4 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

The separation register records a duty conflict against a sub-function and a named post, not against one procedure. 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

2 systems attributed

0 of 2 returning records

The system register

Group ERP — Materials and Inventory

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

modeled

4 of 5 stations attributed here · would write back

Enterprise Data Warehouse

Snowflake · analytics · inbound · critical

modeled

1 of 5 stations attributed here · read only

System attribution is a rule, not a reading. more

Who runs it

Orchestration and accountability

Orchestrated by: Order Promising Orchestrator
That orchestrator’s remit: Owns promise work end to end inside Supply Chain. Runs 3 lines across 15 stations, drains the repeatable share into the M2D tower, and holds 2 human gates.
Accountable person: Director, Order Promising
Sub-function: Order Promising
Shared spine tower: m2d
Hand-over points: customer-service

Other services in this sub-function

2 alongside this one

Order PromiseSC9A Promise Accuracy ReadSC9C

What this page is and is not

This is a catalogue of the modeled estate. more