LensReading which lens this session carries.
The catalogueFinanceControllership & PolicyTransactional

Service FI5B

Policy Query

Runs transactional. Starts when a threshold is crossed. It runs 6,032 times a week across 6 stations. One of those stations stops for a person and 5 are done by an agent, 1 of them on the shared spine.

Runs a week

6,032

103 in flight right now.

Stations

6

1 person · 4 agent · 1 spine

Agent share of steps

83%

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

Decisions a person makes

1

Held by Chief Accounting Officer.

Touchless

56%

Share of runs that complete without anybody opening them.

Timetable against actual

19.7h

Actual 24.1h, 4.4h over the timetable.

Operations

The lane diagram

Read it left to right.

Person1 station and 41% of the dwellAgent4 stations and 44% of the dwellShared spine1 station and 14% of the dwell4 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
Group ERP — Financials
Core HR and Payroll
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

Intake

AgentAccounting Policy Agentworkflow1h 2m2h 25m12Bank Connectivity Gateway
2

Retrieve policy

GBSAccounting Policy Agentgbs55m1h 19m14Group ERP — Financials
3

Draft answer

AgentStandards Watch Agentworkflow19m44m26Enterprise Data Warehouse
4

Controller review

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

HumanChief Accounting Officerpolicy2h 39m5h 7m1Group ERP — Financials
5

Deliver

AgentDisclosure Agentworkflow22m35m40Group ERP — Financials
6

Log precedent

AgentPolicy Interpretation Agentworkflow1h 8m1h 21m10Core HR and Payroll

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,032 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 gates457 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
15,984.8h
6,032 items at 159 minutes of decision each.
Agent time a week
22,720.5h
226 minutes an item, which does not compete for a person.
Gate load
100%
Inside capacity, with 10.2h of headroom.
Stations without a person
83%
1 gate left on 6 stations.
Where an item spends its time
41% waiting on a person
59% in the agent lane
An item now takes 385 minutes of worked time end to end against 385 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 Policy Query

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

now Intake · Accounting Policy Agent · 1.0 hrs

As the ledger has it

the same stations, plus 5 categories the estate already counts

0 min of 20 hrs

now Intake · Accounting Policy Agent · 1.0 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.

4 systems attributed

0 of 4 returning records

The system register

Group ERP — Financials

SAP S/4HANA · ledger · bidirectional · critical

modeled

3 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

Core HR and Payroll

Workday HCM · hcm · bidirectional · critical

modeled

1 of 6 stations attributed here · would write back

System attribution is a rule, not a reading.

Who runs it

Orchestration and accountability

Orchestrated by
Controllership Orchestrator
That orchestrator’s remit
Owns technical position work end to end inside Finance. Runs 3 lines across 19 stations, drains the repeatable share into no shared tower, and holds 4 human gates.
Accountable person
Chief Accounting Officer
Sub-function
Controllership & Policy
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

Technical Accounting PositionFI5AStandards Change ResponseFI5C

What this page is and is not

This is a catalogue of the modeled estate.