The catalogue Procurement & Source-to-PayContract ExecutionTransactional

Service PR5C

Expiry & Renewal Sweep

Runs transactional. Starts when a request lands in the queue. It runs 2,080 times a week across 5 stations. One of those stations stops for a person and 4 are done by an agent, 1 of them on the shared spine.

Runs a week

2,080

69 in flight right now.

Stations

1 person · 3 agent · 1 spine

Agent share of steps

80%

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

Decisions a person makes

Held by Director, Contract Management.

Touchless

80%

Share of runs that complete without anybody opening them.

Timetable against actual

9.8h

Actual 12.5h, 2.7h over the timetable.

Operations

The lane diagram

Read it left to right. more

Person1 station and 36% of the dwellAgent3 stations and 42% of the dwellShared spine1 station and 22% of the dwell3 crossings 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

Treasury and Cash Management

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.

#	Station	Lane	Who	Layer	Dwell	Target	In flight	System
1	Detect expiry	GBS	Template Selection Agent	gbs	2h 50m	4h 10m	7	Group ERP — Financials
2	Assess value	Agent	Terms Assembly Agent	workflow	2h 28m	4h 57m	36	Group ERP — Financials
3	Recommend	Agent	Legal Routing Agent	workflow	1h 40m	3h 44m	7	Source-to-Pay Suite
4	Owner decision Held for a named human when the unit exceeds the supplier contract decision envelope, when confidence falls below the floor, or when a policy clause is engaged.	Human	Director, Contract Management	policy	4h 36m	11h	5	Group ERP — Financials
5	Route to sourcing	Agent	Contract Repository Agent	workflow	1h 18m	2h 36m	14	Treasury and Cash Management

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

Move something

Demand100%

2,080 a week is what the estate records. more

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 gates274 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. more

Person time a week

9,568h

2,080 items at 276 minutes of decision each.

Agent time a week

17,194.7h

496 minutes an item, which does not compete for a person.

Gate load

100%

Inside capacity, with 22h of headroom.

Stations without a person

80%

1 gate left on 5 stations.

Where an item spends its time

36% waiting on a person

64% in the agent lane

An item now takes 772 minutes of worked time end to end against 772 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 Expiry & Renewal Sweep

The simulation is arithmetic on the estate, not a queueing model. more

How it runs

Run it again, going wrong

The same unit and the same stations, broken the way the estate already records breaking. more

5 stations, walked twice

Once clean, once with the categories the estate counts

This is the same unit on the same stations, breaking. more

No break below was chosen. more

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

5 stations, nothing waiting, nothing sent back

0 min of 13 hrs

now Detect expiry · Template Selection Agent · 2.8 hrs

As the ledger has it

the same stations, plus 4 categories the estate already counts

0 min of 28 hrs

now Detect expiry · Template Selection Agent · 2.8 hrs

personagentshared spinework the break addsnobody working it

What breaks, and where it is counted

No break below was chosen. more

What the two runs say together

4 counted categories land on this procedure. more

What this run cannot claim

These breaks are shown together on one unit so the shape of a bad day fits on one screen. more

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

Two clocks run. Worked time is the sum of the time the work is actually being done … more

Live observability

Systems this service would touch

Attributed by rule from the function's system list. more

3 systems attributed

0 of 3 returning records

The system register

Group ERP — Financials

SAP S/4HANA · ledger · bidirectional · critical

modeled

3 of 5 stations attributed here · would write back

Source-to-Pay Suite

SAP Ariba · procurement · bidirectional · critical

modeled

1 of 5 stations attributed here · would write back

Treasury and Cash Management

Kyriba · banking · bidirectional · critical

modeled

1 of 5 stations attributed here · would write back

System attribution is a rule, not a reading. more

Who runs it

Orchestration and accountability

Orchestrated by: Procurement Contract Orchestrator
That orchestrator’s remit: Owns supplier contract work end to end inside Procurement & Source-to-Pay. Runs 3 lines across 18 stations, drains the repeatable share into the S2P tower, and holds 5 human gates.
Accountable person: Director, Contract Management
Sub-function: Contract Execution
Shared spine tower: s2p
Hand-over points: None — this service stays inside its function

Other services in this sub-function

2 alongside this one

Supplier AgreementPR5A Contract AmendmentPR5B

What this page is and is not

This is a catalogue of the modeled estate. more