LensReading which lens this session carries.
The catalogueProcurement & Source-to-PaySavings AssuranceTransactional

Service PR11A

Savings Validation

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

Runs a week

3,868

109 in flight right now.

Stations

6

2 person · 2 agent · 2 spine

Agent share of steps

67%

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

Decisions a person makes

2

Held by Director, Value Assurance.

Touchless

84%

Share of runs that complete without anybody opening them.

Timetable against actual

6.7h

Actual 5.2h, 1.5h under the timetable.

Operations

The lane diagram

Read it left to right.

Person2 stations and 61% of the dwellAgent2 stations and 18% of the dwellShared spine2 stations and 21% 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
Source-to-Pay Suite
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

Claim

AgentSavings Claim Agentworkflow2h 30m3h 55m10Group ERP — Financials
2

Verify baseline

GBSSavings Claim Agentgbs1h 21m2h 7m27Group ERP — Financials
3

Model realization

AgentRealization Tracking Agentworkflow26m34m21Source-to-Pay Suite
4

Finance validate

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

Hands over at finance

HumanDirector, Value Assurancepolicy2h 14m4h 17m9Group ERP — Financials
5

Approve

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

HumanDirector, Value Assurancepolicy7h 37m13h 41m0Group ERP — Financials
6

Publish

GBSSavings Claim Agentgbs2h 8m3h 52m42Group 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,868 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 gates1089 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
38,099.8h
3,868 items at 591 minutes of decision each.
Agent time a week
24,819.7h
385 minutes an item, which does not compete for a person.
Gate load
100%
Inside capacity, with 15.2h of headroom.
Stations without a person
67%
2 gates left on 6 stations.
Where an item spends its time
61% waiting on a person
39% in the agent lane
An item now takes 976 minutes of worked time end to end against 976 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 Savings Validation

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 16 hrs

now Claim · Savings Claim Agent · 2.5 hrs

As the ledger has it

the same stations, plus 5 categories the estate already counts

0 min of 43 hrs

now Claim · Savings Claim Agent · 2.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

5 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.

The separation register records a duty conflict against a sub-function and a named post, not against one procedure.

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

5 of 6 stations attributed here · would write back

Source-to-Pay Suite

SAP Ariba · procurement · bidirectional · critical

modeled

1 of 6 stations attributed here · would write back

System attribution is a rule, not a reading.

Who runs it

Orchestration and accountability

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