LensReading which lens this session carries.
The catalogueEngineeringTechnical DebtTransactional

Service EN8A

Debt Remediation

Runs transactional. Starts when a scheduled window opens. It runs 7,727 times a week across 6 stations. One of those stations stops for a person and 5 are done by an agent, 3 of them on the shared spine.

Runs a week

7,727

169 in flight right now.

Stations

6

1 person · 2 agent · 3 spine

Agent share of steps

83%

Autonomy on this service is set at 71% against a ceiling of 84%.

Decisions a person makes

1

Held by Director, Engineering Effectiveness.

Touchless

78%

Share of runs that complete without anybody opening them.

Timetable against actual

17.8h

Actual 20.8h, 3.0h over the timetable.

Operations

The lane diagram

Read it left to right.

Person1 station and 40% of the dwellAgent2 stations and 7% of the dwellShared spine3 stations and 54% of the dwell3 crossings between lanes
Human
decides
Agent
does the work
GBS
shared spine
System
attributed by rule
Group ERP — Materials and Inventory
Configuration Management Database
Group ERP — Materials and Inventory
Group ERP — Materials and Inventory
Group ERP — Materials and Inventory
Group ERP — Materials and Inventory
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

GBSTechnical Debt Orchestratorgbs2h 22m3h 57m4Group ERP — Materials and Inventory
2

Score risk

AgentRisk Scoring Agentworkflow10m22m42Configuration Management Database
3

Plan remediation

AgentRemediation Planning Agentworkflow36m1h 21m40Group ERP — Materials and Inventory
4

Owner accept

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

HumanDirector, Engineering Effectivenesspolicy4h 22m9h 28m9Group ERP — Materials and Inventory
5

Execute

GBSMigration Agentgbs30m1h 10m28Group ERP — Materials and Inventory
6

Verify

GBSDeprecation Agentgbs3h 3m6h 55m46Group ERP — Materials and Inventory

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%
7,727 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 gates965 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
33,741.2h
7,727 items at 262 minutes of decision each.
Agent time a week
51,642.1h
401 minutes an item, which does not compete for a person.
Gate load
100%
Inside capacity, with 33.8h of headroom.
Stations without a person
83%
1 gate left on 6 stations.
Where an item spends its time
40% waiting on a person
60% in the agent lane
An item now takes 663 minutes of worked time end to end against 663 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 Debt 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.

6 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

6 stations, nothing waiting, nothing sent back

0 min of 11 hrs

now Detect · Technical Debt Orchestrator · 2.4 hrs

As the ledger has it

the same stations, plus 5 categories the estate already counts

0 min of 25 hrs

now Detect · Technical Debt Orchestrator · 2.4 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.

2 systems attributed

0 of 2 returning records

The system register

Group ERP — Materials and Inventory

SAP S/4HANA MM · supply · bidirectional · high

modeled

5 of 6 stations attributed here · would write back

Configuration Management Database

ServiceNow CMDB · itsm · inbound · high

modeled

1 of 6 stations attributed here · read only

System attribution is a rule, not a reading.

Who runs it

Orchestration and accountability

Orchestrated by
Technical Debt Orchestrator
That orchestrator’s remit
Owns debt item work end to end inside Engineering. Runs 3 lines across 16 stations, drains the repeatable share into no shared tower, and holds 3 human gates.
Accountable person
Director, Engineering Effectiveness
Sub-function
Technical Debt
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

Deprecation CampaignEN8BDebt Doctrine PositionEN8C

What this page is and is not

This is a catalogue of the modeled estate.