LensReading which lens this session carries.
The catalogueEngineeringTechnical DebtJudgment

Service EN8C

Debt Doctrine Position

Runs judgment. Starts when a break condition on a live position fires. It runs 4 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

4

100 in flight right now.

Stations

5

1 person · 4 agent · 0 spine

Agent share of steps

80%

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

Decisions a person makes

1

Held by Director, Engineering Effectiveness.

Touchless

49%

Share of runs that complete without anybody opening them.

Timetable against actual

268.4h

Actual 345.6h, 77.2h over the timetable.

Operations

The lane diagram

Read it left to right.

Person1 station and 56% of the dwellAgent4 stations and 44% 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
Group ERP — Materials and Inventory
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

Frame

AgentDebt Detection Agentstrategy10h 57m25h 30m9Group ERP — Materials and Inventory
2

Model cost of carry

AgentRisk Scoring Agentstrategy34h 52m46h19Group ERP — Materials and Inventory
3

Draft position

AgentRemediation Planning Agentstrategy48h 46m64h 41m44Group ERP — Materials and Inventory
4

Challenge

AgentMigration Agentstrategy38h 5m60h 29m24Group ERP — Materials and Inventory
5

Ratify

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 Effectivenesspolicy169h 27m388h 30m4Group 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%
4 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 gates20 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
677.8h
4 items at 10,167 minutes of decision each.
Agent time a week
530.7h
7,960 minutes an item, which does not compete for a person.
Gate load
97%
Inside capacity, with 22.2h of headroom.
Stations without a person
80%
1 gate left on 5 stations.
Where an item spends its time
56% waiting on a person
44% in the agent lane
An item now takes 18,127 minutes of worked time end to end against 18,127 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 Doctrine 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.

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 12.6 days

now Frame · Debt Detection Agent · 11 hrs

As the ledger has it

the same stations, plus 3 categories the estate already counts

0 min of 12.8 days

now Frame · Debt Detection Agent · 11 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.

1 systems attributed

0 of 1 returning records

Group ERP — Materials and Inventory

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

modeled

5 of 5 stations attributed here · would write back

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

What this page is and is not

This is a catalogue of the modeled estate.