LensReading which lens this session carries.
The catalogueRevenue Growth ManagementCRM Data StewardshipTransactional

Service RO1B

Account Hierarchy Rebuild

Runs transactional. Starts when an upstream system posts an event. It runs 7,975 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

7,975

109 in flight right now.

Stations

5

1 person · 3 agent · 1 spine

Agent share of steps

80%

Autonomy on this service is set at 83% against a ceiling of 92%.

Decisions a person makes

1

Held by Director, Revenue Data.

Touchless

85%

Share of runs that complete without anybody opening them.

Timetable against actual

7.7h

Actual 8.9h, 1.2h over the timetable.

Operations

The lane diagram

Read it left to right.

Person1 station and 41% of the dwellAgent3 stations and 40% of the dwellShared spine1 station and 18% of the dwell2 crossings between lanes
Human
decides
Agent
does the work
GBS
shared spine
System
attributed by rule
Customer Relationship Management
Enterprise Data Warehouse
Configure, Price and Quote
Customer Relationship Management
Customer Relationship Management
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

Detect change

AgentDuplicate Detection Agentworkflow28m48m9Customer Relationship Management
2

Model hierarchy

AgentEnrichment Agentworkflow2h 57m5h 17m43Enterprise Data Warehouse
3

Territory impact

Hands over at sales

AgentHierarchy Resolution Agentworkflow2h 53m3h 30m21Configure, Price and Quote
4

Approve

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

HumanDirector, Revenue Datapolicy6h 30m14h 13m7Customer Relationship Management
5

Apply

GBSField Completeness Agentgbs2h 54m4h 11m29Customer Relationship Management

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%
7,975 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 gates1482 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
51,837.5h
7,975 items at 390 minutes of decision each.
Agent time a week
73,370h
552 minutes an item, which does not compete for a person.
Gate load
100%
Inside capacity, with 32.5h of headroom.
Stations without a person
80%
1 gate left on 5 stations.
Where an item spends its time
41% waiting on a person
59% in the agent lane
An item now takes 942 minutes of worked time end to end against 942 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 Account Hierarchy Rebuild

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 16 hrs

now Detect change · Duplicate Detection Agent · 28 min

As the ledger has it

the same stations, plus 3 categories the estate already counts

0 min of 21 hrs

now Detect change · Duplicate Detection Agent · 28 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

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.

3 systems attributed

0 of 3 returning records

The system register

Customer Relationship Management

Salesforce Sales Cloud · crm · 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

Configure, Price and Quote

Salesforce CPQ · crm · inbound · high

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
Data Stewardship Orchestrator
That orchestrator’s remit
Owns record work end to end inside Revenue Growth Management. Runs 3 lines across 15 stations, drains the repeatable share into the O2C tower, and holds 3 human gates.
Accountable person
Director, Revenue Data
Sub-function
CRM Data Stewardship
Shared spine tower
o2c
Hand-over points
sales

Other services in this sub-function

2 alongside this one

Continuous HygieneRO1AData Quality ReportRO1C

What this page is and is not

This is a catalogue of the modeled estate.