The catalogue FinanceManagement ReportingTransactional

Service FI3A

Monthly Reporting Pack

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

1,086

66 in flight right now.

Stations

1 person · 1 agent · 4 spine

Agent share of steps

83%

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

Decisions a person makes

Held by Director, Management Reporting.

Touchless

85%

Share of runs that complete without anybody opening them.

Timetable against actual

1.1h

Actual 1.1h, 0.0h over the timetable.

Operations

The lane diagram

Read it left to right. more

Person1 station and 17% of the dwellAgent1 station and 19% of the dwellShared spine4 stations and 64% 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

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	Assemble	GBS	Report Assembly Agent	gbs	53m	1h 48m	5	Group ERP — Financials
2	Quality check	GBS	Report Assembly Agent	gbs	15m	28m	8	Group ERP — Financials
3	Draft narrative	Agent	Data Quality Agent	workflow	1h 36m	2h 29m	19	Bank Connectivity Gateway
4	Controller review 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.	Human	Director, Management Reporting	policy	1h 28m	2h 59m	2	Group ERP — Financials
5	Publish	GBS	Report Assembly Agent	gbs	2h 25m	2h 53m	9	Group ERP — Financials
6	Distribute	GBS	Report Assembly Agent	gbs	1h 52m	2h 43m	23	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%

1,086 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 gates46 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

1,592.8h

1,086 items at 88 minutes of decision each.

Agent time a week

7,620.1h

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

Gate load

99%

Inside capacity, with 17.2h of headroom.

Stations without a person

83%

1 gate left on 6 stations.

Where an item spends its time

17% waiting on a person

83% in the agent lane

An item now takes 509 minutes of worked time end to end against 509 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 Monthly Reporting Pack

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

now Assemble · Report Assembly Agent · 53 min

As the ledger has it

the same stations, plus 5 categories the estate already counts

0 min of 23 hrs

now Assemble · Report Assembly Agent · 53 min

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

5 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

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

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

Ad-hoc QueryFI3B Anomaly InvestigationFI3C

What this page is and is not

This is a catalogue of the modeled estate. more