LensReading which lens this session carries.
The catalogueFinanceManagement ReportingTransactional

Service FI3C

Anomaly Investigation

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

6,187

72 in flight right now.

Stations

5

1 person · 3 agent · 1 spine

Agent share of steps

80%

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

Decisions a person makes

1

Held by Director, Management Reporting.

Touchless

85%

Share of runs that complete without anybody opening them.

Timetable against actual

13.5h

Actual 13.7h, 0.2h over the timetable.

Operations

The lane diagram

Read it left to right.

Person1 station and 48% of the dwellAgent3 stations and 47% of the dwellShared spine1 station and 5% of the dwell3 crossings between lanes
Human
decides
Agent
does the work
GBS
shared spine
System
attributed by rule
Group ERP — Financials
Bank Connectivity Gateway
Enterprise Data Warehouse
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

Detect

GBSReport Assembly Agentgbs43m1h 35m9Group ERP — Financials
2

Diagnose

AgentNarrative Drafting Agentworkflow2h 49m6h 5m1Bank Connectivity Gateway
3

Draft explanation

AgentData Quality Agentworkflow1h 22m1h 40m36Enterprise Data Warehouse
4

Owner confirm

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

HumanDirector, Management Reportingpolicy7h 13m15h 39m4Group ERP — Financials
5

Log

AgentAnomaly Detection Agentworkflow2h 58m6h 43m22Group 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%
6,187 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 gates1276 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
44,649.5h
6,187 items at 433 minutes of decision each.
Agent time a week
48,671.1h
472 minutes an item, which does not compete for a person.
Gate load
100%
Inside capacity, with 10.5h of headroom.
Stations without a person
80%
1 gate left on 5 stations.
Where an item spends its time
48% waiting on a person
52% in the agent lane
An item now takes 905 minutes of worked time end to end against 905 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 Anomaly Investigation

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.

5 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

5 stations, nothing waiting, nothing sent back

0 min of 15 hrs

now Detect · Report Assembly Agent · 43 min

As the ledger has it

the same stations, plus 5 categories the estate already counts

0 min of 31 hrs

now Detect · Report Assembly Agent · 43 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

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.

3 systems attributed

0 of 3 returning records

Group ERP — Financials

SAP S/4HANA · ledger · bidirectional · critical

modeled

3 of 5 stations attributed here · would write back

Bank Connectivity Gateway

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

not-connected

1 of 5 stations attributed here · would write back

Enterprise Data Warehouse

Snowflake · analytics · inbound · critical

modeled

1 of 5 stations attributed here · read only

System attribution is a rule, not a reading.

Who runs it

Orchestration and accountability

Orchestrated by
Management Reporting Orchestrator
That orchestrator’s remit
Owns report work end to end inside Finance. Runs 3 lines across 17 stations, drains the repeatable share into the P2P tower, and holds 3 human gates.
Accountable person
Director, Management Reporting
Sub-function
Management Reporting
Shared spine tower
p2p
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.