LensReading which lens this session carries.
The catalogueRevenue Growth ManagementRevenue Recognition InterlockTransactional

Service RO6B

Modification Handling

Runs transactional. Starts when a scheduled window opens. It runs 8,025 times a week across 5 stations. One of those stations stops for a person and 4 are done by an agent, 2 of them on the shared spine.

Runs a week

8,025

127 in flight right now.

Stations

5

1 person · 2 agent · 2 spine

Agent share of steps

80%

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

Decisions a person makes

1

Held by Director, Revenue Accounting.

Touchless

67%

Share of runs that complete without anybody opening them.

Timetable against actual

25.3h

Actual 20.4h, 4.9h under the timetable.

Operations

The lane diagram

Read it left to right.

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

AgentPerformance Obligation Agentworkflow3h 9m5h 43m18Customer Relationship Management
2

Reassess obligations

AgentAllocation Agentworkflow2h 19m2h 57m42Enterprise Data Warehouse
3

Recalculate

GBSPerformance Obligation Agentgbs1h 24m2h 28m45Customer Relationship Management
4

Controller approve

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

HumanDirector, Revenue Accountingpolicy3h 41m6h 2m3Customer Relationship Management
5

Repost

GBSPerformance Obligation Agentgbs1h 15m2h 57m19Customer 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%
8,025 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 gates845 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,558.8h
8,025 items at 221 minutes of decision each.
Agent time a week
65,136.3h
487 minutes an item, which does not compete for a person.
Gate load
100%
Inside capacity, with 16.3h of headroom.
Stations without a person
80%
1 gate left on 5 stations.
Where an item spends its time
31% waiting on a person
69% in the agent lane
An item now takes 708 minutes of worked time end to end against 708 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 Modification Handling

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

now Detect modification · Performance Obligation Agent · 3.1 hrs

As the ledger has it

the same stations, plus 4 categories the estate already counts

0 min of 27 hrs

now Detect modification · Performance Obligation Agent · 3.1 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

Customer Relationship Management

Salesforce Sales Cloud · crm · 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
Revenue Recognition Orchestrator
That orchestrator’s remit
Owns revenue schedule work end to end inside Revenue Growth Management. Runs 3 lines across 15 stations, drains the repeatable share into the R2R tower, and holds 3 human gates.
Accountable person
Director, Revenue Accounting
Sub-function
Revenue Recognition Interlock
Shared spine tower
r2r
Hand-over points
None — this service stays inside its function

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.