LensReading which lens this session carries.

Service GB2A

Requisition to PO

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

Runs a week

2,712

108 in flight right now.

Stations

6

1 person · 0 agent · 5 spine

Agent share of steps

83%

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

Decisions a person makes

1

Held by Tower Lead, Source-to-Pay.

Touchless

90%

Share of runs that complete without anybody opening them.

Timetable against actual

21.9h

Actual 26.4h, 4.5h over the timetable.

Operations

The lane diagram

Read it left to right.

Person1 station and 44% of the dwellAgent0 stations and 0% of the dwellShared spine5 stations and 56% of the dwell2 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

Requisition

GBSRequisition Validation Agentgbs17m31m16Group ERP — Financials
2

Policy check

GBSRequisition Validation Agentgbs3h 5m7h 14m24Group ERP — Financials
3

Budget check

Hands over at finance

GBSRequisition Validation Agentgbs3h 7m3h 48m25Group ERP — Financials
4

Approve

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

HumanTower Lead, Source-to-Paypolicy6h 40m14h 1m2Group ERP — Financials
5

Issue PO

GBSRequisition Validation Agentgbs1h 44m2h 26m33Group ERP — Financials
6

Acknowledge

GBSRequisition Validation Agentgbs9m14m8Group 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,712 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 gates517 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
18,080h
2,712 items at 400 minutes of decision each.
Agent time a week
22,690.4h
502 minutes an item, which does not compete for a person.
Gate load
100%
Inside capacity, with 15h of headroom.
Stations without a person
83%
1 gate left on 6 stations.
Where an item spends its time
44% waiting on a person
56% in the agent lane
An item now takes 902 minutes of worked time end to end against 902 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 Requisition to PO

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 Requisition · Requisition Validation Agent · 17 min

As the ledger has it

the same stations, plus 3 categories the estate already counts

0 min of 20 hrs

now Requisition · Requisition Validation Agent · 17 min

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.

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
Source-to-Pay Tower Orchestrator
That orchestrator’s remit
Owns invoice work end to end inside AI GBS & Global Business Services. Runs 4 lines across 24 stations, drains the repeatable share into the S2P tower, and holds 4 human gates.
Accountable person
Tower Lead, Source-to-Pay
Sub-function
S2P Control Tower
Shared spine tower
s2p
Hand-over points
finance

Other services in this sub-function

3 alongside this one

What this page is and is not

This is a catalogue of the modeled estate.