LensReading which lens this session carries.
The catalogueFinanceTreasury & CashTransactional

Service FI6A

Daily Cash Cycle

Runs transactional. Starts when a request lands in the queue. It runs 5,348 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

5,348

108 in flight right now.

Stations

6

1 person · 1 agent · 4 spine

Agent share of steps

83%

Autonomy on this service is set at 73% against a ceiling of 74%.

Decisions a person makes

1

Held by Corporate Treasurer.

Touchless

76%

Share of runs that complete without anybody opening them.

Timetable against actual

8.9h

Actual 6.9h, 2.0h under the timetable.

Operations

The lane diagram

Read it left to right.

Person1 station and 51% of the dwellAgent1 station and 2% of the dwellShared spine4 stations and 47% of the dwell3 crossings between lanes
Human
decides
Agent
does the work
GBS
shared spine
System
attributed by rule
Group ERP — Financials
Group ERP — Financials
Bank Connectivity Gateway
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

Sweep balances

GBSCash Position Agentgbs1h 7m1h 32m4Group ERP — Financials
2

Forecast liquidity

GBSCash Position Agentgbs1h 49m3h 26m22Group ERP — Financials
3

Propose position

AgentFX Exposure Agentworkflow21m29m9Bank Connectivity Gateway
4

Treasurer approve

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

HumanCorporate Treasurerpolicy8h 6m9h 35m1Group ERP — Financials
5

Execute

GBSCash Position Agentgbs1h 33m2h 8m38Group ERP — Financials
6

Reconcile

GBSCash Position Agentgbs2h 54m6h 57m34Group 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%
5,348 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 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.
Person time a week
43,318.8h
5,348 items at 486 minutes of decision each.
Agent time a week
41,357.9h
464 minutes an item, which does not compete for a person.
Gate load
100%
Inside capacity, with 11.2h of headroom.
Stations without a person
83%
1 gate left on 6 stations.
Where an item spends its time
51% waiting on a person
49% in the agent lane
An item now takes 950 minutes of worked time end to end against 950 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 Daily Cash Cycle

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 Sweep balances · Cash Position Agent · 1.1 hrs

As the ledger has it

the same stations, plus 5 categories the estate already counts

0 min of 30 hrs

now Sweep balances · Cash Position Agent · 1.1 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

Bank Connectivity Gateway

SWIFT and host-to-host channels · banking · bidirectional · critical

not-connected

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
Treasury Orchestrator
That orchestrator’s remit
Owns cash action work end to end inside Finance. Runs 3 lines across 17 stations, drains the repeatable share into the R2R tower, and holds 5 human gates.
Accountable person
Corporate Treasurer
Sub-function
Treasury & Cash
Shared spine tower
r2r
Hand-over points
None — this service stays inside its function

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.