Service EN6C
Release Readiness
Runs transactional. Starts when a request lands in the queue. It runs 4,656 times a week across 3 stations. One of those stations stops for a person and 2 are done by an agent, 2 of them on the shared spine.
Runs a week
4,656
61 in flight right now.
Stations
3
1 person · 0 agent · 2 spine
Agent share of steps
67%
Autonomy on this service is set at 81% against a ceiling of 85%.
Decisions a person makes
1
Held by Director, Release Engineering.
Touchless
78%
Share of runs that complete without anybody opening them.
Timetable against actual
21.4h
Actual 20.2h, 1.2h under the timetable.
Operations
The lane diagram
Read it left to right. more
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 | Check gates | GBS | Release Note Agent | gbs | 1h 18m | 2h 8m | 26 | Group ERP — Materials and Inventory |
| 2 | Assemble evidence | GBS | Release Note Agent | gbs | 2h 38m | 4h 24m | 33 | Group ERP — Materials and Inventory |
| 3 | Release manager sign Held for a named human when the unit exceeds the release decision envelope, when confidence falls below the floor, or when a policy clause is engaged. | Human | Director, Release Engineering | policy | 34m | 59m | 2 | 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
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
3 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
3 stations, nothing waiting, nothing sent back
0 min of 4.5 hrs
now Check gates · Release Note Agent · 1.3 hrs
As the ledger has it
the same stations, plus 3 categories the estate already counts
0 min of 9.6 hrs
now Check gates · Release Note Agent · 1.3 hrs
What breaks, and where it is counted
No break below was chosen. more
What the two runs say together
3 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
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
1 systems attributed
0 of 1 returning records
Group ERP — Materials and Inventory
SAP S/4HANA MM · supply · bidirectional · high
3 of 3 stations attributed here · would write back
System attribution is a rule, not a reading. more
Who runs it
Orchestration and accountability
- Orchestrated by
- Release Orchestrator
- That orchestrator’s remit
- Owns release work end to end inside Engineering. Runs 3 lines across 15 stations, drains the repeatable share into the IT tower, and holds 3 human gates.
- Accountable person
- Director, Release Engineering
- Sub-function
- Release & Deployment
- Shared spine tower
- it
- 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. more