The catalogue FinanceFP&A & PlanningAnalytical

Service FI1B

Scenario Request

Runs analytical. Starts when the reporting period closes. It runs 84 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

76 in flight right now.

Stations

1 person · 3 agent · 1 spine

Agent share of steps

80%

Autonomy on this service is set at 51% against a ceiling of 76%.

Decisions a person makes

Held by VP Financial Planning & Analysis.

Touchless

54%

Share of runs that complete without anybody opening them.

Timetable against actual

149.3h

Actual 164.5h, 15.2h over the timetable.

Operations

The lane diagram

Read it left to right. more

Person1 station and 42% of the dwellAgent3 stations and 42% of the dwellShared spine1 station and 15% of the dwell3 crossings between lanes

Human

decides

Agent

does the work

GBS

shared spine

System

attributed by rule

Bank Connectivity Gateway

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	Frame scenario	Agent	Driver Model Agent	workflow	5h 33m	12h 39m	20	Bank Connectivity Gateway
2	Model	GBS	Driver Model Agent	gbs	10h 10m	19h 36m	1	Group ERP — Financials
3	Stress test	Agent	Variance Explanation Agent	workflow	9h 26m	13h 56m	35	Enterprise Data Warehouse
4	Draft finding	Agent	Commentary Drafting Agent	workflow	13h 47m	26h 45m	19	Group ERP — Financials
5	Leader review Held for a named human when the unit exceeds the analysis decision envelope, when confidence falls below the floor, or when a policy clause is engaged.	Human	VP Financial Planning & Analysis	policy	28h 46m	47h 25m	1	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%

84 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 gates70 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

2,416.4h

84 items at 1,726 minutes of decision each.

Agent time a week

3,270.4h

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

Gate load

99%

Inside capacity, with 33.6h of headroom.

Stations without a person

80%

1 gate left on 5 stations.

Where an item spends its time

42% waiting on a person

58% in the agent lane

An item now takes 4,062 minutes of worked time end to end against 4,062 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 Scenario Request

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

5 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

5 stations, nothing waiting, nothing sent back

0 min of 2.8 days

now Frame scenario · Driver Model Agent · 5.5 hrs

As the ledger has it

the same stations, plus 5 categories the estate already counts

0 min of 4.9 days

now Frame scenario · Driver Model Agent · 5.5 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

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

3 systems attributed

0 of 3 returning records

The system register

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

Who runs it

Orchestration and accountability

Orchestrated by: FP&A Orchestrator
That orchestrator’s remit: Owns analysis work end to end inside Finance. Runs 3 lines across 18 stations, drains the repeatable share into the P2P tower, and holds 4 human gates.
Accountable person: VP Financial Planning & Analysis
Sub-function: FP&A & Planning
Shared spine tower: p2p
Hand-over points: None — this service stays inside its function

Other services in this sub-function

2 alongside this one

Monthly Business ReviewFI1A Capital Allocation PositionFI1C

What this page is and is not

This is a catalogue of the modeled estate. more