The catalogue AI GBS & Global Business ServicesAutomation FactoryJudgment

Service GB7D

Automation Portfolio Position

Runs judgment. Starts when a break condition on a live position fires. It runs 5 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

161 in flight right now.

Stations

1 person · 5 agent · 0 spine

Agent share of steps

83%

Autonomy on this service is set at 68% against a ceiling of 80%.

Decisions a person makes

Held by Head of Automation.

Touchless

50%

Share of runs that complete without anybody opening them.

Timetable against actual

417.3h

Actual 543.5h, 126.2h over the timetable.

Operations

The lane diagram

Read it left to right. more

Person1 station and 54% of the dwellAgent5 stations and 46% 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

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.

#	Station	Lane	Who	Layer	Dwell	Target	In flight	System
1	Frame question	Agent	Opportunity Mining Agent	strategy	49h 49m	83h 18m	40	Enterprise Data Warehouse
2	Gather evidence	Agent	Feasibility Scoring Agent	strategy	29h 42m	61h 43m	27	Enterprise Data Warehouse
3	Model options	Agent	Build Agent	strategy	31h 1m	63h 55m	35	Enterprise Data Warehouse
4	Draft position	Agent	Test Harness Agent	strategy	12h 23m	17h 40m	43	Enterprise Data Warehouse
5	Challenge	Agent	Deployment Agent	strategy	30h 13m	57h 17m	9	Enterprise Data Warehouse
6	Ratify Held for a named human when the unit exceeds the automation decision envelope, when confidence falls below the floor, or when a policy clause is engaged.	Human	Head of Automation	policy	181h 25m	248h 19m	7	Group 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. more

Move something

Demand100%

5 a week is what the estate records. more

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

Person time a week

907.1h

5 items at 10,885 minutes of decision each.

Agent time a week

765.7h

9,188 minutes an item, which does not compete for a person.

Gate load

100%

Inside capacity, with 2.9h of headroom.

Stations without a person

83%

1 gate left on 6 stations.

Where an item spends its time

54% waiting on a person

46% in the agent lane

An item now takes 20,073 minutes of worked time end to end against 20,073 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 Automation Portfolio Position

The simulation is arithmetic on the estate, not a queueing model. more

How it runs

Run it again, going wrong

The same unit and the same stations, broken the way the estate already records breaking. more

6 stations, walked twice

Once clean, once with the categories the estate counts

This is the same unit on the same stations, breaking. more

No break below was chosen. more

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

now Frame question · Opportunity Mining Agent · 2.1 days

As the ledger has it

the same stations, plus 2 categories the estate already counts

0 min of 14.0 days

now Frame question · Opportunity Mining Agent · 2.1 days

personagentshared spinework the break addsnobody working it

What breaks, and where it is counted

No break below was chosen. more

What the two runs say together

2 counted categories land on this procedure. more

What this run cannot claim

These breaks are shown together on one unit so the shape of a bad day fits on one screen. more

Two clocks run. Worked time is the sum of the time the work is actually being done … more

Live observability

Systems this service would touch

Attributed by rule from the function's system list. more

2 systems attributed

0 of 2 returning records

The system register

Enterprise Data Warehouse

Snowflake · analytics · inbound · critical

modeled

5 of 6 stations attributed here · read only

Group ERP — Financials

SAP S/4HANA · ledger · bidirectional · critical

modeled

1 of 6 stations attributed here · would write back

System attribution is a rule, not a reading. more

Who runs it

Orchestration and accountability

Orchestrated by: Automation Factory Orchestrator
That orchestrator’s remit: Owns automation work end to end inside AI GBS & Global Business Services. Runs 4 lines across 26 stations, drains the repeatable share into the AI-OPS tower, and holds 4 human gates.
Accountable person: Head of Automation
Sub-function: Automation Factory
Shared spine tower: Not on the shared spine
Hand-over points: None — this service stays inside its function

Other services in this sub-function

3 alongside this one

Idea to ProductionGB7A Regression ResponseGB7B Portfolio RebalanceGB7C

What this page is and is not

This is a catalogue of the modeled estate. more