LensReading which lens this session carries.
The catalogueAI GBS & Global Business ServicesGlobal Process OwnershipJudgment

Service GB6C

Global Process Design Position

Runs judgment. Starts when a leadership team frames the question. It runs 2 times a week across 7 stations. One of those stations stops for a person and 6 are done by an agent, none of them on the shared spine.

Runs a week

2

124 in flight right now.

Stations

7

1 person · 6 agent · 0 spine

Agent share of steps

86%

Autonomy on this service is set at 48% against a ceiling of 66%.

Decisions a person makes

1

Held by Global Process Owner.

Touchless

26%

Share of runs that complete without anybody opening them.

Timetable against actual

392.1h

Actual 495.5h, 103.4h over the timetable.

Operations

The lane diagram

Read it left to right.

Person1 station and 15% of the dwellAgent6 stations and 85% 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
Enterprise Data Warehouse
Enterprise Data Warehouse
Enterprise Data Warehouse
Enterprise Data Warehouse
Enterprise Data Warehouse
Enterprise Data Warehouse
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

AgentProcess Model Agentstrategy39h 51m89h 57m37Enterprise Data Warehouse
2

Gather evidence

AgentVariant Detection Agentstrategy35h 26m59h 17m16Enterprise Data Warehouse
3

Model options

AgentStandardization Agentstrategy40h 4m55h 17m21Enterprise Data Warehouse
4

Draft position

AgentControl Design Agentstrategy27h 8m64h 21m6Enterprise Data Warehouse
5

Challenge

AgentProcess Mining Agentstrategy31h 20m38h 18m26Enterprise Data Warehouse
6

Revise

AgentCompliance Mapping Agentstrategy61h 25m77h 47m14Enterprise Data Warehouse
7

Ratify

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

HumanGlobal Process Ownerpolicy41h 55m77h 16m4Group 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%
2 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 gates3 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
83.8h
2 items at 2,515 minutes of decision each.
Agent time a week
470.5h
14,114 minutes an item, which does not compete for a person.
Gate load
80%
Inside capacity, with 21.2h of headroom.
Stations without a person
86%
1 gate left on 7 stations.
Where an item spends its time
15% waiting on a person
85% in the agent lane
An item now takes 16,629 minutes of worked time end to end against 16,629 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 Global Process Design 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.

7 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

7 stations, nothing waiting, nothing sent back

0 min of 11.5 days

now Frame question · Process Model Agent · 40 hrs

As the ledger has it

the same stations, plus 3 categories the estate already counts

0 min of 11.8 days

now Frame question · Process Model Agent · 40 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

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.

2 systems attributed

0 of 2 returning records

Enterprise Data Warehouse

Snowflake · analytics · inbound · critical

modeled

6 of 7 stations attributed here · read only

Group ERP — Financials

SAP S/4HANA · ledger · bidirectional · critical

modeled

1 of 7 stations attributed here · would write back

System attribution is a rule, not a reading.

Who runs it

Orchestration and accountability

Orchestrated by
Process Ownership Orchestrator
That orchestrator’s remit
Owns process standard work end to end inside AI GBS & Global Business Services. Runs 3 lines across 19 stations, drains the repeatable share into no shared tower, and holds 3 human gates.
Accountable person
Global Process Owner
Sub-function
Global Process Ownership
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.