LensReading which lens this session carries.
The catalogueRevenue Growth ManagementForecast IntegrityAnalytical

Service RO9B

Divergence Investigation

Runs analytical. Starts when the cycle calendar fires. It runs 85 times a week across 5 stations. One of those stations stops for a person and 4 are done by an agent, none of them on the shared spine.

Runs a week

85

134 in flight right now.

Stations

5

1 person · 4 agent · 0 spine

Agent share of steps

80%

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

Decisions a person makes

1

Held by VP Revenue Growth Management.

Touchless

62%

Share of runs that complete without anybody opening them.

Timetable against actual

93.2h

Actual 119.6h, 26.4h over the timetable.

Operations

The lane diagram

Read it left to right.

Person1 station and 11% of the dwellAgent4 stations and 89% of the dwellShared spine0 stations and 0% 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
Reporting Semantic Layer
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 divergence

AgentSubmission Compliance Agentworkflow9h 41m13h 29m35Customer Relationship Management
2

Assemble evidence

AgentModel vs Commit Agentworkflow7h 43m13h 28m39Enterprise Data Warehouse
3

Draft finding

AgentHistorical Accuracy Agentworkflow14h 55m27h 58m15Configure, Price and Quote
4

Leader review

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

HumanVP Revenue Growth Managementpolicy4h 52m6h 38m1Customer Relationship Management
5

Log

AgentCoverage Ratio Agentworkflow6h 9m10h 38m44Reporting Semantic Layer

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%
85 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 gates12 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
413.7h
85 items at 292 minutes of decision each.
Agent time a week
3,269.7h
2,308 minutes an item, which does not compete for a person.
Gate load
98%
Inside capacity, with 6.3h of headroom.
Stations without a person
80%
1 gate left on 5 stations.
Where an item spends its time
89% in the agent lane
An item now takes 2,600 minutes of worked time end to end against 2,600 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 Divergence Investigation

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

now Detect divergence · Submission Compliance Agent · 9.7 hrs

As the ledger has it

the same stations, plus 3 categories the estate already counts

0 min of 2.0 days

now Detect divergence · Submission Compliance Agent · 9.7 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

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.

4 systems attributed

0 of 4 returning records

The system register

Customer Relationship Management

Salesforce Sales Cloud · crm · bidirectional · critical

modeled

2 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

Reporting Semantic Layer

Power BI shared datasets · analytics · inbound · medium

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
Forecast Integrity Orchestrator
That orchestrator’s remit
Owns submission work end to end inside Revenue Growth Management. Runs 3 lines across 13 stations, drains the repeatable share into the P2P tower, and holds 2 human gates.
Accountable person
VP Revenue Growth Management
Sub-function
Forecast Integrity
Shared spine tower
Not on the shared spine
Hand-over points
None — this service stays inside its function

Other services in this sub-function

2 alongside this one

Weekly Integrity CheckRO9AAccuracy ScorecardRO9C

What this page is and is not

This is a catalogue of the modeled estate.