LensReading which lens this session carries.
The catalogueSupply ChainResilience & RiskTransactional

Service SC11B

Multi-tier Risk Sweep

Runs transactional. Starts when a request lands in the queue. It runs 5,355 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,355

44 in flight right now.

Stations

5

1 person · 3 agent · 1 spine

Agent share of steps

80%

Autonomy on this service is set at 69% against a ceiling of 74%.

Decisions a person makes

1

Held by Director, Supply Resilience.

Touchless

69%

Share of runs that complete without anybody opening them.

Timetable against actual

12.4h

Actual 15.6h, 3.2h over the timetable.

Operations

The lane diagram

Read it left to right.

Person1 station and 43% of the dwellAgent3 stations and 47% of the dwellShared spine1 station and 10% 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
Group ERP — Materials and Inventory
Supply and Demand Planning
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

Map tier 2 and 3

GBSSupply Resilience Orchestratorgbs1h 21m2h 19m5Group ERP — Materials and Inventory
2

Score concentration

AgentMulti-tier Mapping Agentworkflow3h 8m4h 25m25Enterprise Data Warehouse
3

Flag single source

AgentSingle-source Risk Agentworkflow2h 15m5h 19m7Group ERP — Materials and Inventory
4

Owner review

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

HumanDirector, Supply Resiliencepolicy5h 51m13h 17m1Group ERP — Materials and Inventory
5

Mitigate

AgentRecovery Coordination Agentworkflow58m2h 12m6Supply and Demand Planning

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,355 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 gates896 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
31,326.8h
5,355 items at 351 minutes of decision each.
Agent time a week
41,233.5h
462 minutes an item, which does not compete for a person.
Gate load
100%
Inside capacity, with 33.3h of headroom.
Stations without a person
80%
1 gate left on 5 stations.
Where an item spends its time
43% waiting on a person
57% in the agent lane
An item now takes 813 minutes of worked time end to end against 813 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 Multi-tier Risk Sweep

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

now Map tier 2 and 3 · Supply Resilience Orchestrator · 1.4 hrs

As the ledger has it

the same stations, plus 4 categories the estate already counts

0 min of 31 hrs

now Map tier 2 and 3 · Supply Resilience Orchestrator · 1.4 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

4 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.

The separation register records a duty conflict against a sub-function and a named post, not against one procedure.

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

The system register

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 Resilience Orchestrator
That orchestrator’s remit
Owns risk event work end to end inside Supply Chain. Runs 3 lines across 18 stations, drains the repeatable share into no shared tower, and holds 4 human gates.
Accountable person
Director, Supply Resilience
Sub-function
Resilience & Risk
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

Disruption ResponseSC11AResilience Posture PositionSC11C

What this page is and is not

This is a catalogue of the modeled estate.