LensReading which lens this session carries.
The catalogueEngineeringCode Review & QualityTransactional

Service EN4C

Convention Change

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

Runs a week

2,432

34 in flight right now.

Stations

4

2 person · 1 agent · 1 spine

Agent share of steps

50%

Autonomy on this service is set at 82% against a ceiling of 88%.

Decisions a person makes

2

Held by Director, Engineering Quality.

Touchless

86%

Share of runs that complete without anybody opening them.

Timetable against actual

21.5h

Actual 16.2h, 5.3h under the timetable.

Operations

The lane diagram

Read it left to right.

Person2 stations and 79% of the dwellAgent1 station and 7% of the dwellShared spine1 station and 13% of the dwell2 crossings between lanes
Human
decides
Agent
does the work
GBS
shared spine
System
attributed by rule
Configuration Management Database
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

Propose

AgentStatic Analysis Agentworkflow30m1h 3m19Configuration Management Database
2

Team review

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

HumanDirector, Engineering Qualitypolicy4h 47m8h 41m8Group ERP — Materials and Inventory
3

Ratify

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

HumanDirector, Engineering Qualitypolicy36m1h 5m4Group ERP — Materials and Inventory
4

Enforce

GBSComplexity Monitorgbs54m1h 42m3Group 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%
2,432 a week is what the estate records.
Decisions handed to agents0 of 2
Cheapest decision first. The last gate never moves: something on this service always ends with a person.
People on the gates375 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
13,092.3h
2,432 items at 323 minutes of decision each.
Agent time a week
3,404.8h
84 minutes an item, which does not compete for a person.
Gate load
100%
Inside capacity, with 32.7h of headroom.
Stations without a person
50%
2 gates left on 4 stations.
Where an item spends its time
79% waiting on a person
21% in the agent lane
An item now takes 407 minutes of worked time end to end against 407 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 Convention Change

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.

4 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

4 stations, nothing waiting, nothing sent back

0 min of 6.8 hrs

now Propose · Static Analysis Agent · 30 min

As the ledger has it

the same stations, plus 4 categories the estate already counts

0 min of 26 hrs

now Propose · Static Analysis Agent · 30 min

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

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

2 systems attributed

0 of 2 returning records

The system register

Group ERP — Materials and Inventory

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

modeled

3 of 4 stations attributed here · would write back

Configuration Management Database

ServiceNow CMDB · itsm · inbound · high

modeled

1 of 4 stations attributed here · read only

System attribution is a rule, not a reading.

Who runs it

Orchestration and accountability

Orchestrated by
Code Quality Orchestrator
That orchestrator’s remit
Owns pull request work end to end inside Engineering. Runs 3 lines across 14 stations, drains the repeatable share into no shared tower, and holds 5 human gates.
Accountable person
Director, Engineering Quality
Sub-function
Code Review & Quality
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

Pull Request ReviewEN4AQuality Debt SweepEN4B

What this page is and is not

This is a catalogue of the modeled estate.