LensReading which lens this session carries.
The catalogueProcurement & Source-to-PaySourcing & RFxTransactional

Service PR3A

Sourcing Event

Runs transactional. Starts when a threshold is crossed. It runs 3,113 times a week across 10 stations. 2 of those stations stop for a person and 8 are done by an agent, 2 of them on the shared spine.

Runs a week

3,113

224 in flight right now.

Stations

10

2 person · 6 agent · 2 spine

Agent share of steps

80%

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

Decisions a person makes

2

Held by Director, Strategic Sourcing.

Touchless

84%

Share of runs that complete without anybody opening them.

Timetable against actual

8.4h

Actual 6.4h, 2.0h under the timetable.

Operations

The lane diagram

Read it left to right.

Person2 stations and 25% of the dwellAgent6 stations and 50% of the dwellShared spine2 stations and 25% of the dwell5 crossings between lanes
Human
decides
Agent
does the work
GBS
shared spine
System
attributed by rule
Group ERP — Financials
Group ERP — Financials
Source-to-Pay Suite
Treasury and Cash Management
Group ERP — Financials
Group ERP — Financials
Invoice Capture and AP Automation
Contract Lifecycle Management
Group ERP — Materials and Inventory
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

Capture requirement

AgentRequirement Capture Agentworkflow1h 34m1h 54m33Group ERP — Financials
2

Approve scope

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

HumanDirector, Strategic Sourcingpolicy11m22m4Group ERP — Financials
3

Build longlist

AgentRFx Authoring Agentworkflow2h 37m5h 34m39Source-to-Pay Suite
4

Author RFx

AgentBid Analysis Agentworkflow5m11m31Treasury and Cash Management
5

Issue

GBSRequirement Capture Agentgbs1h 39m3h 49m31Group ERP — Financials
6

Clarify

GBSRequirement Capture Agentgbs2h 46m5h 8m32Group ERP — Financials
7

Analyze bids

AgentSourcing Policy Agentworkflow1h 19m2h1Invoice Capture and AP Automation
8

Shortlist

AgentSourcing Orchestratorworkflow1h 2m1h 36m28Contract Lifecycle Management
9

Recommend

AgentRequirement Capture Agentworkflow2h 21m4h 29m16Group ERP — Materials and Inventory
10

Award decision

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

HumanDirector, Strategic Sourcingpolicy4h 14m8h 19m9Group 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%
3,113 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 gates393 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
13,749.1h
3,113 items at 265 minutes of decision each.
Agent time a week
41,662.3h
803 minutes an item, which does not compete for a person.
Gate load
100%
Inside capacity, with 5.9h of headroom.
Stations without a person
80%
2 gates left on 10 stations.
Where an item spends its time
25% waiting on a person
75% in the agent lane
An item now takes 1,068 minutes of worked time end to end against 1,068 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 Sourcing Event

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.

10 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

10 stations, nothing waiting, nothing sent back

0 min of 18 hrs

now Capture requirement · Requirement Capture Agent · 1.6 hrs

As the ledger has it

the same stations, plus 4 categories the estate already counts

0 min of 37 hrs

now Capture requirement · Requirement Capture Agent · 1.6 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.

6 systems attributed

0 of 6 returning records

Group ERP — Financials

SAP S/4HANA · ledger · bidirectional · critical

modeled

5 of 10 stations attributed here · would write back

Source-to-Pay Suite

SAP Ariba · procurement · bidirectional · critical

modeled

1 of 10 stations attributed here · would write back

Treasury and Cash Management

Kyriba · banking · bidirectional · critical

modeled

1 of 10 stations attributed here · would write back

Invoice Capture and AP Automation

Basware · procurement · bidirectional · high

modeled

1 of 10 stations attributed here · would write back

Contract Lifecycle Management

Icertis · legal · bidirectional · high

modeled

1 of 10 stations attributed here · would write back

Group ERP — Materials and Inventory

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

modeled

1 of 10 stations attributed here · would write back

System attribution is a rule, not a reading.

Who runs it

Orchestration and accountability

Orchestrated by
Sourcing Orchestrator
That orchestrator’s remit
Owns sourcing event work end to end inside Procurement & Source-to-Pay. Runs 3 lines across 21 stations, drains the repeatable share into the S2P tower, and holds 4 human gates.
Accountable person
Director, Strategic Sourcing
Sub-function
Sourcing & RFx
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.