Service RO9C
Accuracy Scorecard
Runs analytical. Starts when a drift signal breaches tolerance. It runs 27 times a week across 3 stations. No station stops for a person and 3 are done by an agent, 1 of them on the shared spine.
Runs a week
27
52 in flight right now.
Stations
3
0 person · 2 agent · 1 spine
Agent share of steps
100%
Autonomy on this service is set at 64% against a ceiling of 86%.
Decisions a person makes
0
Nothing on this service waits for a person.
Touchless
67%
Share of runs that complete without anybody opening them.
Timetable against actual
122.0h
Actual 148.7h, 26.7h over the timetable.
Operations
The lane diagram
Read it left to right. more
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.
| # | Station | Lane | Who | Layer | Dwell | Target | In flight | System |
|---|---|---|---|---|---|---|---|---|
| 1 | Aggregate history | Agent | Submission Compliance Agent | workflow | 9h 32m | 14h 37m | 1 | Customer Relationship Management |
| 2 | Rank | Agent | Model vs Commit Agent | workflow | 2h 24m | 3h 31m | 46 | Enterprise Data Warehouse |
| 3 | Publish | GBS | Submission Compliance Agent | gbs | 5h 19m | 7h 24m | 5 | Customer 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. more
The simulation is arithmetic on the estate, not a queueing model. more
How it runs
Run it again, going wrong
The same unit and the same stations, broken the way the estate already records breaking. more
3 stations, walked twice
Once clean, once with the categories the estate counts
This is the same unit on the same stations, breaking. more
No break below was chosen. more
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
3 stations, nothing waiting, nothing sent back
0 min of 17 hrs
now Aggregate history · Submission Compliance Agent · 9.5 hrs
As the ledger has it
the same stations, plus 2 categories the estate already counts
0 min of 19 hrs
now Aggregate history · Submission Compliance Agent · 9.5 hrs
What breaks, and where it is counted
No break below was chosen. more
What the two runs say together
2 counted categories land on this procedure. more
What this run cannot claim
These breaks are shown together on one unit so the shape of a bad day fits on one screen. more
Two clocks run. Worked time is the sum of the time the work is actually being done … more
Live observability
Systems this service would touch
Attributed by rule from the function's system list. more
2 systems attributed
0 of 2 returning records
Customer Relationship Management
Salesforce Sales Cloud · crm · bidirectional · critical
2 of 3 stations attributed here · would write back
Enterprise Data Warehouse
Snowflake · analytics · inbound · critical
1 of 3 stations attributed here · read only
System attribution is a rule, not a reading. more
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
- p2p
- 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. more