LensReading which lens this session carries.
The catalogueProcurement & Source-to-PaySpend AnalyticsTransactional

Service PR2B

Maverick Spend Sweep

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

Runs a week

7,021

52 in flight right now.

Stations

4

1 person · 0 agent · 3 spine

Agent share of steps

75%

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

Decisions a person makes

1

Held by Director, Procurement Analytics.

Touchless

97%

Share of runs that complete without anybody opening them.

Timetable against actual

14.1h

Actual 13.8h, 0.3h under the timetable.

Operations

The lane diagram

Read it left to right.

Person1 station and 41% of the dwellAgent0 stations and 0% of the dwellShared spine3 stations and 59% of the dwell1 crossing 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
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 off-contract

GBSSpend Classification Agentgbs2h 8m3h 7m20Group ERP — Financials
2

Notify requester

GBSSpend Classification Agentgbs2h 6m3h 22m24Group ERP — Financials
3

Redirect to contract

GBSSpend Classification Agentgbs1h 51m2h 29m1Group ERP — Financials
4

Escalate repeat

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

HumanDirector, Procurement Analyticspolicy4h 9m6h 22m7Group 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%
7,021 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 gates833 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
29,137.2h
7,021 items at 249 minutes of decision each.
Agent time a week
42,711.1h
365 minutes an item, which does not compete for a person.
Gate load
100%
Inside capacity, with 17.9h of headroom.
Stations without a person
75%
1 gate left on 4 stations.
Where an item spends its time
41% waiting on a person
59% in the agent lane
An item now takes 614 minutes of worked time end to end against 614 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 Maverick Spend 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.

4 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

4 stations, nothing waiting, nothing sent back

0 min of 10 hrs

now Detect off-contract · Spend Classification Agent · 2.1 hrs

As the ledger has it

the same stations, plus 2 categories the estate already counts

0 min of 12 hrs

now Detect off-contract · Spend Classification Agent · 2.1 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

2 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

4 of 4 stations attributed here · would write back

System attribution is a rule, not a reading.

Who runs it

Orchestration and accountability

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