Service RD5C
Model Retirement
Runs transactional. Starts when a request lands in the queue. It runs 4,999 times a week across 5 stations. One of those stations stops for a person and 4 are done by an agent, 3 of them on the shared spine.
Runs a week
4,999
136 in flight right now.
Stations
5
1 person · 1 agent · 3 spine
Agent share of steps
80%
Autonomy on this service is set at 75% against a ceiling of 83%.
Decisions a person makes
1
Held by Director, Data Science.
Touchless
86%
Share of runs that complete without anybody opening them.
Timetable against actual
7.2h
Actual 8.3h, 1.1h over 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 | Detect obsolescence | GBS | Feature Engineering Agent | gbs | 1h 41m | 2h 15m | 32 | Product Lifecycle Management |
| 2 | Assess dependency | Agent | Model Training Agent | workflow | 2h 49m | 5h 44m | 39 | Product Lifecycle Management |
| 3 | Owner approve Held for a named human when the unit exceeds the model decision envelope, when confidence falls below the floor, or when a policy clause is engaged. | Human | Director, Data Science | policy | 4h 3m | 5h 41m | 4 | Product Lifecycle Management |
| 4 | Retire | GBS | Feature Engineering Agent | gbs | 1h 59m | 4h 4m | 18 | Product Lifecycle Management |
| 5 | Archive | GBS | Feature Engineering Agent | gbs | 2h 30m | 3h 43m | 43 | Product Lifecycle 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
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 13 hrs
now Detect obsolescence · Feature Engineering Agent · 1.7 hrs
As the ledger has it
the same stations, plus 4 categories the estate already counts
0 min of 28 hrs
now Detect obsolescence · Feature Engineering Agent · 1.7 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
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
1 systems attributed
0 of 1 returning records
Product Lifecycle Management
Siemens Teamcenter · engineering · inbound · high
5 of 5 stations attributed here · read only
System attribution is a rule, not a reading. more
Who runs it
Orchestration and accountability
- Orchestrated by
- Modeling Orchestrator
- That orchestrator’s remit
- Owns model work end to end inside Research & Development. Runs 3 lines across 19 stations, drains the repeatable share into the DATA-ANALYTICS tower, and holds 4 human gates.
- Accountable person
- Director, Data Science
- Sub-function
- Data Science & Modeling
- Shared spine tower
- data-analytics
- 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