The catalogue FinanceCost & ProfitabilityAnalytical

Service FI10B

Cost-to-Serve Study

Runs analytical. Starts when the reporting period closes. It runs 23 times a week across 5 stations. One of those stations stops for a person and 4 are done by an agent, none of them on the shared spine.

Runs a week

91 in flight right now.

Stations

1 person · 4 agent · 0 spine

Agent share of steps

80%

Autonomy on this service is set at 55% against a ceiling of 84%.

Decisions a person makes

Held by Director, Profitability Analytics.

Touchless

70%

Share of runs that complete without anybody opening them.

Timetable against actual

189.4h

Actual 200.5h, 11.1h over the timetable.

Operations

The lane diagram

Read it left to right. more

Person1 station and 23% of the dwellAgent4 stations and 77% of the dwellShared spine0 stations and 0% of the dwell1 crossing between lanes

Human

decides

Agent

does the work

GBS

shared spine

System

attributed by rule

Bank Connectivity Gateway

Enterprise Data Warehouse

Group ERP — Financials

Core HR and Payroll

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 scope	Agent	Cost Allocation Agent	workflow	12h 32m	19h 53m	3	Bank Connectivity Gateway
2	Model	Agent	Product Margin Agent	workflow	7h 18m	11h 12m	38	Enterprise Data Warehouse
3	Compare channels	Agent	Customer Profitability Agent	workflow	11h 37m	18h 13m	34	Group ERP — Financials
4	Draft finding	Agent	Cost-to-Serve Agent	workflow	10h 52m	25h 42m	15	Core HR and Payroll
5	Ratify 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	Director, Profitability Analytics	policy	12h 57m	28h 17m	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%

23 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 gates9 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

297.9h

23 items at 777 minutes of decision each.

Agent time a week

973.3h

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

Gate load

95%

Inside capacity, with 17.2h of headroom.

Stations without a person

80%

1 gate left on 5 stations.

Where an item spends its time

23% waiting on a person

77% in the agent lane

An item now takes 3,316 minutes of worked time end to end against 3,316 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 Cost-to-Serve Study

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.3 days

now Frame scope · Cost Allocation Agent · 13 hrs

As the ledger has it

the same stations, plus 2 categories the estate already counts

0 min of 2.4 days

now Frame scope · Cost Allocation Agent · 13 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

2 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

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

4 systems attributed

0 of 4 returning records

The system register

Group ERP — Financials

SAP S/4HANA · ledger · bidirectional · critical

modeled

2 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

Core HR and Payroll

Workday HCM · hcm · bidirectional · critical

modeled

1 of 5 stations attributed here · would write back

System attribution is a rule, not a reading. more

Who runs it

Orchestration and accountability

Orchestrated by: Profitability Orchestrator
That orchestrator’s remit: Owns analysis work end to end inside Finance. Runs 3 lines across 16 stations, drains the repeatable share into the P2P tower, and holds 3 human gates.
Accountable person: Director, Profitability Analytics
Sub-function: Cost & Profitability
Shared spine tower: Not on the shared spine
Hand-over points: None — this service stays inside its function

Other services in this sub-function

2 alongside this one

Monthly Profitability ReadFI10A Cost Structure PositionFI10C

What this page is and is not

This is a catalogue of the modeled estate. more