Service SL10A
Seller Ramp
Runs transactional. Starts when an upstream system posts an event. It runs 367 times a week across 4 stations. One of those stations stops for a person and 3 are done by an agent, 1 of them on the shared spine.
Runs a week
367
98 in flight right now.
Stations
4
1 person · 2 agent · 1 spine
Agent share of steps
75%
Autonomy on this service is set at 75% against a ceiling of 84%.
Decisions a person makes
1
Held by Director, Sales Enablement.
Touchless
78%
Share of runs that complete without anybody opening them.
Timetable against actual
3.0h
Actual 2.6h, 0.4h under 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 | Assign path Hands over at human-resources | GBS | Enablement Orchestrator | gbs | 2h 20m | 2h 50m | 43 | Customer Relationship Management |
| 2 | Track milestones | Agent | Content Assembly Agent | workflow | 2h 22m | 3h 47m | 23 | Customer Relationship Management |
| 3 | Certify Held for a named human when the unit exceeds the enablement asset decision envelope, when confidence falls below the floor, or when a policy clause is engaged. | Human | Director, Sales Enablement | policy | 1h 36m | 1h 53m | 5 | Contract Lifecycle Management |
| 4 | Measure ramp | Agent | Call Coaching Agent | workflow | 1h 27m | 2h 56m | 27 | Contract Lifecycle 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
4 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
4 stations, nothing waiting, nothing sent back
0 min of 7.8 hrs
now Assign path · Enablement Orchestrator · 2.3 hrs
As the ledger has it
the same stations, plus 4 categories the estate already counts
0 min of 23 hrs
now Assign path · Enablement Orchestrator · 2.3 hrs
What breaks, and where it is counted
No break below was chosen. more
What the two runs say together
4 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
The separation register records a duty conflict against a sub-function and a named post, not against one procedure. 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 4 stations attributed here · would write back
Contract Lifecycle Management
Icertis · legal · bidirectional · high
2 of 4 stations attributed here · would write back
System attribution is a rule, not a reading. more
Who runs it
Orchestration and accountability
- Orchestrated by
- Enablement Orchestrator
- That orchestrator’s remit
- Owns enablement asset work end to end inside Sales. Runs 3 lines across 14 stations, drains the repeatable share into no shared tower, and holds 3 human gates.
- Accountable person
- Director, Sales Enablement
- Sub-function
- Sales Enablement
- Shared spine tower
- Not on the shared spine
- Hand-over points
- human-resources
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