Service RO10B
Schema Change Release
Runs transactional. Starts when a threshold is crossed. It runs 2,498 times a week across 7 stations. One of those stations stops for a person and 6 are done by an agent, none of them on the shared spine.
Runs a week
2,498
133 in flight right now.
Stations
7
1 person · 6 agent · 0 spine
Agent share of steps
86%
Autonomy on this service is set at 72% against a ceiling of 80%.
Decisions a person makes
1
Held by Director, Revenue Systems.
Touchless
75%
Share of runs that complete without anybody opening them.
Timetable against actual
5.9h
Actual 4.5h, 1.4h 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 | Request | Agent | Integration Health Monitor | workflow | 8m | 15m | 26 | Customer Relationship Management |
| 2 | Impact scan | Agent | Sync Failure Agent | workflow | 3h 8m | 7h 19m | 41 | Enterprise Data Warehouse |
| 3 | Build | Agent | Schema Change Agent | workflow | 32m | 47m | 13 | Configure, Price and Quote |
| 4 | Test | Agent | Sandbox Refresh Agent | workflow | 2h 37m | 6h 13m | 23 | Reporting Semantic Layer |
| 5 | Change board approve Held for a named human when the unit exceeds the change decision envelope, when confidence falls below the floor, or when a policy clause is engaged. Hands over at information-technology | Human | Director, Revenue Systems | policy | 5h 52m | 7h 40m | 8 | Customer Relationship Management |
| 6 | Deploy | Agent | Systems Policy Agent | workflow | 1h 59m | 3h | 17 | Marketing Automation |
| 7 | Verify | Agent | Revenue Systems Orchestrator | workflow | 34m | 51m | 5 | Customer Relationship Management |
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
7 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
7 stations, nothing waiting, nothing sent back
0 min of 15 hrs
now Request · Integration Health Monitor · 8 min
As the ledger has it
the same stations, plus 3 categories the estate already counts
0 min of 20 hrs
now Request · Integration Health Monitor · 8 min
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
5 systems attributed
0 of 5 returning records
Customer Relationship Management
Salesforce Sales Cloud · crm · bidirectional · critical
3 of 7 stations attributed here · would write back
Enterprise Data Warehouse
Snowflake · analytics · inbound · critical
1 of 7 stations attributed here · read only
Configure, Price and Quote
Salesforce CPQ · crm · inbound · high
1 of 7 stations attributed here · read only
Reporting Semantic Layer
Power BI shared datasets · analytics · inbound · medium
1 of 7 stations attributed here · read only
Marketing Automation
Marketo Engage · marketing · bidirectional · medium
1 of 7 stations attributed here · would write back
System attribution is a rule, not a reading. more
Who runs it
Orchestration and accountability
- Orchestrated by
- Revenue Systems Orchestrator
- That orchestrator’s remit
- Owns change work end to end inside Revenue Growth Management. Runs 3 lines across 17 stations, drains the repeatable share into the IT tower, and holds 3 human gates.
- Accountable person
- Director, Revenue Systems
- Sub-function
- Systems & Integration
- Shared spine tower
- Not on the shared spine
- Hand-over points
- information-technology
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