The catalogue AI GBS & Global Business ServicesO2C Control TowerTransactional

Service GB3C

Collections Cycle

Runs transactional. Starts when a threshold is crossed. It runs 7,557 times a week across 6 stations. One of those stations stops for a person and 5 are done by an agent, 4 of them on the shared spine.

Runs a week

7,557

99 in flight right now.

Stations

1 person · 1 agent · 4 spine

Agent share of steps

83%

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

Decisions a person makes

Held by Tower Lead, Order-to-Cash.

Touchless

87%

Share of runs that complete without anybody opening them.

Timetable against actual

6.7h

Actual 6.7h, 0.0h over the timetable.

Operations

The lane diagram

Read it left to right. more

Person1 station and 30% of the dwellAgent1 station and 15% of the dwellShared spine4 stations and 55% of the dwell3 crossings between lanes

Human

decides

Agent

does the work

GBS

shared spine

System

attributed by rule

Group ERP — Financials

Enterprise Data Warehouse

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.

#	Station	Lane	Who	Layer	Dwell	Target	In flight	System
1	Age ledger	GBS	Order Validation Agent	gbs	3h 5m	5h 14m	6	Group ERP — Financials
2	Segment	GBS	Order Validation Agent	gbs	2h 6m	3h 11m	25	Group ERP — Financials
3	Dunning	GBS	Order Validation Agent	gbs	2h 49m	5h 52m	38	Group ERP — Financials
4	Promise to pay	Agent	Cash Application Agent	workflow	2h 53m	3h 41m	7	Enterprise Data Warehouse
5	Escalate 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.	Human	Tower Lead, Order-to-Cash	policy	5h 44m	12h 18m	8	Group ERP — Financials
6	Recover	GBS	Order Validation Agent	gbs	2h 34m	5h 49m	15	Group 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. more

Move something

Demand100%

7,557 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 gates1238 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

43,326.8h

7,557 items at 344 minutes of decision each.

Agent time a week

101,641.7h

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

Gate load

100%

Inside capacity, with 3.2h of headroom.

Stations without a person

83%

1 gate left on 6 stations.

Where an item spends its time

30% waiting on a person

70% in the agent lane

An item now takes 1,151 minutes of worked time end to end against 1,151 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 Collections Cycle

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

6 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

6 stations, nothing waiting, nothing sent back

0 min of 19 hrs

now Age ledger · Order Validation Agent · 3.1 hrs

As the ledger has it

the same stations, plus 4 categories the estate already counts

0 min of 38 hrs

now Age ledger · Order Validation Agent · 3.1 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

2 systems attributed

0 of 2 returning records

The system register

Group ERP — Financials

SAP S/4HANA · ledger · bidirectional · critical

modeled

5 of 6 stations attributed here · would write back

Enterprise Data Warehouse

Snowflake · analytics · inbound · critical

modeled

1 of 6 stations attributed here · read only

System attribution is a rule, not a reading. more

Who runs it

Orchestration and accountability

Orchestrated by: Order-to-Cash 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 O2C tower, and holds 3 human gates.
Accountable person: Tower Lead, Order-to-Cash
Sub-function: O2C Control Tower
Shared spine tower: o2c
Hand-over points: None — this service stays inside its function

Other services in this sub-function

3 alongside this one

Order to InvoiceGB3A Cash ApplicationGB3B Dispute to ResolutionGB3D

What this page is and is not

This is a catalogue of the modeled estate. more