LensReading which lens this session carries.
The catalogueSupply ChainLogistics & TransportationTransactional

Service SC5A

Ship-to-Deliver

Runs transactional. Starts when a request lands in the queue. It runs 3,328 times a week across 8 stations. No station stops for a person and 8 are done by an agent, 7 of them on the shared spine.

Runs a week

3,328

164 in flight right now.

Stations

8

0 person · 1 agent · 7 spine

Agent share of steps

100%

Autonomy on this service is set at 82% against a ceiling of 91%.

Decisions a person makes

0

Nothing on this service waits for a person.

Touchless

85%

Share of runs that complete without anybody opening them.

Timetable against actual

25.5h

Actual 28.2h, 2.7h over the timetable.

Operations

The lane diagram

Read it left to right.

Person0 stations and 0% of the dwellAgent1 station and 16% of the dwellShared spine7 stations and 84% of the dwell2 crossings between lanes
Human
decides
Agent
does the work
GBS
shared spine
System
attributed by rule
Group ERP — Materials and Inventory
Group ERP — Materials and Inventory
Group ERP — Materials and Inventory
Group ERP — Materials and Inventory
Enterprise Data Warehouse
Group ERP — Materials and Inventory
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

Plan shipment

GBSCarrier Selection Agentgbs1h 49m4h 21m34Group ERP — Materials and Inventory
2

Select carrier

GBSCarrier Selection Agentgbs2h 37m3h 47m17Group ERP — Materials and Inventory
3

Book

GBSCarrier Selection Agentgbs2h 36m3h 40m0Group ERP — Materials and Inventory
4

Track

GBSCarrier Selection Agentgbs4m8m46Group ERP — Materials and Inventory
5

Detect exception

AgentException Recovery Agentworkflow2h 10m3h 57m40Enterprise Data Warehouse
6

Recover

GBSCarrier Selection Agentgbs2h 22m3h 48m4Group ERP — Materials and Inventory
7

Confirm delivery

GBSCarrier Selection Agentgbs57m2h 11m7Group ERP — Materials and Inventory
8

Audit freight

GBSCarrier Selection Agentgbs1h 21m2h 36m16Group 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%
3,328 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 gates1 person
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
0h
3,328 items at 0 minutes of decision each.
Agent time a week
46,370.1h
836 minutes an item, which does not compete for a person.
Gate load
0%
Inside capacity, with 35h of headroom.
Stations without a person
100%
0 gates left on 8 stations.
Where an item spends its time
100% in the agent lane
An item now takes 836 minutes of worked time end to end against 836 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 Ship-to-Deliver

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.

8 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

8 stations, nothing waiting, nothing sent back

0 min of 14 hrs

now Plan shipment · Carrier Selection Agent · 1.8 hrs

As the ledger has it

the same stations, plus 3 categories the estate already counts

0 min of 19 hrs

now Plan shipment · Carrier Selection Agent · 1.8 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.

2 systems attributed

0 of 2 returning records

Group ERP — Materials and Inventory

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

modeled

7 of 8 stations attributed here · would write back

Enterprise Data Warehouse

Snowflake · analytics · inbound · critical

modeled

1 of 8 stations attributed here · read only

System attribution is a rule, not a reading.

Who runs it

Orchestration and accountability

Orchestrated by
Logistics Orchestrator
That orchestrator’s remit
Owns shipment work end to end inside Supply Chain. Runs 3 lines across 17 stations, drains the repeatable share into the M2D tower, and holds 2 human gates.
Accountable person
Director, Logistics
Sub-function
Logistics & Transportation
Shared spine tower
m2d
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.