Service MK6C
Site Health Watch
Runs transactional. Starts when a threshold is crossed. It runs 2,597 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
2,597
110 in flight right now.
Stations
5
1 person · 2 agent · 2 spine
Agent share of steps
80%
Autonomy on this service is set at 72% against a ceiling of 84%.
Decisions a person makes
1
Held by Director, Digital Experience.
Touchless
80%
Share of runs that complete without anybody opening them.
Timetable against actual
15.3h
Actual 13.1h, 2.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 | Monitor | GBS | Site Performance Agent | gbs | 1h 34m | 2h 43m | 26 | Customer Relationship Management |
| 2 | Detect regression | Agent | Conversion Path Agent | workflow | 56m | 1h 16m | 45 | Customer Relationship Management |
| 3 | Auto-revert | GBS | Site Performance Agent | gbs | 2h 28m | 5h 32m | 25 | Customer Relationship Management |
| 4 | Notify Held for a named human when the unit exceeds the web change decision envelope, when confidence falls below the floor, or when a policy clause is engaged. | Human | Director, Digital Experience | policy | 10h 11m | 17h 11m | 9 | Customer Relationship Management |
| 5 | Root cause | Agent | Accessibility Monitor | workflow | 2h 24m | 4h 4m | 5 | Marketing Automation |
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
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 18 hrs
now Monitor · Site Performance Agent · 1.6 hrs
As the ledger has it
the same stations, plus 4 categories the estate already counts
0 min of 31 hrs
now Monitor · Site Performance Agent · 1.6 hrs
What breaks, and where it is counted
No break below was chosen. more
What the two runs say together
4 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
2 systems attributed
0 of 2 returning records
Customer Relationship Management
Salesforce Sales Cloud · crm · bidirectional · critical
4 of 5 stations attributed here · would write back
Marketing Automation
Marketo Engage · marketing · bidirectional · medium
1 of 5 stations attributed here · would write back
System attribution is a rule, not a reading. more
Who runs it
Orchestration and accountability
- Orchestrated by
- Digital Orchestrator
- That orchestrator’s remit
- Owns web change work end to end inside Marketing. Runs 3 lines across 19 stations, drains the repeatable share into the A2L tower, and holds 3 human gates.
- Accountable person
- Director, Digital Experience
- Sub-function
- Digital & Web
- Shared spine tower
- a2l
- 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