LensReading which lens this session carries.
The catalogueAI GBS & Global Business ServicesMaster Data ManagementTransactional

Service GB8C

Hierarchy Change

Runs transactional. Starts when a threshold is crossed. It runs 746 times a week across 5 stations. One of those stations stops for a person and 4 are done by an agent, 3 of them on the shared spine.

Runs a week

746

41 in flight right now.

Stations

5

1 person · 1 agent · 3 spine

Agent share of steps

80%

Autonomy on this service is set at 79% against a ceiling of 87%.

Decisions a person makes

1

Held by Head of Master Data.

Touchless

80%

Share of runs that complete without anybody opening them.

Timetable against actual

5.7h

Actual 4.9h, 0.8h under the timetable.

Operations

The lane diagram

Read it left to right.

Person1 station and 49% of the dwellAgent1 station and 2% of the dwellShared spine3 stations and 48% of the dwell3 crossings between lanes
Human
decides
Agent
does the work
GBS
shared spine
System
attributed by rule
Enterprise Data Warehouse
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

Propose

AgentData Quality Agentworkflow21m50m4Enterprise Data Warehouse
2

Impact assess

Hands over at finance

GBSHierarchy Agentgbs1h 37m3h 17m25Group ERP — Financials
3

Approve

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

HumanHead of Master Datapolicy7h 6m9h3Group ERP — Financials
4

Apply

GBSHierarchy Agentgbs3h5h 15m8Group ERP — Financials
5

Reconcile

GBSHierarchy Agentgbs2h 21m4h 51m1Group 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%
746 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 gates152 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
5,296.6h
746 items at 426 minutes of decision each.
Agent time a week
5,458.2h
439 minutes an item, which does not compete for a person.
Gate load
100%
Inside capacity, with 23.4h of headroom.
Stations without a person
80%
1 gate left on 5 stations.
Where an item spends its time
49% waiting on a person
51% in the agent lane
An item now takes 865 minutes of worked time end to end against 865 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 Hierarchy Change

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.

5 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

5 stations, nothing waiting, nothing sent back

0 min of 14 hrs

now Propose · Data Quality Agent · 21 min

As the ledger has it

the same stations, plus 5 categories the estate already counts

0 min of 28 hrs

now Propose · Data Quality Agent · 21 min

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

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

The separation register records a duty conflict against a sub-function and a named post, not against one procedure.

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

Group ERP — Financials

SAP S/4HANA · ledger · bidirectional · critical

modeled

4 of 5 stations attributed here · would write back

Enterprise Data Warehouse

Snowflake · analytics · inbound · critical

modeled

1 of 5 stations attributed here · read only

System attribution is a rule, not a reading.

Who runs it

Orchestration and accountability

Orchestrated by
Master Data Orchestrator
That orchestrator’s remit
Owns master record work end to end inside AI GBS & Global Business Services. Runs 3 lines across 17 stations, drains the repeatable share into the DATA-ANALYTICS tower, and holds 2 human gates.
Accountable person
Head of Master Data
Sub-function
Master Data Management
Shared spine tower
data-analytics
Hand-over points
finance

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.