LensReading which lens this session carries.
The catalogueSupply ChainSupply PlanningTransactional

Service SC2C

Allocation Decision

Runs transactional. Starts when a scheduled window opens. It runs 5,845 times a week across 5 stations. One of those stations stops for a person and 4 are done by an agent, 1 of them on the shared spine.

Runs a week

5,845

124 in flight right now.

Stations

5

1 person · 3 agent · 1 spine

Agent share of steps

80%

Autonomy on this service is set at 75% against a ceiling of 84%.

Decisions a person makes

1

Held by Director, Supply Planning.

Touchless

81%

Share of runs that complete without anybody opening them.

Timetable against actual

11.9h

Actual 12.4h, 0.5h over the timetable.

Operations

The lane diagram

Read it left to right.

Person1 station and 30% of the dwellAgent3 stations and 60% of the dwellShared spine1 station and 10% of the dwell2 crossings 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
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.

#StationLaneWhoLayerDwellTargetIn flightSystem
1

Detect scarcity

AgentCapacity Balancing Agentworkflow2h 43m4h 13m7Enterprise Data Warehouse
2

Model customer impact

Hands over at customer-service

AgentConstraint Detection Agentworkflow1h 28m2h 16m40Group ERP — Materials and Inventory
3

Draft allocation

AgentMaterial Requirements Agentworkflow3h 5m3h 52m46Supply and Demand Planning
4

Leader decide

Held for a named human when the unit exceeds the supply plan decision envelope, when confidence falls below the floor, or when a policy clause is engaged.

HumanDirector, Supply Planningpolicy3h 37m4h 36m8Group ERP — Materials and Inventory
5

Communicate

GBSCapacity Balancing Agentgbs1h 16m1h 51m23Group 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.

Move something
Demand100%
5,845 a week is what the estate records.
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 gates604 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.
Person time a week
21,139.4h
5,845 items at 217 minutes of decision each.
Agent time a week
49,877.3h
512 minutes an item, which does not compete for a person.
Gate load
100%
Inside capacity, with 0.6h of headroom.
Stations without a person
80%
1 gate left on 5 stations.
Where an item spends its time
30% waiting on a person
70% in the agent lane
An item now takes 729 minutes of worked time end to end against 729 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 Allocation Decision

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

How it runs

Run it again, going wrong

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

5 stations, walked twice

Once clean, once with the categories the estate counts

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

No break below was chosen.

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

now Detect scarcity · Capacity Balancing Agent · 2.7 hrs

As the ledger has it

the same stations, plus 3 categories the estate already counts

0 min of 17 hrs

now Detect scarcity · Capacity Balancing Agent · 2.7 hrs

personagentshared spinework the break addsnobody working it

What breaks, and where it is counted

No break below was chosen.

What the two runs say together

3 counted categories land on this procedure.

What this run cannot claim

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

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

Live observability

Systems this service would touch

Attributed by rule from the function's system list.

3 systems attributed

0 of 3 returning records

Group ERP — Materials and Inventory

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

modeled

3 of 5 stations attributed here · would write back

Enterprise Data Warehouse

Snowflake · analytics · inbound · critical

modeled

1 of 5 stations attributed here · read only

Supply and Demand Planning

Kinaxis RapidResponse · supply · bidirectional · high

modeled

1 of 5 stations attributed here · would write back

System attribution is a rule, not a reading.

Who runs it

Orchestration and accountability

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

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.