LensReading which lens this session carries.
The catalogueEngineeringPortfolio & IntakeAnalytical

Service EN1B

Capacity Rebalance

Runs analytical. Starts when a leader asks the question. It runs 73 times a week across 4 stations. One of those stations stops for a person and 3 are done by an agent, none of them on the shared spine.

Runs a week

73

54 in flight right now.

Stations

4

1 person · 3 agent · 0 spine

Agent share of steps

75%

Autonomy on this service is set at 67% against a ceiling of 74%.

Decisions a person makes

1

Held by VP Engineering Operations.

Touchless

47%

Share of runs that complete without anybody opening them.

Timetable against actual

135.6h

Actual 131.7h, 3.9h under the timetable.

Operations

The lane diagram

Read it left to right.

Person1 station and 43% of the dwellAgent3 stations and 57% 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
Configuration Management Database
Group ERP — Materials and Inventory
Product Lifecycle Management
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

Model demand

AgentRequest Triage Agentworkflow13h 57m18h 41m8Configuration Management Database
2

Model capacity

AgentEffort Estimation Agentworkflow2h 44m3h 46m3Group ERP — Materials and Inventory
3

Draft recommendation

AgentDependency Mapping Agentworkflow10h 49m16h 21m38Product Lifecycle Management
4

Leader review

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

HumanVP Engineering Operationspolicy20h 43m32h 21m5Group 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%
73 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 gates44 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
1,512.3h
73 items at 1,243 minutes of decision each.
Agent time a week
2,007.5h
1,650 minutes an item, which does not compete for a person.
Gate load
98%
Inside capacity, with 27.7h of headroom.
Stations without a person
75%
1 gate left on 4 stations.
Where an item spends its time
43% waiting on a person
57% in the agent lane
An item now takes 2,893 minutes of worked time end to end against 2,893 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 Capacity Rebalance

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

now Model demand · Request Triage Agent · 14 hrs

As the ledger has it

the same stations, plus 2 categories the estate already counts

0 min of 2.1 days

now Model demand · Request Triage Agent · 14 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

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

3 systems attributed

0 of 3 returning records

The system register

Group ERP — Materials and Inventory

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

modeled

2 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

Product Lifecycle Management

Siemens Teamcenter · engineering · 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
Engineering Intake Orchestrator
That orchestrator’s remit
Owns request work end to end inside Engineering. Runs 3 lines across 16 stations, drains the repeatable share into the C2L tower, and holds 4 human gates.
Accountable person
VP Engineering Operations
Sub-function
Portfolio & Intake
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

Intake-to-BacklogEN1AInvestment PositionEN1C

What this page is and is not

This is a catalogue of the modeled estate.