LensReading which lens this session carries.
The catalogueEngineeringBuildTransactional

Service EN3A

Feature Build

Runs transactional. Starts when a request lands in the queue. It runs 1,610 times a week across 6 stations. 2 of those stations stop for a person and 4 are done by an agent, 3 of them on the shared spine.

Runs a week

1,610

95 in flight right now.

Stations

6

2 person · 1 agent · 3 spine

Agent share of steps

67%

Autonomy on this service is set at 76% against a ceiling of 86%.

Decisions a person makes

2

Held by Director, Platform Engineering.

Touchless

81%

Share of runs that complete without anybody opening them.

Timetable against actual

18.7h

Actual 24.5h, 5.8h over the timetable.

Operations

The lane diagram

Read it left to right.

Person2 stations and 46% of the dwellAgent1 station and 21% of the dwellShared spine3 stations and 34% 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
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

Refine specification

AgentSpecification Agentworkflow2h 35m3h 24m43Configuration Management Database
2

Generate code

GBSSpecification Agentgbs1h 38m1h 56m26Group ERP — Materials and Inventory
3

Self-test

GBSCode Generation Agentgbs1h 34m2h 46m22Group ERP — Materials and Inventory
4

Open pull request

GBSScaffold Agentgbs58m1h 20m0Group ERP — Materials and Inventory
5

Human 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, Platform Engineeringpolicy1h 43m3h 59m0Group ERP — Materials and Inventory
6

Merge

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, Platform Engineeringpolicy3h 58m7h 3m4Group 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%
1,610 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 gates262 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
9,150.2h
1,610 items at 341 minutes of decision each.
Agent time a week
10,867.5h
405 minutes an item, which does not compete for a person.
Gate load
100%
Inside capacity, with 19.8h of headroom.
Stations without a person
67%
2 gates left on 6 stations.
Where an item spends its time
46% waiting on a person
54% in the agent lane
An item now takes 746 minutes of worked time end to end against 746 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 Feature Build

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

now Refine specification · Specification Agent · 2.6 hrs

As the ledger has it

the same stations, plus 5 categories the estate already counts

0 min of 41 hrs

now Refine specification · Specification Agent · 2.6 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

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