The catalogue AI GBS & Global Business ServicesGlobal Process OwnershipAnalytical

Service GB6B

Control Design Review

Runs analytical. Starts when the reporting period closes. It runs 18 times a week across 5 stations. One of those stations stops for a person and 4 are done by an agent, 1 of them on the shared spine.

Runs a week

84 in flight right now.

Stations

1 person · 3 agent · 1 spine

Agent share of steps

80%

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

Decisions a person makes

Held by Global Process Owner.

Touchless

43%

Share of runs that complete without anybody opening them.

Timetable against actual

42.6h

Actual 34.6h, 8.0h under the timetable.

Operations

The lane diagram

Read it left to right. more

Person1 station and 33% of the dwellAgent3 stations and 53% of the dwellShared spine1 station and 14% of the dwell2 crossings between lanes

Human

decides

Agent

does the work

GBS

shared spine

System

attributed by rule

Enterprise Data Warehouse

Group ERP — Financials

Core HR and Payroll

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	Map risks	Agent	Process Model Agent	workflow	12h 52m	16h 22m	27	Enterprise Data Warehouse
2	Design controls	Agent	Variant Detection Agent	workflow	7h 25m	13h 49m	43	Group ERP — Financials
3	Test design	Agent	Standardization Agent	workflow	6h 25m	14h 50m	12	Core HR and Payroll
4	Approve 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.	Human	Global Process Owner	policy	16h 50m	23h 54m	0	Group ERP — Financials
5	Embed	GBS	Control Design Agent	gbs	7h 15m	16h 53m	2	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%

18 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 gates9 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

303h

18 items at 1,010 minutes of decision each.

Agent time a week

611.1h

2,037 minutes an item, which does not compete for a person.

Gate load

96%

Inside capacity, with 12h of headroom.

Stations without a person

80%

1 gate left on 5 stations.

Where an item spends its time

33% waiting on a person

67% in the agent lane

An item now takes 3,047 minutes of worked time end to end against 3,047 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 Control Design Review

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

5 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

5 stations, nothing waiting, nothing sent back

0 min of 2.1 days

now Map risks · Process Model Agent · 13 hrs

As the ledger has it

the same stations, plus 2 categories the estate already counts

0 min of 2.2 days

now Map risks · Process Model Agent · 13 hrs

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

3 systems attributed

0 of 3 returning records

The system register

Group ERP — Financials

SAP S/4HANA · ledger · bidirectional · critical

modeled

3 of 5 stations attributed here · would write back

Enterprise Data Warehouse

Snowflake · analytics · inbound · critical

modeled

1 of 5 stations attributed here · read only

Core HR and Payroll

Workday HCM · hcm · bidirectional · critical

modeled

1 of 5 stations attributed here · would write back

System attribution is a rule, not a reading. more

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

Variant to StandardGB6A Global Process Design PositionGB6C

What this page is and is not

This is a catalogue of the modeled estate. more