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

Service RO1A

Continuous Hygiene

Runs transactional. Starts when a request lands in the queue. It runs 3,968 times a week across 6 stations. One of those stations stops for a person and 5 are done by an agent, 3 of them on the shared spine.

Runs a week

3,968

186 in flight right now.

Stations

6

1 person · 2 agent · 3 spine

Agent share of steps

83%

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

Decisions a person makes

1

Held by Director, Revenue Data.

Touchless

96%

Share of runs that complete without anybody opening them.

Timetable against actual

18.7h

Actual 20.3h, 1.6h over the timetable.

Operations

The lane diagram

Read it left to right.

Person1 station and 46% of the dwellAgent2 stations and 17% of the dwellShared spine3 stations and 37% of the dwell4 crossings between lanes
Human
decides
Agent
does the work
GBS
shared spine
System
attributed by rule
Customer Relationship Management
Customer Relationship Management
Customer Relationship Management
Customer Relationship Management
Customer Relationship Management
Enterprise Data Warehouse
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

Scan

GBSField Completeness Agentgbs2h 26m5h 41m28Customer Relationship Management
2

Detect defect

AgentEnrichment Agentworkflow54m1h 56m36Customer Relationship Management
3

Auto-merge

GBSField Completeness Agentgbs2h 14m5h 19m42Customer Relationship Management
4

Auto-enrich

GBSField Completeness Agentgbs1h 17m1h 32m41Customer Relationship Management
5

Steward review

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 Datapolicy7h 22m15h 24m5Customer Relationship Management
6

Close

AgentData Policy Agentworkflow1h 55m3h 30m34Enterprise Data Warehouse

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%
3,968 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 gates836 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
29,230.9h
3,968 items at 442 minutes of decision each.
Agent time a week
34,786.1h
526 minutes an item, which does not compete for a person.
Gate load
100%
Inside capacity, with 29.1h of headroom.
Stations without a person
83%
1 gate left on 6 stations.
Where an item spends its time
46% waiting on a person
54% in the agent lane
An item now takes 968 minutes of worked time end to end against 968 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 Continuous Hygiene

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.

6 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

6 stations, nothing waiting, nothing sent back

0 min of 16 hrs

now Scan · Field Completeness Agent · 2.4 hrs

As the ledger has it

the same stations, plus 4 categories the estate already counts

0 min of 31 hrs

now Scan · Field Completeness Agent · 2.4 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

4 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

The system register

Customer Relationship Management

Salesforce Sales Cloud · crm · bidirectional · critical

modeled

5 of 6 stations attributed here · would write back

Enterprise Data Warehouse

Snowflake · analytics · inbound · critical

modeled

1 of 6 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
None — this service stays inside its function

Other services in this sub-function

2 alongside this one

Account Hierarchy RebuildRO1BData Quality ReportRO1C

What this page is and is not

This is a catalogue of the modeled estate.