Service RD6C
Scale Readiness Assessment
Runs analytical. Starts when the reporting period closes. It runs 12 times a week across 4 stations. One of those stations stops for a person and 3 are done by an agent, none of them on the shared spine.
Runs a week
12
115 in flight right now.
Stations
4
1 person · 3 agent · 0 spine
Agent share of steps
75%
Autonomy on this service is set at 76% against a ceiling of 76%.
Decisions a person makes
1
Held by Director, Product Development.
Touchless
49%
Share of runs that complete without anybody opening them.
Timetable against actual
49.0h
Actual 50.9h, 1.9h 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 | Score readiness | Agent | Build Planning Agent | workflow | 5h 19m | 9h 28m | 29 | Product Lifecycle Management |
| 2 | Identify gaps | Agent | Test Plan Agent | workflow | 1h 44m | 2h 5m | 41 | Research Notebook and Experiment Data |
| 3 | Draft plan | Agent | Iteration Tracking Agent | workflow | 14h 4m | 33h 19m | 36 | Product Lifecycle Management |
| 4 | Leader review Held for a named human when the unit exceeds the prototype decision envelope, when confidence falls below the floor, or when a policy clause is engaged. | Human | Director, Product Development | policy | 18h 52m | 23h 59m | 9 | 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
4 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
4 stations, nothing waiting, nothing sent back
0 min of 40 hrs
now Score readiness · Build Planning Agent · 5.3 hrs
As the ledger has it
the same stations, plus 3 categories the estate already counts
0 min of 45 hrs
now Score readiness · Build Planning Agent · 5.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
2 systems attributed
0 of 2 returning records
Product Lifecycle Management
Siemens Teamcenter · engineering · inbound · high
3 of 4 stations attributed here · read only
Research Notebook and Experiment Data
Benchling · engineering · inbound · medium
1 of 4 stations attributed here · read only
System attribution is a rule, not a reading. more
Who runs it
Orchestration and accountability
- Orchestrated by
- Prototype Orchestrator
- That orchestrator’s remit
- Owns prototype work end to end inside Research & Development. Runs 3 lines across 17 stations, drains the repeatable share into the C2L tower, and holds 4 human gates.
- Accountable person
- Director, Product Development
- Sub-function
- Prototype & Pilot
- Shared spine tower
- Not on the shared spine
- 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