LensReading which lens this session carries.
The catalogueEngineeringSite ReliabilityTransactional

Service EN7C

Capacity Response

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

Runs a week

5,263

18 in flight right now.

Stations

4

1 person · 1 agent · 2 spine

Agent share of steps

75%

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

Decisions a person makes

1

Held by Director, Site Reliability.

Touchless

85%

Share of runs that complete without anybody opening them.

Timetable against actual

23.6h

Actual 20.6h, 3.0h under the timetable.

Operations

The lane diagram

Read it left to right.

Person1 station and 35% of the dwellAgent1 station and 8% of the dwellShared spine2 stations and 57% 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
Configuration Management Database
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

Forecast

GBSAlert Correlation Agentgbs1h1h 25m2Group ERP — Materials and Inventory
2

Scale in-policy

GBSAlert Correlation Agentgbs38m47m11Group ERP — Materials and Inventory
3

Escalate cost

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

HumanDirector, Site Reliabilitypolicy1h 1m1h 44m2Group ERP — Materials and Inventory
4

Apply

AgentCapacity Agentworkflow14m33m3Configuration Management Database

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%
5,263 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 gates153 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
5,350.7h
5,263 items at 61 minutes of decision each.
Agent time a week
9,824.3h
112 minutes an item, which does not compete for a person.
Gate load
100%
Inside capacity, with 4.3h of headroom.
Stations without a person
75%
1 gate left on 4 stations.
Where an item spends its time
35% waiting on a person
65% in the agent lane
An item now takes 173 minutes of worked time end to end against 173 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 Response

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.9 hrs

now Forecast · Alert Correlation Agent · 1.0 hrs

As the ledger has it

the same stations, plus 2 categories the estate already counts

0 min of 4.6 hrs

now Forecast · Alert Correlation Agent · 1.0 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.

2 systems attributed

0 of 2 returning records

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
Reliability Orchestrator
That orchestrator’s remit
Owns incident work end to end inside Engineering. Runs 3 lines across 17 stations, drains the repeatable share into the AI-OPS tower, and holds 3 human gates.
Accountable person
Director, Site Reliability
Sub-function
Site Reliability
Shared spine tower
ai-ops
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.