LensReading which lens this session carries.
The catalogueProcurement & Source-to-PayPayment InterlockAnalytical

Service PR10C

Term Optimization

Runs analytical. Starts when the cycle calendar fires. It runs 56 times a week across 3 stations. One of those stations stops for a person and 2 are done by an agent, none of them on the shared spine.

Runs a week

56

67 in flight right now.

Stations

3

1 person · 2 agent · 0 spine

Agent share of steps

67%

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

Decisions a person makes

1

Held by Director, Payment Operations.

Touchless

55%

Share of runs that complete without anybody opening them.

Timetable against actual

61.2h

Actual 50.5h, 10.7h under the timetable.

Operations

The lane diagram

Read it left to right.

Person1 station and 70% of the dwellAgent2 stations and 30% of the dwellShared spine0 stations and 0% of the dwell1 crossing between lanes
Human
decides
Agent
does the work
GBS
shared spine
System
attributed by rule
Group ERP — Financials
Source-to-Pay Suite
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

Model working capital

AgentPayment Proposal Agentworkflow6h 30m9h 55m16Group ERP — Financials
2

Draft recommendation

AgentDiscount Capture Agentworkflow11h 40m27h 47m45Source-to-Pay Suite
3

Treasury review

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

Hands over at finance

HumanDirector, Payment Operationspolicy42h 44m58h 36m6Group 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%
56 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 gates69 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
2,393.1h
56 items at 2,564 minutes of decision each.
Agent time a week
1,017.3h
1,090 minutes an item, which does not compete for a person.
Gate load
99%
Inside capacity, with 21.9h of headroom.
Stations without a person
67%
1 gate left on 3 stations.
Where an item spends its time
70% waiting on a person
30% in the agent lane
An item now takes 3,654 minutes of worked time end to end against 3,654 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 Term Optimization

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.

3 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

3 stations, nothing waiting, nothing sent back

0 min of 2.5 days

now Model working capital · Payment Proposal Agent · 6.5 hrs

As the ledger has it

the same stations, plus 3 categories the estate already counts

0 min of 2.7 days

now Model working capital · Payment Proposal Agent · 6.5 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

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.

2 systems attributed

0 of 2 returning records

Group ERP — Financials

SAP S/4HANA · ledger · bidirectional · critical

modeled

2 of 3 stations attributed here · would write back

Source-to-Pay Suite

SAP Ariba · procurement · bidirectional · critical

modeled

1 of 3 stations attributed here · would write back

System attribution is a rule, not a reading.

Who runs it

Orchestration and accountability

Orchestrated by
Payment Interlock Orchestrator
That orchestrator’s remit
Owns payment run work end to end inside Procurement & Source-to-Pay. Runs 3 lines across 16 stations, drains the repeatable share into the S2P tower, and holds 4 human gates.
Accountable person
Director, Payment Operations
Sub-function
Payment Interlock
Shared spine tower
Not on the shared spine
Hand-over points
finance

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.