LensReading which lens this session carries.
The catalogueFinanceControllership & PolicyJudgment

Service FI5A

Technical Accounting Position

Runs judgment. Starts when a break condition on a live position fires. It runs 1 times a week across 8 stations. 2 of those stations stop for a person and 6 are done by an agent, 1 of them on the shared spine.

Runs a week

1

72 in flight right now.

Stations

8

2 person · 5 agent · 1 spine

Agent share of steps

75%

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

Decisions a person makes

2

Held by Chief Accounting Officer.

Touchless

29%

Share of runs that complete without anybody opening them.

Timetable against actual

761.5h

Actual 963.1h, 201.6h over the timetable.

Operations

The lane diagram

Read it left to right.

Person2 stations and 48% of the dwellAgent5 stations and 43% of the dwellShared spine1 station and 8% of the dwell2 crossings between lanes
Human
decides
Agent
does the work
GBS
shared spine
System
attributed by rule
Enterprise Data Warehouse
Enterprise Data Warehouse
Enterprise Data Warehouse
Enterprise Data Warehouse
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

Frame issue

AgentAccounting Policy Agentstrategy30h 14m47h 7m9Enterprise Data Warehouse
2

Research standards

AgentTechnical Position Agentstrategy66h 50m151h 44m5Enterprise Data Warehouse
3

Model treatments

AgentStandards Watch Agentstrategy34h 30m54h 24m10Enterprise Data Warehouse
4

Draft position

AgentJudgment Documentation Agentstrategy33h 6m41h 39m27Enterprise Data Warehouse
5

Challenge

AgentDisclosure Agentstrategy10h 36m22h 31m17Enterprise Data Warehouse
6

Controller ratify

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 Officerpolicy47h 52m80h 59m2Group ERP — Financials
7

Auditor concur

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 Officerpolicy146h 58m196h0Group ERP — Financials
8

File

GBSControllership Orchestratorgbs33h 40m72h 12m2Group 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%
1 a week is what the estate records.
Decisions handed to agents0 of 2
Cheapest decision first. The last gate never moves: something on this service always ends with a person.
People on the gates6 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
194.8h
1 items at 11,690 minutes of decision each.
Agent time a week
208.9h
12,536 minutes an item, which does not compete for a person.
Gate load
93%
Inside capacity, with 15.2h of headroom.
Stations without a person
75%
2 gates left on 8 stations.
Where an item spends its time
48% waiting on a person
52% in the agent lane
An item now takes 24,226 minutes of worked time end to end against 24,226 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 Technical Accounting Position

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.

8 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

8 stations, nothing waiting, nothing sent back

0 min of 16.8 days

now Frame issue · Accounting Policy Agent · 30 hrs

As the ledger has it

the same stations, plus 4 categories the estate already counts

0 min of 17.6 days

now Frame issue · Accounting Policy Agent · 30 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

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

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.

2 systems attributed

0 of 2 returning records

Enterprise Data Warehouse

Snowflake · analytics · inbound · critical

modeled

5 of 8 stations attributed here · read only

Group ERP — Financials

SAP S/4HANA · ledger · bidirectional · critical

modeled

3 of 8 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

What this page is and is not

This is a catalogue of the modeled estate.