LensReading which lens this session carries.
The catalogueHuman ResourcesStrategic Workforce PlanningJudgment

Service HR1C

Build-Buy-Borrow Position

Runs judgment. Starts when the annual doctrine review opens. It runs 1 times a week across 7 stations. One of those stations stops for a person and 6 are done by an agent, none of them on the shared spine.

Runs a week

1

216 in flight right now.

Stations

7

1 person · 6 agent · 0 spine

Agent share of steps

86%

Autonomy on this service is set at 38% against a ceiling of 62%.

Decisions a person makes

1

Held by VP Workforce Strategy.

Touchless

30%

Share of runs that complete without anybody opening them.

Timetable against actual

347.1h

Actual 335.7h, 11.4h under the timetable.

Operations

The lane diagram

Read it left to right.

Person1 station and 35% of the dwellAgent6 stations and 65% of the dwellShared spine0 stations and 0% of the dwell1 crossing between lanes
Human
decides
Agent
does the work
GBS
shared spine
System
attributed by rule
Core HR and Payroll
Core HR and Payroll
Core HR and Payroll
Core HR and Payroll
Core HR and Payroll
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

Frame question

AgentDemand Forecast Agentstrategy53h 42m103h 24m45Core HR and Payroll
2

Gather evidence

AgentSupply & Attrition Model Agentstrategy65h 21m79h 54m30Core HR and Payroll
3

Model options

AgentSkills Taxonomy Agentstrategy52h 23m115h 45m46Core HR and Payroll
4

Draft position

AgentBuild-Buy-Borrow Agentstrategy32h 18m57h 28m34Core HR and Payroll
5

Challenge

AgentHeadcount Scenario Agentstrategy26h 53m41h 41m13Core HR and Payroll
6

Revise

AgentLocation Strategy Agentstrategy62h 7m106h 38m41Core HR and Payroll
7

Ratify

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

HumanVP Workforce Strategypolicy161h 6m210h 35m7Core 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%
1 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 gates5 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
161.1h
1 items at 9,666 minutes of decision each.
Agent time a week
292.7h
17,564 minutes an item, which does not compete for a person.
Gate load
92%
Inside capacity, with 13.9h of headroom.
Stations without a person
86%
1 gate left on 7 stations.
Where an item spends its time
35% waiting on a person
65% in the agent lane
An item now takes 27,230 minutes of worked time end to end against 27,230 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 Build-Buy-Borrow Position

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.

7 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

7 stations, nothing waiting, nothing sent back

0 min of 18.9 days

now Frame question · Demand Forecast Agent · 2.2 days

As the ledger has it

the same stations, plus 3 categories the estate already counts

0 min of 19.1 days

now Frame question · Demand Forecast Agent · 2.2 days

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.

1 systems attributed

0 of 1 returning records

Core HR and Payroll

Workday HCM · hcm · bidirectional · critical

modeled

7 of 7 stations attributed here · would write back

System attribution is a rule, not a reading.

Who runs it

Orchestration and accountability

Orchestrated by
Workforce Planning Orchestrator
That orchestrator’s remit
Owns plan scenario work end to end inside Human Resources. Runs 3 lines across 22 stations, drains the repeatable share into the P2P tower, and holds 3 human gates.
Accountable person
VP Workforce Strategy
Sub-function
Strategic Workforce Planning
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.