LensReading which lens this session carries.
The catalogueFinanceFinance SystemsTransactional

Service FI11B

Interface Incident

Runs transactional. Starts when an upstream system posts an event. It runs 1,819 times a week across 6 stations. One of those stations stops for a person and 5 are done by an agent, 2 of them on the shared spine.

Runs a week

1,819

108 in flight right now.

Stations

6

1 person · 3 agent · 2 spine

Agent share of steps

83%

Autonomy on this service is set at 71% against a ceiling of 81%.

Decisions a person makes

1

Held by Director, Finance Systems.

Touchless

75%

Share of runs that complete without anybody opening them.

Timetable against actual

21.8h

Actual 21.0h, 0.8h under the timetable.

Operations

The lane diagram

Read it left to right.

Person1 station and 28% of the dwellAgent3 stations and 61% of the dwellShared spine2 stations and 11% of the dwell4 crossings between lanes
Human
decides
Agent
does the work
GBS
shared spine
System
attributed by rule
Group ERP — Financials
Bank Connectivity Gateway
Group ERP — Financials
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.

#StationLaneWhoLayerDwellTargetIn flightSystem
1

Detect

GBSMaster Data Agentgbs54m1h 37m21Group ERP — Financials
2

Classify

AgentInterface Monitoring Agentworkflow3h 3m6h 34m35Bank Connectivity Gateway
3

Auto-retry

GBSMaster Data Agentgbs23m33m9Group ERP — Financials
4

Escalate

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

HumanDirector, Finance Systemspolicy3h 6m7h 11m2Group ERP — Financials
5

Restore

AgentChange Release Agentworkflow2h 31m3h 46m32Enterprise Data Warehouse
6

Post-mortem

AgentSystems Policy Agentworkflow1h 14m1h 44m9Group 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%
1,819 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 gates162 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
5,638.9h
1,819 items at 186 minutes of decision each.
Agent time a week
14,703.6h
485 minutes an item, which does not compete for a person.
Gate load
99%
Inside capacity, with 31.1h of headroom.
Stations without a person
83%
1 gate left on 6 stations.
Where an item spends its time
28% waiting on a person
72% in the agent lane
An item now takes 671 minutes of worked time end to end against 671 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 Interface Incident

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

now Detect · Master Data Agent · 54 min

As the ledger has it

the same stations, plus 4 categories the estate already counts

0 min of 26 hrs

now Detect · Master Data Agent · 54 min

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

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

3 systems attributed

0 of 3 returning records

Group ERP — Financials

SAP S/4HANA · ledger · bidirectional · critical

modeled

4 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

Enterprise Data Warehouse

Snowflake · analytics · inbound · critical

modeled

1 of 6 stations attributed here · read only

System attribution is a rule, not a reading.

Who runs it

Orchestration and accountability

Orchestrated by
Finance Systems Orchestrator
That orchestrator’s remit
Owns change work end to end inside Finance. Runs 3 lines across 18 stations, drains the repeatable share into the R2R tower, and holds 3 human gates.
Accountable person
Director, Finance Systems
Sub-function
Finance Systems
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.