LensReading which lens this session carries.
The catalogueFinanceCost & ProfitabilityAnalytical

Service FI10A

Monthly Profitability Read

Runs analytical. Starts when the cycle calendar fires. It runs 47 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

47

137 in flight right now.

Stations

6

1 person · 3 agent · 2 spine

Agent share of steps

83%

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

Decisions a person makes

1

Held by Director, Profitability Analytics.

Touchless

61%

Share of runs that complete without anybody opening them.

Timetable against actual

110.8h

Actual 144.0h, 33.2h over the timetable.

Operations

The lane diagram

Read it left to right.

Person1 station and 28% of the dwellAgent3 stations and 46% of the dwellShared spine2 stations and 26% 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
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

Allocate costs

GBSCost Allocation Agentgbs7h 9m14h40Group ERP — Financials
2

Model margin

AgentProduct Margin Agentworkflow12h 24m25h 19m34Bank Connectivity Gateway
3

Rank customers

AgentCustomer Profitability Agentworkflow13h 39m17h 49m4Enterprise Data Warehouse
4

Draft readout

AgentCost-to-Serve Agentworkflow11h 18m15h 10m26Group 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.

HumanDirector, Profitability Analyticspolicy22h 33m31h 23m6Group ERP — Financials
6

Publish

GBSCost Allocation Agentgbs13h 22m25h 45m27Group 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%
47 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 gates31 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
1,059.9h
47 items at 1,353 minutes of decision each.
Agent time a week
2,719.7h
3,472 minutes an item, which does not compete for a person.
Gate load
98%
Inside capacity, with 25.2h 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 4,825 minutes of worked time end to end against 4,825 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 Profitability Read

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 3.4 days

now Allocate costs · Cost Allocation Agent · 7.2 hrs

As the ledger has it

the same stations, plus 5 categories the estate already counts

0 min of 5.7 days

now Allocate costs · Cost Allocation Agent · 7.2 hrs

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

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