LensReading which lens this session carries.
The catalogueRevenue Growth ManagementRevenue AnalyticsTransactional

Service RO11B

Board Pack Build

Runs transactional. Starts when a request lands in the queue. It runs 6,676 times a week across 6 stations. 2 of those stations stop for a person and 4 are done by an agent, 1 of them on the shared spine.

Runs a week

6,676

105 in flight right now.

Stations

6

2 person · 3 agent · 1 spine

Agent share of steps

67%

Autonomy on this service is set at 64% against a ceiling of 78%.

Decisions a person makes

2

Held by VP Revenue Analytics.

Touchless

72%

Share of runs that complete without anybody opening them.

Timetable against actual

19.0h

Actual 21.2h, 2.2h over the timetable.

Operations

The lane diagram

Read it left to right.

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

Assemble

GBSCohort Analysis Agentgbs1h 18m2h 21m15Customer Relationship Management
2

Fact check

AgentFunnel Diagnostic Agentworkflow26m31m28Customer Relationship Management
3

Draft narrative

AgentRetention Modeling Agentworkflow8m15m29Enterprise Data Warehouse
4

Finance review

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

Hands over at finance

HumanVP Revenue Analyticspolicy1h 30m2h 13m2Customer Relationship Management
5

Revenue chief sign

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

HumanVP Revenue Analyticspolicy5h 39m8h 20m0Customer Relationship Management
6

Deliver

AgentRevenue Architecture Agentworkflow10m22m31Configure, Price and Quote

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%
6,676 a week is what the estate records.
Decisions handed to agents0 of 2
Cheapest decision first. The last gate never moves: something on this service always ends with a person.
People on the gates1364 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
47,733.4h
6,676 items at 429 minutes of decision each.
Agent time a week
13,574.5h
122 minutes an item, which does not compete for a person.
Gate load
100%
Inside capacity, with 6.6h of headroom.
Stations without a person
67%
2 gates left on 6 stations.
Where an item spends its time
78% waiting on a person
22% in the agent lane
An item now takes 551 minutes of worked time end to end against 551 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 Board Pack Build

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

now Assemble · Cohort Analysis Agent · 1.3 hrs

As the ledger has it

the same stations, plus 5 categories the estate already counts

0 min of 33 hrs

now Assemble · Cohort Analysis Agent · 1.3 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

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.

3 systems attributed

0 of 3 returning records

The system register

Customer Relationship Management

Salesforce Sales Cloud · crm · bidirectional · critical

modeled

4 of 6 stations attributed here · would write back

Enterprise Data Warehouse

Snowflake · analytics · inbound · critical

modeled

1 of 6 stations attributed here · read only

Configure, Price and Quote

Salesforce CPQ · crm · inbound · high

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
Revenue Analytics Orchestrator
That orchestrator’s remit
Owns analysis work end to end inside Revenue Growth Management. Runs 3 lines across 17 stations, drains the repeatable share into the DATA-ANALYTICS tower, and holds 4 human gates.
Accountable person
VP Revenue Analytics
Sub-function
Revenue Analytics
Shared spine tower
data-analytics
Hand-over points
finance

Other services in this sub-function

2 alongside this one

Monthly Revenue ReadRO11ARevenue Architecture PositionRO11C

What this page is and is not

This is a catalogue of the modeled estate.