LensReading which lens this session carries.
The catalogueEngineeringArchitecture & DesignJudgment

Service EN2C

Architecture Strategy Position

Runs judgment. Starts when the annual doctrine review opens. It runs 2 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

2

110 in flight right now.

Stations

5

1 person · 4 agent · 0 spine

Agent share of steps

80%

Autonomy on this service is set at 66% against a ceiling of 70%.

Decisions a person makes

1

Held by Chief Architect.

Touchless

34%

Share of runs that complete without anybody opening them.

Timetable against actual

281.2h

Actual 306.4h, 25.2h over the timetable.

Operations

The lane diagram

Read it left to right.

Person1 station and 54% of the dwellAgent4 stations and 46% 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

AgentDesign Option Agentstrategy19h 20m39h 42m34Group ERP — Materials and Inventory
2

Model options

AgentPattern Compliance Agentstrategy10h 51m17h 54m24Group ERP — Materials and Inventory
3

Draft position

AgentNon-functional Requirements Agentstrategy13h 2m27h 26m31Group ERP — Materials and Inventory
4

Challenge

AgentCost Modeling Agentstrategy36h 32m47h16Group ERP — Materials and Inventory
5

CTO ratify

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

HumanChief Architectpolicy92h 15m200h 47m5Group 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 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 gates6 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
184.5h
2 items at 5,535 minutes of decision each.
Agent time a week
159.5h
4,785 minutes an item, which does not compete for a person.
Gate load
88%
Inside capacity, with 25.5h of headroom.
Stations without a person
80%
1 gate left on 5 stations.
Where an item spends its time
54% waiting on a person
46% in the agent lane
An item now takes 10,320 minutes of worked time end to end against 10,320 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 Architecture Strategy 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 7.2 days

now Frame · Design Option Agent · 19 hrs

As the ledger has it

the same stations, plus 3 categories the estate already counts

0 min of 7.4 days

now Frame · Design Option Agent · 19 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
Architecture Orchestrator
That orchestrator’s remit
Owns design decision work end to end inside Engineering. Runs 3 lines across 17 stations, drains the repeatable share into no shared tower, and holds 3 human gates.
Accountable person
Chief Architect
Sub-function
Architecture & Design
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.