LensReading which lens this session carries.
The catalogueProcurement & Source-to-PaySupplier OnboardingTransactional

Service PR6B

Supplier Data Change

Runs transactional. Starts when an upstream system posts an event. It runs 2,180 times a week across 6 stations. 2 of those stations stop for a person and 4 are done by an agent, 3 of them on the shared spine.

Runs a week

2,180

112 in flight right now.

Stations

6

2 person · 1 agent · 3 spine

Agent share of steps

67%

Autonomy on this service is set at 78% against a ceiling of 79%.

Decisions a person makes

2

Held by Director, Supplier Management.

Touchless

83%

Share of runs that complete without anybody opening them.

Timetable against actual

10.2h

Actual 11.1h, 0.9h over the timetable.

Operations

The lane diagram

Read it left to right.

Person2 stations and 46% of the dwellAgent1 station and 15% of the dwellShared spine3 stations and 39% of the dwell4 crossings between lanes
Human
decides
Agent
does the work
GBS
shared spine
System
attributed by rule
Group ERP — Financials
Group ERP — Financials
Group ERP — Financials
Group ERP — Financials
Group ERP — Financials
Group ERP — Financials
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

Request

AgentRegistration Agentworkflow2h 12m4h 15m34Group ERP — Financials
2

Verify change

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

HumanDirector, Supplier Managementpolicy1h 29m2h 43m7Group ERP — Financials
3

Fraud check

GBSRegistration Agentgbs2h 57m6h 3m35Group ERP — Financials
4

Approve

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

HumanDirector, Supplier Managementpolicy5h 22m7h 49m6Group ERP — Financials
5

Apply

GBSRegistration Agentgbs2h 24m4h 52m1Group ERP — Financials
6

Notify

GBSRegistration Agentgbs25m54m29Group ERP — Financials

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%
2,180 a week is what the estate records.
Decisions handed to agents0 of 2
Cheapest decision first. The last gate never moves: something on this service always ends with a person.
People on the gates427 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
14,933h
2,180 items at 411 minutes of decision each.
Agent time a week
17,367.3h
478 minutes an item, which does not compete for a person.
Gate load
100%
Inside capacity, with 12h of headroom.
Stations without a person
67%
2 gates left on 6 stations.
Where an item spends its time
46% waiting on a person
54% in the agent lane
An item now takes 889 minutes of worked time end to end against 889 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 Supplier Data Change

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.

6 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

6 stations, nothing waiting, nothing sent back

0 min of 15 hrs

now Request · Registration Agent · 2.2 hrs

As the ledger has it

the same stations, plus 4 categories the estate already counts

0 min of 34 hrs

now Request · Registration Agent · 2.2 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.

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.

1 systems attributed

0 of 1 returning records

Group ERP — Financials

SAP S/4HANA · ledger · bidirectional · critical

modeled

6 of 6 stations attributed here · would write back

System attribution is a rule, not a reading.

Who runs it

Orchestration and accountability

Orchestrated by
Supplier Onboarding Orchestrator
That orchestrator’s remit
Owns supplier record work end to end inside Procurement & Source-to-Pay. Runs 3 lines across 18 stations, drains the repeatable share into the S2P tower, and holds 4 human gates.
Accountable person
Director, Supplier Management
Sub-function
Supplier Onboarding
Shared spine tower
s2p
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.