The catalogue EngineeringSite ReliabilityTransactional

Service EN7B

Error Budget Enforcement

Runs transactional. Starts when a threshold is crossed. It runs 3,053 times a week across 5 stations. One of those stations stops for a person and 4 are done by an agent, 2 of them on the shared spine.

Runs a week

3,053

118 in flight right now.

Stations

1 person · 2 agent · 2 spine

Agent share of steps

80%

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

Decisions a person makes

Held by Director, Site Reliability.

Touchless

85%

Share of runs that complete without anybody opening them.

Timetable against actual

24.4h

Actual 31.5h, 7.1h over the timetable.

Operations

The lane diagram

Read it left to right. more

Person1 station and 50% of the dwellAgent2 stations and 28% of the dwellShared spine2 stations and 22% of the dwell4 crossings between lanes

Human

decides

Agent

does the work

GBS

shared spine

System

attributed by rule

Group ERP — Materials and Inventory

Configuration Management Database

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.

#	Station	Lane	Who	Layer	Dwell	Target	In flight	System
1	Measure	GBS	Alert Correlation Agent	gbs	16m	26m	44	Group ERP — Materials and Inventory
2	Detect burn	Agent	Incident Commander Agent	workflow	1h	1h 49m	32	Configuration Management Database
3	Freeze releases 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.	Human	Director, Site Reliability	policy	4h 55m	6h 15m	1	Group ERP — Materials and Inventory
4	Notify	GBS	Alert Correlation Agent	gbs	1h 57m	4h 16m	40	Group ERP — Materials and Inventory
5	Restore	Agent	Error Budget Agent	workflow	1h 45m	3h 17m	1	Group 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. more

Move something

Demand100%

3,053 a week is what the estate records. more

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 gates429 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. more

Person time a week

15,010.6h

3,053 items at 295 minutes of decision each.

Agent time a week

15,163.2h

298 minutes an item, which does not compete for a person.

Gate load

100%

Inside capacity, with 4.4h of headroom.

Stations without a person

80%

1 gate left on 5 stations.

Where an item spends its time

50% waiting on a person

50% in the agent lane

An item now takes 593 minutes of worked time end to end against 593 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 Error Budget Enforcement

The simulation is arithmetic on the estate, not a queueing model. more

How it runs

Run it again, going wrong

The same unit and the same stations, broken the way the estate already records breaking. more

5 stations, walked twice

Once clean, once with the categories the estate counts

This is the same unit on the same stations, breaking. more

No break below was chosen. more

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

now Measure · Alert Correlation Agent · 16 min

As the ledger has it

the same stations, plus 5 categories the estate already counts

0 min of 22 hrs

now Measure · Alert Correlation Agent · 16 min

personagentshared spinework the break addsnobody working it

What breaks, and where it is counted

No break below was chosen. more

What the two runs say together

5 counted categories land on this procedure. more

What this run cannot claim

These breaks are shown together on one unit so the shape of a bad day fits on one screen. more

The separation register records a duty conflict against a sub-function and a named post, not against one procedure. more

Two clocks run. Worked time is the sum of the time the work is actually being done … more

Live observability

Systems this service would touch

Attributed by rule from the function's system list. more

2 systems attributed

0 of 2 returning records

The system register

Group ERP — Materials and Inventory

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

modeled

4 of 5 stations attributed here · would write back

Configuration Management Database

ServiceNow CMDB · itsm · inbound · high

modeled

1 of 5 stations attributed here · read only

System attribution is a rule, not a reading. more

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

Incident ResponseEN7A Capacity ResponseEN7C

What this page is and is not

This is a catalogue of the modeled estate. more