LensReading which lens this session carries.
The catalogueEngineeringTest & AssuranceTransactional

Service EN5C

Performance Baseline

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

Runs a week

7,697

49 in flight right now.

Stations

4

1 person · 0 agent · 3 spine

Agent share of steps

75%

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

Decisions a person makes

1

Held by Director, Quality Engineering.

Touchless

93%

Share of runs that complete without anybody opening them.

Timetable against actual

9.1h

Actual 8.6h, 0.5h under the timetable.

Operations

The lane diagram

Read it left to right.

Person1 station and 29% of the dwellAgent0 stations and 0% of the dwellShared spine3 stations and 71% of the dwell2 crossings 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
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

Run load

GBSTest Generation Agentgbs40m1h 24m28Group ERP — Materials and Inventory
2

Compare baseline

GBSTest Generation Agentgbs1h 49m4h 13m9Group ERP — Materials and Inventory
3

Flag regression

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

HumanDirector, Quality Engineeringpolicy1h 58m3h 18m6Group ERP — Materials and Inventory
4

File issue

GBSTest Generation Agentgbs2h 18m3h 41m6Group 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,697 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 gates433 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
15,137.4h
7,697 items at 118 minutes of decision each.
Agent time a week
36,817.3h
287 minutes an item, which does not compete for a person.
Gate load
100%
Inside capacity, with 17.6h of headroom.
Stations without a person
75%
1 gate left on 4 stations.
Where an item spends its time
29% waiting on a person
71% in the agent lane
An item now takes 405 minutes of worked time end to end against 405 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 Performance Baseline

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 Run load · Test Generation Agent · 40 min

As the ledger has it

the same stations, plus 3 categories the estate already counts

0 min of 12 hrs

now Run load · Test Generation Agent · 40 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

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

4 of 4 stations attributed here · would write back

System attribution is a rule, not a reading.

Who runs it

Orchestration and accountability

Orchestrated by
Test Orchestrator
That orchestrator’s remit
Owns test run work end to end inside Engineering. Runs 3 lines across 15 stations, drains the repeatable share into the C2L tower, and holds 3 human gates.
Accountable person
Director, Quality Engineering
Sub-function
Test & Assurance
Shared spine tower
c2l
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.