LensReading which lens this session carries.
The catalogueAdministrationCorporate ServicesJudgment

Service AD10C

Corporate Services Model Position

Runs judgment. Starts when the annual doctrine review opens. It runs 1 times a week across 6 stations. One of those stations stops for a person and 5 are done by an agent, none of them on the shared spine.

Runs a week

1

131 in flight right now.

Stations

6

1 person · 5 agent · 0 spine

Agent share of steps

83%

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

Decisions a person makes

1

Held by Director, Corporate Services.

Touchless

49%

Share of runs that complete without anybody opening them.

Timetable against actual

763.1h

Actual 803.1h, 40.0h over the timetable.

Operations

The lane diagram

Read it left to right.

Person1 station and 36% of the dwellAgent5 stations and 64% 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
Group ERP — Financials
Group ERP — Financials
Group ERP — Financials
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 question

AgentService Catalog Agentstrategy51h 59m89h 17m41Group ERP — Financials
2

Gather evidence

AgentRequest Triage Agentstrategy68h 52m114h 29m23Group ERP — Financials
3

Model options

AgentSupplier Performance Agentstrategy66h140h 33m22Group ERP — Financials
4

Draft position

AgentCost Allocation Agentstrategy10h 33m20h 3m20Group ERP — Financials
5

Challenge

AgentService Level Agentstrategy47h 56m112h 46m19Group ERP — Financials
6

Ratify

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

HumanDirector, Corporate Servicespolicy135h 9m238h 57m6Group 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 0
This service has at most one gate, so there is nothing to hand over without removing the last human decision.
People on the gates4 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
135.2h
1 items at 8,109 minutes of decision each.
Agent time a week
245.3h
14,720 minutes an item, which does not compete for a person.
Gate load
97%
Inside capacity, with 4.9h of headroom.
Stations without a person
83%
1 gate left on 6 stations.
Where an item spends its time
36% waiting on a person
64% in the agent lane
An item now takes 22,829 minutes of worked time end to end against 22,829 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 Corporate Services Model 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.

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

now Frame question · Service Catalog Agent · 2.2 days

As the ledger has it

the same stations, plus 3 categories the estate already counts

0 min of 16.1 days

now Frame question · Service Catalog Agent · 2.2 days

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

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

1 systems attributed

0 of 1 returning records

Group ERP — Financials

SAP S/4HANA · ledger · bidirectional · critical

modeled

6 of 6 stations attributed here · would write back

System attribution is a rule, not a reading.

Who runs it

Orchestration and accountability

Orchestrated by
Corporate Services Orchestrator
That orchestrator’s remit
Owns service request work end to end inside Administration. Runs 3 lines across 17 stations, drains the repeatable share into the S2P tower, and holds 2 human gates.
Accountable person
Director, Corporate Services
Sub-function
Corporate Services
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.