LensReading which lens this session carries.
The catalogueHuman ResourcesTalent MobilityAnalytical

Service HR7C

Succession Slate Refresh

Runs analytical. Starts when a leader asks the question. It runs 76 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

76

46 in flight right now.

Stations

5

1 person · 4 agent · 0 spine

Agent share of steps

80%

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

Decisions a person makes

1

Held by Director, Global Mobility.

Touchless

40%

Share of runs that complete without anybody opening them.

Timetable against actual

99.1h

Actual 92.9h, 6.2h under the timetable.

Operations

The lane diagram

Read it left to right.

Person1 station and 25% of the dwellAgent4 stations and 75% 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
Core HR and Payroll
Recruiting and Applicant Tracking
Workforce Management
Core HR and Payroll
Core HR and Payroll
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

Scan roles

AgentInternal Opportunity Match Agentworkflow3h 42m7h 18m7Core HR and Payroll
2

Score bench

AgentSuccession Slate Agentworkflow9h 12m12h 15m19Recruiting and Applicant Tracking
3

Draft slates

AgentAssignment Structuring Agentworkflow7h 48m10h 55m9Workforce Management
4

Leader review

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

HumanDirector, Global Mobilitypolicy8h 2m9h 51m2Core HR and Payroll
5

Lock

AgentRelocation Coordination Agentworkflow3h 33m4h 48m9Core HR and Payroll

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%
76 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 gates18 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
610.5h
76 items at 482 minutes of decision each.
Agent time a week
1,843h
1,455 minutes an item, which does not compete for a person.
Gate load
97%
Inside capacity, with 19.5h of headroom.
Stations without a person
80%
1 gate left on 5 stations.
Where an item spends its time
25% waiting on a person
75% in the agent lane
An item now takes 1,937 minutes of worked time end to end against 1,937 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 Succession Slate Refresh

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

now Scan roles · Internal Opportunity Match Agent · 3.7 hrs

As the ledger has it

the same stations, plus 3 categories the estate already counts

0 min of 37 hrs

now Scan roles · Internal Opportunity Match Agent · 3.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.

3 systems attributed

0 of 3 returning records

Core HR and Payroll

Workday HCM · hcm · bidirectional · critical

modeled

3 of 5 stations attributed here · would write back

Recruiting and Applicant Tracking

Greenhouse · hcm · inbound · medium

modeled

1 of 5 stations attributed here · read only

Workforce Management

NICE WFM · service · 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
Mobility Orchestrator
That orchestrator’s remit
Owns assignment work end to end inside Human Resources. Runs 3 lines across 19 stations, drains the repeatable share into the H2R tower, and holds 5 human gates.
Accountable person
Director, Global Mobility
Sub-function
Talent Mobility
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

What this page is and is not

This is a catalogue of the modeled estate.