LensReading which lens this session carries.
The catalogueHuman ResourcesHR AI-ITTransactional

Service HR11A

Data Quality Remediation

Runs transactional. Starts when an upstream system posts an event. It runs 5,555 times a week across 5 stations. One of those stations stops for a person and 4 are done by an agent, 1 of them on the shared spine.

Runs a week

5,555

115 in flight right now.

Stations

5

1 person · 3 agent · 1 spine

Agent share of steps

80%

Autonomy on this service is set at 66% against a ceiling of 74%.

Decisions a person makes

1

Held by Director, HR Technology.

Touchless

72%

Share of runs that complete without anybody opening them.

Timetable against actual

9.0h

Actual 10.3h, 1.3h over the timetable.

Operations

The lane diagram

Read it left to right.

Person1 station and 17% of the dwellAgent3 stations and 69% of the dwellShared spine1 station and 14% of the dwell3 crossings between lanes
Human
decides
Agent
does the work
GBS
shared spine
System
attributed by rule
Core HR and Payroll
Recruiting and Applicant Tracking
Core HR and Payroll
Core HR and Payroll
Workforce Management
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 defect

AgentHRIS Data Quality Agentworkflow1h 14m2h 30m26Core HR and Payroll
2

Classify

AgentIntegration Health Monitorworkflow1h 55m3h 3m17Recruiting and Applicant Tracking
3

Auto-fix

GBSIntegration Health Monitorgbs51m1h 21m37Core HR and Payroll
4

Steward review

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

HumanDirector, HR Technologypolicy1h 3m1h 25m8Core HR and Payroll
5

Close

AgentConfig Change Agentworkflow1h 8m1h 19m27Workforce 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.

Move something
Demand100%
5,555 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 gates167 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
5,832.8h
5,555 items at 63 minutes of decision each.
Agent time a week
28,515.7h
308 minutes an item, which does not compete for a person.
Gate load
100%
Inside capacity, with 12.3h of headroom.
Stations without a person
80%
1 gate left on 5 stations.
Where an item spends its time
17% waiting on a person
83% in the agent lane
An item now takes 371 minutes of worked time end to end against 371 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 Data Quality Remediation

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

now Detect defect · HRIS Data Quality Agent · 1.2 hrs

As the ledger has it

the same stations, plus 5 categories the estate already counts

0 min of 21 hrs

now Detect defect · HRIS Data Quality Agent · 1.2 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

5 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.

The separation register records a duty conflict against a sub-function and a named post, not against one procedure.

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
HR Tech Orchestrator
That orchestrator’s remit
Owns change work end to end inside Human Resources. Runs 3 lines across 19 stations, drains the repeatable share into the H2R tower, and holds 4 human gates.
Accountable person
Director, HR Technology
Sub-function
HR AI-IT
Shared spine tower
h2r
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.